Vous êtes sur la page 1sur 16

Authorization Trace in transaction ST01

Sometimes you may face a strange behavior in DMS functions which are caused by wrong authorization customizing or you do not know how and where authorization objects are checked by the system. So this page explains how an authorization trace is started in transaction ST01. This trace shows all checked authorization objects, the values which are handed over to the check and which object leads to the missing authorization behavior .

To use the ST01 Trace for checking the authorization objects please go to transaction ST01 and set the flag for 'Authorization check' first. Then press the 'Trace on' button and leave the transaction.

For executing a more detailed authorization check you can also maintain some filter criteria by using button 'General Filter'. Here you can define a special user name or some other data which

restricts the amount of data which is logged in the trace result.

Now execute exactly the same steps which lead to the mentioned authorization warning message. Afterwards please return to transaction ST01 and press the 'Trace off' button. Then press the 'Analysis' button and on the next screen choose Execute.

Now a list with all checked authorization objects should appear and the one which is responsible for the warning message should be marked in red. If you face problems with the complexity of this output list please see the following link which

ST02 Tune summary

1) Hit ratio for each buffer should be greater than 95%. 2) If hit ratio is less than 95%, no swap should be there. 3) Current usage of extended memory should not cross 75%. 4) We have to check the swaps for each buffer. For program buffers it should be 10000 hits/ day & for other buffers it should be 1000 hits/ day. 5) We have to check the free space & the free directory for each buffer.

Workload Monitor (Transaction ST03 or ST03N)

The ST03 Workload Monitor is the central access point for analyzing performance problems in the SAP system. ST03N is a revised version of transaction ST03. In current SAP Releases transactionST03N replaces transaction ST03 and is automatically started when you enter transaction code ST03. Here you can compare the performance values for all instances, and compare the performance of particular instances over a period of time. Due to the number of possible analysis views for the data determined in transaction ST03, you can quickly determine the cause of performance problems.

You can use the workload monitor to display the following, among other things:

Number of instances configured for your system Number of users working on the different instances Response time distribution Distribution of workload by transaction steps, transactions, packages, subapplications, and applications Transactions with the largest response times and database time Memory usage for each transaction or each user per dialog step Workload caused by RFC, broken down by transactions, function modules, and destinations Number and volume of spool requests Statistics about response time distribution, with or without the GUI time Optional: table accesses Workload and transactions used by users, broken down by users, accounting numbers, and clients Workload generated by requests from external systems Handy Calling up transaction ST03 Switch to advanced mode. Choose an analysis period. Choose an analysis view.

Look at the DB time. It should not be more than 40% of the response time.

The following are important analysis views in transaction ST03:

System load overview: general response time distribution across different task types Time profile: How does the response time react over the day? Are there peak times with bad response times? Transaction profile: Can you observe response time problems in general or only in certain transactions?

ST03 Workload Overview:

Handy Important information in ST03 are time and transaction profile as well. In the Workload Monitor you can also determine which transactions have accessed which database tables and how often. Since the number of statistics records greatly increases by logging table accesses of this type, this option is deactivated by default.

ST04 Database performanance overview

Check Buffer Quality should be always > 97%

If it is below 97%, please investigate as it may be error. However, poor buffer quality is not always due to a real problem. For example, Transports into a system can reduce buffer quality. You can increase db_cache_size in Oracle init<Sid>.ora file To maintain good data buffer quality we have to run Update Optimizer statistics daily in DB13. Reasons for low Buffer quality are: Transports Buffer resets Offline Backups, SAP system reboots. Not enough memory allocated to buffers. Too much information is loaded into system. Users are using too much different data all the time. In Shared Pool Area Check DD cache quality is at least 95% And pin ratio is at least 99% and reloads/pins % is less than 0.2

In log buffer area Redo log wait is less than 5 sec

And in the detailed analysis menu check for database alerts and check for log changes Log change history will be in Detailed analysis->DisplayV$values-> V$LOGHIST Per hour there may be three log changes. (good practice)

Finding a BADI using Buffer trace - Transaction ST05 (Screenshots)

SAP Enhancements Business Add-in (BADI) How do we find the BADI's associate for a transaction using 'Buffer Trace' (SQL Trace)? Start transaction 'ST05' (Performance Analysis). Set flag field "Buffer trace" Remark: We need to trace also the buffer calls, because BADI database tables are buffered. (Especially view V_EXT_IMP and V_EXT_ACT) Push the button "Activate Trace". Start transaction in a new GUI session.

