topic Re: Debugging in our user while user executes in another user in Application Development and Automation Discussions

Debugging in our user while user executes in another user

former_member242512 — Thu, 23 Jun 2011 12:45:50 GMT

Hi All,

I have authorization to debug and change values runtime debugging in a client.

I dont have authorization for transaction code J*** for which i need to debug.

Is it possible that another user logon which have authorization can execute the j*** tcode

and through my user logon i will put break point in standard code and program will be debugged for that user.

Note the two users are different.

Kindly help is this is possible.

Re: Debugging in our user while user executes in another user

Former Member — Thu, 23 Jun 2011 12:49:29 GMT

hello,

no the break point will not be visible for other users, but you could enter /h comand in comand line (on top left corner of the screen there you are entering tcode name). before entering final step/action enter /h push enter button and for example post document save changes and so on, debugging mode'll be generated.

best regards,

dez_

Re: Debugging in our user while user executes in another user

Former Member — Thu, 23 Jun 2011 13:01:40 GMT

Hi,

You can debug the code with different types of Breakpoint concepts.

External Breakpoint.

Session Breakpoint

BREAK-POINT

or using /H command

Session and external breakpoints are w.r.t User(SY-UNAME). if you have devloper access, you can hardcode the code BREAK-POINT in the requied line and debug the tcode. if you code like BREAK-POINT USERID ,then it will be only for mentioned userid. if only BREAK-POINT then, all the users will be accessing this breakpoint.

Final option and easiest way of debugging irrespective of user is using /H command.

Regads,

Shreyansh

Edited by: shreyansh babagond on Jun 23, 2011 6:52 PM

Re: Debugging in our user while user executes in another user

Former Member — Thu, 23 Jun 2011 19:18:02 GMT

If the user ( who has authorization to j*** tcode ) doesn't have the authorization to debug, he/she will not be able to debug.

Re: Debugging in our user while user executes in another user

Former Member — Fri, 24 Jun 2011 06:10:56 GMT

Hi,

Go to SE93 and enter your J*** tcode and check what is the program name attached to the tcode.

Then, go to SE38(ABAP Editor) and enter the program name and check what is the issue or you can execute the program by keeping breakpoint. Please check in this way and let me know.

Regards,

Shreyansh

Re: Debugging in our user while user executes in another user

former_member242512 — Fri, 24 Jun 2011 06:18:59 GMT

Hi All , thanks for your replies. As per the replies im concluding that if the two users are different the breakpoint needs to be hardcoded externally in the abap code .. Thanks.

Re: Debugging in our user while user executes in another user

Former Member — Fri, 24 Jun 2011 06:24:55 GMT

HI,

If you put Session/External Break-point it wont stop for other users logons.

It is restricted only to your user logon.

If your breakpoint needs to stop for all users then you need to hardcode

the word 'BREAK POINT' only. But since, this is a standard code, this option

is ruled out.

You can do any of the below:

1) try to call the J*** tcode from FM CALL_TRANSACTION_FROM_TABLE and check

whether it opens, if so, you can debug.

2) Take the other person logon and debug J***. if other person is not having debug

authorization, goto tcode SRDEBUG, select the other person username

and Activate Debugging. So that debug option will be available in J***.

thanks,

Padma

Re: Debugging in our user while user executes in another user

former_member608468 — Tue, 09 Nov 2021 09:38:23 GMT

Hello ,

I believe this will be helpful in this scenario.

if anyone needs to debug any transaction triggered by other user an as a developer may follow below steps-

1. Set external debugger into the code

2. Go to Utilities ->Settings

3.Under ABAP editor main tab locate sub-tab Debugging

Here , enter the user name from which Transaction is to be executed.

4.Save the setting.

This will allow developer to debug any report/program statements executed by another user.

Thanks and Regards,

Abhishek Kokate