Most of you might know and also have already worked with the STAUTHTRACE transaction code. For those who are still not aware of this transaction code or never used it before, STAUTHTRACE is an enhanced and user-friendly transaction code when compare to ST01 AUTH TRACE and is meant only for the authorization trace.
Further, SAP has introduced 2 new transaction codes STUSERTRACE and STSIMAUTHCHECK in the recent past.
Refer the below notes for more detailed information on these transaction codes:
- 2220030 – STUSERTRACE: User trace for authorization checks
- 2442227 – STSIMAUTHCHECK: Simulation of authorization checks
The authorization trace can be activated by enabling the profile parameter ‘auth/auth_user_trace’. The profile parameter can be switched dynamically. Once the trace is activated, filters can be defined either for a single/group of users or for a set of authorization objects. Additionally, you can also ignore the generic transaction codes such as SE37, SU53, SE38, and so on.