Go back to the Performance trace session. Push the button "Deactivate Trace". Push the button "Display Trace". The pop-up screen "Set Restrictions for Displaying Trace" appears. Now, filter the trace on Objects: V_EXT_IMP V_EXT_ACT Push button "Multiple selections" button behind field Objects Fill: V_EXT_IMP and V_EXT_ACT

Here goes the possible list of BADI for the respective transaction

ST06 - Operating System Monitor

An SAP instance runs within an operating system. The operating system provides the instance with the following resources:

Virtual memory Physical memory CPU File system management Physical disk Network

Performance indicators are:

Average load of and utilization of the CPU Memory utilization Paging in and out of data to and from the memory (replaced by pool data in the OS/400 operating system monitor) Disk utilization information LAN activity Operating system configuration parameters

Possible Error Messages Shared memory not available SAPOSCOL has not created a shared memory segment. This is usually due to the fact that the SAPOSCOL program has not been started. Collector not running SAPOSCOL was started and created a shared memory segment, but was later terminated.

CPU: The following data about CPU usage is displayed for every CPU, broken down as percentages by:

Users System Times in which the CPU had no task to perform or was waiting for an input/output (idle)

Other Values Collected

Number of CPUs Interrupts per second/hour System calls per second/hour Context switches per second/hour Average number of waiting processes for the last minute, last five minutes and the last 15 minutes


Physically available and free main memory in Kilobyte; the minimum and maximum free main memory is also measured hourly. As a rule of thumb, if CPU bottlenecks occur if there is less than 10 MB of free physical memory for a small hardware configuration. This value can vary depending on operating system and system size.

Paging is the exchange of data pages between the main memory of a host system and the overflow store in a paging file on the hard disk; paging occurs if the main memory is not large enough for the contexts of all running processes SAPOSCOL measures the number of pages paged in and paged out per second with the quantities of memory paged in and paged out in kilobytes. High paging rates indicate that the main memory is too small for the running processes. Measures that you can take are to extend the main memory, to move processes to other host systems, and to delay memory-intensive program runs to times of lower system workload. On Windows platforms (unlike UNIX platforms), the system performs paging out as a precautionary measure even when space is not required in the working memory, meaning that this value is irrelevant and you should only consider the paging in rate. Under UNIX, on the other hand, Page_Out is the critical value for evaluating the paging.

Swap Space is storage space on the hard disk to which data that is not required is written from the main memory, so that there is space in the main memory for the program currently being executed. SAPOSCOL measures the configured and free swap space in kilobytes and the actual and maximum size of the swap space in kilobytes. In addition, the maximum and minimum sizes of the free swap space are measured hourly. The most important values are the free and the actual swap space. Not all types of swap space are available on all operating systems. For this reason, in some cases, the actual swap space size corresponds to the configured and maximum swap space.

1. What will u do when OS collector is not runing, and if saposcol service is not starting? Check whether OS COL version is up to date if not apply the latest version and also check for Kernel version. Check for the permissions of the Owner of OSCOL

There is a service called sapstartsrv.exe in \usr\sap\<sid>\sys\exe\run . doubleclick that exe and give the parameters...
Try with the below commands

Saposcol-d Collector>clean Collector>quit saposcol-k tostopthecollector. Saposcol-d (before restarting) Collector >leave (You should get a message Shared memory deleted) Collector>quit cd/usr/sap/tmp mv dev_coll dev_coll.old (make sure to remove the coll.put file) Saposcol -l (to start the SAPOSCOL.) 2. TP Commands: tp is a C program that runs independently of the SAP System. It reads and writes various files. "File" means a file in the operating system sense, not a database table. All the files tp works with are located in a special transport directory. tp starts specific programs, some of which are C programs, some of which are special operating system commands, and some of which are ABAP programs. tp uses the tables TRBAT and TRJOB to communicate with the ABAP transport programs.

tp addtobuffer <request> <sapsid> tp cleanbuffer <sapsid> This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .

tp delfrombuffer <request> <sapsid> If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.

tp delstopmark <sapsid> If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.

tp export <request> This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.

