cancel
Showing results for 
Search instead for 
Did you mean: 

User ID which used debug function

vikas_sehra2
Participant
0 Kudos
2,585

Dear Team

Business clients want to know, which User ID has used Debug function in Production system.

Is there any audit transaction or other method to know that which ID used debug.

Please suggest.

Regards

Vikas

matt
Active Contributor

Change made to the value of a field while in debug are logged in the system log - as is "go to line".

But the ability to do debug in production with change should be strictly controlled. In order to debug and make changes in production you should have a specific role; this role should only be added as needed and removed after it is no longer needed. The history of role assignment is stored in the change documents accessible from SU01.

If you are just wishing to monitor debug activity in general - then so long as write access is denied - there is no way. Except as described above. I'm not convinced that your business client would or should be interested in display only debug access. I've debugged productive systems display only in validated, gxp relevant systems without issue. It's routine. Change access requires signatures!

vikas_sehra2
Participant
0 Kudos

Hi Matthew Billingham

I am convinced with your comment that debug should be restricted. This is a new client for me and we are working in the same.

But, as of now several users have debug authorization, so thats the reason, client wants to check previous history.

Is there any way, that we can get the details of user Id who used debug function.

Regards

Vikas

matt
Active Contributor

Debug access does not have to be restricted. It isn't (usually) necessary.

Debug access with change must be restricted.

Accepted Solutions (0)

Answers (2)

Answers (2)

flotxi
Participant

Hi Vikas,

you can check in transaction SM21.

Column User has the SAP Username and in Column Message Text you see what happened.

Best regards,

Florian

vikas_sehra2
Participant
0 Kudos

Hi Florian

Yes, SM21 screen shot above in good for us.

- Is there any setting required in SM21 to get the ALV layout as we get unicode display and we have to click and drill down to get the Debugger word.

That will be very tedious.

- SM21 is giving data only when there is an update in Debug, no log is generated if the debug function is selected but no change/update is done.

Regards

Vikas

matt
Active Contributor
0 Kudos

Reverse engineer SM21 to find out what file(s) it is reading to produce the output, write your own program.

touzik_itc
Active Participant
0 Kudos

Events logged in the system log can be found in the table TSL1T:

A1	8	'C debugging activated'
A2	3	'Goto ABAP Debugger: &9&9&9&9'
A2	6	'A manually caught process was stopped from within the Debugger (&A)'
A2	8	'DB &8 executed on explicit request from the debugger'
CU	K	'C debugging activated'
CU	M	'Jump to ABAP Debugger: &A'
CU	N	'A manually caught process was stopped from within the Debugger (&A)'
CU	O	'Explicit database commit or rollback from debugger &A'
CU	P	'Non-exclusive debugging session started'
IC	4	'Debugging of &A created for URL &B'
IC	5	'Debugging of &A deleted for URL &B'
IC	J	'Debugging entry was created by User &A for requirements of User &B.'
IC	K	'Debugging entry was deleted by User &A for requirements of User &B.'
R0	L	'Program &9&9&9&9&4 set manually to debug mode by user &9&3'
R0	X	'An update request was carried out in debugging mode'
R1	X	'Debugging session of user/mode &A/&B reset'
R6	H	'VM &a was moved to the debug mode<br>'
vikas_sehra2
Participant
0 Kudos

Thank You

Table TSL1T does not provides User ID, date time. Our requirement is to check the details for the user ID

tom_wan
Advisor
Advisor
0 Kudos

Hi vikas.sehra2There is no such standard function can check the execution history of debugger directly.

With Audit Log(SM19/SM20) or System Log(SM21), only critical activities of debugger will be recorded. This is explained in notes:

1559742 - Insufficient Logging of Debugger Activities

1411741 - Evaluating debugger events in audit log

Some customer uses ST03N to check who executed debugger: program RSTPDAMAIN. But ST03N is used for recording system load, so it only contains limited information and it might be not 100% reliable.

Regards

Tom