Some more info, I was forwarded these in an email and thought it might be useful for the readers here:
1.)We are running SAP release 4.0B using the 620 GUI. By default, my list, save, local file, directory is C:SapWorkDir. How do I change this to something else? If I click on Options there is a directory for the local data area, which looks like the place to change the directory, but that does nothing. There must be a way to change this.
Use transaction SO21 to maintain the PC local directory. Or, run the ABAP program (via SA38 or SE38) RSSOPCDR.
2.)I would like to know which users have access to particular transactions. Is this possible?
Yes. There are several ways.
I think the easiest one is for you to run transaction /nSUIM. In this transaction (User Information System), drill down to:
Infosystem authorization -User -Users by complex selection criteria -By transaction authorizations
Finally, enter the transaction in question and execute.
If you are running R/3 4.7, you can also run transaction /nPFCG.
3.)I want to install SAPGUI into 50 machines. Can I do it from the server by installing the SAP installation server? If so, how?
Go to the “Knowledge Corner” section and look for it under “SAPGUI 6.20 for Windows”. The steps are basically the same for SAPGUI 6.40 –if you are installing that version.
Once you have set up the server you can use SAPadmin to create custom packages and install the client software remotely.
4.)I’d like to know if we make client copy today, will the data will be copied to another client today as well? Suppose after one week I want to copy the rest of the data to the same client. Will I have to copy all the client data and overwrite it, or do I have an option to copy only one week’s worth of data and update it?
A client copy overwrites the target client. The only exception is the user master records (SAP_USER copy profile). But, you cannot just copy a week’s worth data using SAP standard tools. You need to use ALE to transfer the data you want or use third-party tools for that.
5.)I have a problem with my server. When I start the server the dispatcher (disp+work.exe) is getting started, but then it’s stopping. I am using R/3 4.6B. Its sysid = DEV and the OS = 2003server.
This could be due to a number of reasons. My best recommendation at this time is to examine the developer tracer.
Within the SAP MMC, right-mouse click on the instance name and choose developer traces from the drop-down menu. There, choose to examine the file dev_disp, dev_ms and see if there are any dev_wpX files exist.
Also, make sure that the system profiles exists under usrsapsysprofile. Check that the services file contains the appropriate entries (example: sapMS xx).
6.)Can we make the WPs changes in operation mode effective immediately by force? One of our consultants said that it is possible through a transaction.
Yes. It’s possible via transaction RZ03.
Choose the instance and use Control -> Switch Operation Mode.
7.)Users are complaining that the SAP system shows a hour glass for a long time at the time of logon and they aren’t able to log on to the system. How can I troubleshoot this problem?
This is a symptom of busy dialog processes. Use one of these tools to find out the status of the work processes: dpmon.exe at the OS level (part of the R/3 kernel), MMC and SM50 (Work Process Overview).
Also, check the CPU and other system resources via ST06 and using Performance Monitor at the OS level.
8.)I have a stand-alone computer for which I forgot the user and password for log in.
Is there anyway I can log in to it?
Yes. This requires you to go to the database level, though. I don’t know what RDBMS you have (MSSQL, Oracle, MaxDB, etc.). But, really all you have to do is to delete the SAP record in table USR02 for client 100. After that, SAP will let you log in as SAP with password PASS.
9.)Our SAP file system is filling up because initially it was defied too small. What are the non-required files that can be deleted from the SAP system? We are using HP-UX NetWeaver2004s on an Oracle database.
The files that can be deleted are mentioned below.
1. Offline Redo log files
Backup them and then delete
2. Old spool and log files
They are not necessary for R/3 functions and should be deleted regularly by scheduling a periodic batch job.
3. File name “CORE” (Unix only)
The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often contains a file called ‘core’ from previous program terminations. This file may be deleted at any time.
4. Old ABAP/4 trace files.
Use Transaction SE30 to delete the files
5. Old output requests
They are stored on the data directory as files SP*.
Remember that deleting these files is not a permanent solution. You should increase the file system sizes.
10.)It is a very common misconception that “sequential reads in SM50 means that a full table scan is executed and an index is not used”. The correct definition/concept is:
Direct read
The term “Direct read” refers to accesses in which a maximum of one line is returned by the database. This includes summarization queries such as SELECT COUNT and fully-qualified primary key accesses.
Sequential Read
A “Sequential Read” refers to all other read database accesses, in which there may be more than one line returned. It is true that the term “Sequential read” is a little deceptive since it implies that blocks are always read sequentially (as in a full table scan). In reality, however, when you perform a trace on these queries you will see that index is used in most cases.
So, “Direct read” and “Sequential read” in SM50 are worthless for a performance analysis. It only shows that the processes are running and processing one of the queries directed at the database interface.
For expensive SQL statements analysis, “Reads/User Calls” value (TCODE BACOCKPIT or ST04OLD) is an indication. If this value is above 15, the SQL statements should be checked in detail.
11.)My admin user ID has been locked out. Is there a table I can update in Oracle to reset the flag and enable myself to log in?
Select all entries of table USR02 where ‘UFLAG’=128. These users are locked by reason of incorrect logons. ‘UFLAG’=64 will give you the users that are blocked by Administrator. Set ‘UFLAG’ to 0, to unlock your account.
12.)Why are transport requests classified into workbench and customizing? What does this classification indicate?
All customizing changes (changes to SAP functionality) are collected in customizing requests. Changes to the SAP repository and data dictionary (customers development or changes to SAP standard objects) are collected in workbench requests.