tp reformatbuffer <sapsid> [options] This automatically reformats the entire buffer.

tp setstopmark <sapsid> A special STOP mark is added to the list of requests registered for import into the specified SAP System

tp showparams <sapsid> This tp function displays which values the individual parameters of the transport profile have for the current SAP System.

tp verse <request> This creates versions of the objects in the specified request

tp Information Commands tp checkimpdp <sapsid>

The scheduling type for the transport daemon RDDIMPDP in the background processing of the SAP System <SAPSID>is displayed on the screen. tp connect <sapsid> The transport control program tp tries to log on to the database of the <SAPSID> SAP System and informs you if it has been successful or not with a message on the screen. If necessary, tp then logs off again. tp also calls R3trans. R3trans also attempts to log on to the database and informs you if it has been successful or not with a message. tp count <sapsid> The requests flagged for import into the <SAPSID> system are counted. The result is displayed. tp showinfo <request> The header information of the <request>is displayed on the screen.

3. name the jobs that will run while a transport is going on RDDIMPDP... If the above job is not scheduled go to SE38 and run job RDDNEWPP which will schedule RDDIMPDP Standard Default Jobs are created a job with TX STMS_IMPORT if you schedule the imports: the name is typically 'TMS_0000000001TMS_TP_IMPORT You also need to ensure the following job is scheduled in every client: RDDIMPDP To Schedule this job, correctly, run program RDDNEWPP in every client. his job will schedule other jobs RDD* when imports are taking place. 4. Finding any of the SAP tables that have been changed
During the production run of the SAP system, additional fields might have been added and you might have lost tracks of the SAP tables changes. Transaction code SPDD have been created to help you to find all the SAP tables that have been modified. Other ABAP Dictionary objects such as lock objects, matchcodes, and views, for which modification would not result in data loss, are not processed during the upgrade with transaction SPDD, but only after the upgrade is complete with transaction SPAU. SPAU Display modified DE objects


Display modified DDIC objects

How to reset user SAP*

To reset password of user SAP in ABAP stack on client 000, use this strategy: We need to delete user ID SAP* in Client '000' at SQL level For MS-SQL, you will use the SQL Management Studio and run a Query. Use the following SQL: Delete from <Schema>.USR02 where MANDT='000' and BNAME='SAP*' For Oracle: sqlplus "/ as sysdba" Delete from <Schema>.USR02 where MANDT='000' and BNAME='SAP*'; <Schema> is one of these entries: if system was originally installed with SAP Basis 4.x or below: SAPR3 if originally installed with SAP Basis 6.x (That is ERP 5): SAP[SID] If originally installed with SAP Basis 7.x (That is ERP 6): SAPSR3 You then need to change the instance parameter: 'login/no_automatic_user_sapstar = 0' (Zero) and restart the system. You can then logon to client '000' with User SAP* and password 'PASS'. You then create your user ID in client '000' and Recreate SAP* then change the instance parameter 'login/no_automatic_user_sapstar = 1' and restart the system. If you want to change SAP* in clients other than 000, simply use the same procedure and adapt client number accordingly.

Difference between SDM and JSPM In WAS 640 we have SDM through which we can deploy single patches. For deployment of entire stack, we get SAPINST with Support Stack. Then we have to run SAPINST to install Support Patch Stack.

However in WAS 700 we have we get JSPM through which we can import single support patch & Support Stack also. We can also apply latest kernel through JSPM. Saying that you can continue to use SDM for deploying your software components. JSPM can also be controlled with NWDI. JSPM is just an interface for SDM all the processing will done from SDM only. Using SDM you can deploy JAVA support as well as Business Packages. Till Net weaver 7.0 version JSPM can't be used to apply BP but from release 7.1 all the stuff has to be done from JSPM. Source system connection from BW to R/3 When you are trying to connect BW to R3 and R3 to BW in general the process is: 1. BW to R3 user is ALEREMOTE (system user)

2. R3 to BW user is BWREMOTE (system user) In your RSA1 -> Source system -> Create you use these users to create the connection. But when the connections are getting created the system asks you to log in to R3 once At that time you have to use a dialog user with Admin access to log in and it will also ask you to log into BW once here again you need to use a dialog user with admin access. Dont get confused with these users. The ALEREMOTE & BWREMOTE users are only for Data extraction handshake process.