SAP Basis Administrator Problems And Solutions

The below give you some ideas what you are likely to encounter while working as a SAP Basis Administrator.  Do remember that the company you work with are unique and some solution are generic and some requires some thinking skill from your role as the basis consultant.
 
1) How can I produce a list of users and the transactions they have accessed for the past month? Is there any tool apart from turning the audit log on? 
 
Without using SM19 and SM20 to turn auditing on and analyzing the audit logs, you basically have one option: ST03N.
 
In ST03N you can use the User Profile under the Analysis Views section. Just keep in mind that ST03N keeps limited data and it might not help you to go back one full month. Check the configuration parameters by switching to "Expert Mode" and looking under "Collector and Performance DB," "Statistics Records and Files". 
 
2) We get stuck during the SAP import process using SAPinst. The user DDIC is unable to login.
 
This kind of problem may arise for different reasons. You can examine the installation logs to determine the cause. If everything in the installation went fine with no errors at all, you can do a quick hack to finish the install.
 
You can edit the control file (keyb.xml) and replace the ERROR status with OK. Then, re-run SAPinst and finish the install. After that you can reset the password for account DDIC.  
 
3) We have SAP 6.20 installed in one of our systems. The system configuration is as follows: Intel Pentium III, 850 MHz, 128 MB RAM, 40 GB hard disk. We are able to connect to the SAP server maintained by HCL. When we try to log in using SAP logon, the login screen appears. But when we try to log in, it displays a SAPGUI 620 sapdp00-error.
 
Analyze the developer traces (dev_*) files under "usrsap<SID>DVEBMGS00work.  The lack of memory in your system might be the culprit of the problem. Anything based on Web AS 6.20 needs much more than 128MB of RAM. Even 512MB of RAM is the bare bone minimum for a one-user test system. Also, you should consider adding more disk space and more than one disk. Performance with a single disk is terrible. 
 
4) Is there a way to download file structures (SE11) from one SAP R/3 system in server 'X' version 4.6c to another SAP R/3 system in server 'Y' and version 6.0? I have developed something that should run in various systems, but it seems to be a problem to be able to transport the information all over due to the differences of field types in the various releases etc. Do I have to install everything manually? Just a little extra info: 4.6.c is a normal automotive system and the 6.0 is a BW system.
 
It seems that you're asking how to transport a table structure from one system to another under different SAP products and versions. If that's the case, please take a look at SAP note 330267 (Transports between Basis Releases 4.6* and 6*). Technically, you can create a transport via SE01 and enter the objects there so they can be imported later into another system. If you simply want to export the structure of a table into a file please do the following: 
 
Run SE11 and enter the table in question. Click Display.
Select Utilities --> Runtime Object --> Display.
After displaying the runtime objects for the table in question click Views. Then, select List Output. On the next screen you will be able to select System --> List --> Save --> Local File. 
 
5) I would like to know how to set up a transport strategy. For instance, when I create and release a request at DEV200, the CR goes automatically to QLT100. 
 
You need to set up the Extended Transport Control in STMS. Set parameter CTC to 1 instead of 0. This allows you to specify target clients instead of just target systems. Thus, allowing you to enter the specific client(s) where you want your transports to go. 
 
6) What is the procedure for importing a client that was exported with SCC8? 
 
The exported client (via SCC8) is now available in the form of transports at the OS level and it's also available for import via STMS or TP IMPORT. If you are using R/3 4.5 or higher, use transaction STMS to import the client. Simply go to the Import Overview in STMS of the system where you want to import the client into. Then, highlight the first transport created as a result of the export and click Import. The import will take a while. Depending on the size of the transport, it may take several hours. Once the import is complete, you need to log in to the target client and run transaction SCC7 to perform the post-client import, which normally does not take long at all. 
 
7) I have a question about authorization roles in SAP. How many roles can we create in an SAP system? What is the maximum number of roles allowed in an SAP system.
 
I am not aware of any limit. As far as I know, you can create hundreds of roles. R/3 4.7 (R/3 Enterprise) already comes with more than 1,500 roles. 
 
8) We are on version 4.5B. We went live November of 1999. Our current database is 700GB+. We have 45 active retail shops (school and office supplies). Do you think the size of our production is normal?
 
It depends on what modules you have implemented. The database is large for sure. However, I am afraid I cannot judge if it's too large for what you have running. I do recommend you check if the application logs are cleaned up once in a while. Take a look at SAP note 195157 (Application log: Deletion of logs). Have you done any archiving, yet? As an SAP customer you are entitled to have them log in to your system and do a system check. They may be able to come up with sound recommendations as to what to do to keep the database at a decent size.
 
9) Because of tight security requirements for the government, it is necessary to add a "Security Banner" to be "checked" through before entering SAP. (Just like the license banner at "first" SAP login.) How can we do this?
 
I have not done this myself, but it is possible that you need to change program SAPMSYST. However, SAP does not recommend changing it because if something goes wrong you might not be able to login to the system at all. I would consult with SAP to see if they have a way to do what you're asking here.
 
On the other hand, you can add text to the login screen. This can be done easily via transaction SE61. Change document ZLOGIN_SCREEN_INFO and add the text you want. This will appear then at the login screen. This is an approach that a lot of companies use.
 
A quick solution would be to invoke a script that displays the banner first and then invokes saplogon.exe.
 
10) Which are the implications to allow the ABAPers to use transactions such as SM66, SM50, SM51, STAD, ST05 and ST04? According to our BASIS team, this is not advisable, since it could allow to ABAPERS to cancel work process in the server, besides canceling user processes. What do you think about it? 
 
This is one of those decisions management needs to make. Even if the ABAP developers had access to those transactions, you would most likely be able to find out what they did by reading the system log. In an ideal environment, ABAP developers should not have access to the Production system, only users, business analysts and administrators. ST04 is a Basis transaction. I would not give that one to them. I don't see the need. ST05 they might need in development and testing. SM66 and SM50/51 are also Basis transactions, but I've seen developers have access to them in development and test servers. STAD is usually just for Basis admins.

See Also
Responsibilities Of SAP Basis Consultant

Get help for your Basis problems
Do you have a SAP Basis Question?

SAP Basis Admin Books
SAP System Administration, Security, Authorization, ALE, Performance Tuning Reference Books

SAP Basis Tips
SAP BC Tips and Basis Components Discussion Forum

Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES 

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.