How to debug using External Breakpoint

[former_member321825]

Hello,

I am using external breakpoint in system B.

I am running a program in systemA which updates table in systemB through programB.

I am using RFCuser to login to system B.

Currently it is not going in debugging mode in program B.

KIndly suggest what needs to be done?

[Former Member]

Debugging is USER specific..

[SuhaSaha]

>

> I am using RFCuser to login to system B.
> Currently it is not going in debugging mode in program B.

Hello Rachel,

Can you check the "user type" of the RFC User in system B? If this is "Communiucation User" i don't think you can debug.

BR,

Suhas

[Former Member]

You need to do the following.

1. Identify the userid you are using for the RFC session.

2. While in the ABAP editor, go to Utilities->Settings

3. Ensure that you are in the tab 'Abap Editor'

4. Under the tab 'Abap Editor' go to the tab 'Debugging'

5. Ensure that the user name entered there is the one identified in step 1.

6. Set the external breakpoint

7. Logon to the target system.

At this stage, when you start the external transaction, it should stop where you set the breakpoint.

[brad_bohn]

But as Suhas has already pointed out, you can't do that with a comm or system user.

Rachel, you either need to switch the logon to a dialog user, or you need to use another method of analysis. Logpoints are good for recording data transfers in a readable format. An RFC destination trace from SM59 is also good but the logs aren't as user friendly as logpoints. Web services have the best data trapping with the SICF recorder.

[Former Member]

Hi,

set a break point for the line for debug.

type /h in command prompt,

press execute.

regards

Dinesh s

[brad_bohn]

set a break point for the line for debug.
type /h in command prompt,
press execute.

That isn't debugging with external break-points...re-read the question...