04-11-2007 11:56 PM
04-12-2007 5:08 AM
Hi Sunny,
ST01 is used as Authorization Trace. Authorization Object S_ADMI_FCD gives access to the trace function
You can analyze authorizations as follows: Choose Tools -> Administration -> Monitor -> Traces -> SAP System Trace or Transaction ST01.
Choose trace component Authorization check and pushbutton Trace on. The trace is automatically written to the hard disk.
To limit the trace function to your own sessions, choose Edit -> Filter -> Shared. Enter your user ID in field Trace for user only in the displayed dialog box.
Once the analysis is completed, choose Trace off.
To display the results of the analysis, choose Goto -> Files/Analysis or the pushbutton File listSelect the required file and choose Analyze.
The results of the authorization check are displayed in the following format: <Authorization object>:<Field>=<Tested value>
The return code shows whether or not the authorization code was successful.
ST01 Return Code 0 -
Authorization check passed
1 -
No Authorization
2 -
Too many parameters for authorization check
3 -
Object not contained in user buffer
4 -
No profile contained in user buffer
6 -
Authorization check incorrect
7,8,9 -
Invalid user buffer
Hope it helps.
Please awatd points if it is useful.
Thanks & Regards,
Santosh
04-12-2007 12:40 AM
ST01 is to troubleshoot where the authorization issues happening.
Well you can do a trace on the following components:-
Kernel
RFC calls
Lock operations
Auth Check
Table buffer
Db access.
This is a handy method to troubleshoot. You need to manually turn on the TRACE for any of the above components and filter the trace by user (either single or all) and turn off the trace after particular activity has been completed.
Otherwise we have the CCMS which trigger the automatic alerts that happens at the system level.
Plz Award points if you find this useful.
Thanks
Sudhan Shan
04-12-2007 5:08 AM
Hi Sunny,
ST01 is used as Authorization Trace. Authorization Object S_ADMI_FCD gives access to the trace function
You can analyze authorizations as follows: Choose Tools -> Administration -> Monitor -> Traces -> SAP System Trace or Transaction ST01.
Choose trace component Authorization check and pushbutton Trace on. The trace is automatically written to the hard disk.
To limit the trace function to your own sessions, choose Edit -> Filter -> Shared. Enter your user ID in field Trace for user only in the displayed dialog box.
Once the analysis is completed, choose Trace off.
To display the results of the analysis, choose Goto -> Files/Analysis or the pushbutton File listSelect the required file and choose Analyze.
The results of the authorization check are displayed in the following format: <Authorization object>:<Field>=<Tested value>
The return code shows whether or not the authorization code was successful.
ST01 Return Code 0 -
Authorization check passed
1 -
No Authorization
2 -
Too many parameters for authorization check
3 -
Object not contained in user buffer
4 -
No profile contained in user buffer
6 -
Authorization check incorrect
7,8,9 -
Invalid user buffer
Hope it helps.
Please awatd points if it is useful.
Thanks & Regards,
Santosh
04-12-2007 8:04 AM
Hi Sunny,
I find there are a couple of limitations to ST01
1. It returns the results of all the checks evaluated rather than purely the checks required for the transaction to proceed. It's not a problem, rather than something that needs to be understood and factored into any analysis of the trace.
2. In older versions of SAP, I have experienced problems in the past when trying to trace the auth checks in reports that use logical databases. An example is some S_ALR* used to be delivered without the corresponding auths updated in the usob* tables.
Regards
Alex