Authorization object for debugging in SE37

[Former Member]

I have given the S_DEVELOP authorization to one of our user. But he is not able to debug a function module. Do I have to give any special authorization for him to debug in SE37. Can you please let me know what is that authorization object for allowing him to debug in SE37

Thanks!

Surya.

[jurjen_heeck]

I believe S_DEVELOP with the combination of ACTVT 03 and OBJTYPE DEBUG will do the trick.

[Former Member]

Jurjen,

I have checked the S_DEVELOP object and I have checked both 01 and 03. Please advice me.

Thanks!

Surya.

[Former Member]

Jurjen

Yes that is correct, however be sure NOT to allow this in PRD as it is a security risk when debug is combined with SE16/30/31. All table data can be changed in debug mode!

[Former Member]

go to tx. SU02 and check on profile S_BI_DEBUG (SAP standard profile). I added this today to search for a bug in a programm. it worked.

[Former Member]

and yes - it sounds like BI only, but isn't.

[jurjen_heeck]

As far as I know you do not need 01, just 03.

Are you still getting authorization failures?

[Former Member]

I am still getting the authorizations issue. I have given the SU53 authorizations for this user and when I chacked whats failing. There is a red mark on

Activity 03

Object Type Debug

But my S_DEVELOP object, Field Name ACTVT

I have checked, 03(Display), 16(Execute)

and I see all the tabs green in my pfcg role.

Please advice me.

Thanks!

Surya.

[jurjen_heeck]

And which object types are in this S_DEVELOP object?

(I'll be offline for the rest of the day soon, so maybe someone else can take over?)

[Former Member]

Try activity 03 (to set the breakpoint) and 90 (for the debugger) placing the name of the external session user ID in the object_name field, and ensure that the external user type is SERVICE for the debugging session.

The system might be blocking the debugging because the user type is Dialog (or the developer is entering their own user ID into the single step).

Cheers,

Julius

[Former Member]

Julias,

Instead of specifying the t-code SE37, I have added the authorization object S_DEVELOP manually and specified the ACTIVITY field values as 03 and 16 and I could debug now.

Thanks!

Surya.