topic Re: Debug authorization in S_DEVELOP in Application Development and Automation Discussions

Debug authorization in S_DEVELOP

Former Member — Wed, 07 Jan 2009 09:05:06 GMT

Hi,

I am working on ECC 6.0

I need authorization to debug an RFC session in our production environment. I checked the authorization details for S_DEVELOP (all fields are given '*' including 'ACTVT') . The same authorizations exist in Quality and Development, there i can debug the RFC session.

Can anybody please let me know why i could not debug in production even though the authorizations are same as in development and quality.

When I checkd the documentation for S_DEVELOP, it stated that for object DEBUG there are some separate activaties in which '90' is for debugging HTTP and RFC sessions. If this is so how to maintain this. Are these activities are different from the activities in S_DEVELOP.

Thanks.

Re: Debug authorization in S_DEVELOP

Former Member — Wed, 07 Jan 2009 09:24:22 GMT

Please refer the OSS note 668252 [click here|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=668252]

Re: Debug authorization in S_DEVELOP

Former Member — Wed, 07 Jan 2009 09:37:05 GMT

Hi Praveena,

Please have a look in the below link

http://help.sap.com/saphelp_nw70/helpdata/EN/de/6b0d9cf34d11d3a6510000e835363f/frameset.htm

Use DEBUG /PROG as Development object type

regards

Anand.M

Re: Debug authorization in S_DEVELOP

Former Member — Wed, 07 Jan 2009 09:39:05 GMT

The note is very useful. But in my system for external debugging it is given as '90 copy' instead of '90 transfer'. I changed the activity, but still i am unable to debug in production.

Re: Debug authorization in S_DEVELOP

Former Member — Wed, 07 Jan 2009 09:48:23 GMT

You can also protect dialog type users from being debugged using the user type itself, and but the authority to be debugged (as this is checked for the user who is doing the debugging).

To achieve this, set the paramater profile abap/ext_debugging_possible to 1.

This might have been done in your system (you can check it in RZ11).

If this is the case, then for the user ID you are setting the external break-point for (or terminal-point), make sure it is of the type 'SERVICE' in its own logon data tab in SU01.

Another possibility is that someone else is currently debugging. Then the system will tell you to have a coffee and come back later (or similar message :-).

Cheers,

Julius