For troubleshooting in a bgRFC, you can use external debugging.
● The user who schedules the unit in bgRFC must have debugging authorization at the time of scheduling.
● The user who wants to debug the unit must have debugging administration at the time of debugging.
The required authorizations are combined in the SAP_BC_WEBSERVICE_DEBUGGER role. This role is available in SAP_BASIS 7.10 SP2 and higher.
The following
general rules apply: If the person scheduling the unit is the same person as
the one who wants to debug it, a bgRFC can always be debugged from the
monitor. In other words, the user can always debug his/her own units.
If the person scheduling the unit and the person debugging it are two
different people, it depends which setting the system is operated with in
accordance with SAP Note 999004:
● If the setting stipulates that the unit is started under the user scheduling the unit, the unit can be debugged (though this setting is not recommended).
●
If the setting
stipulates that the unit starts under the user who is currently logged on, and
this user is not the scheduler, debugging will fail, as switching from
one dialog user (debugger) to another (scheduler) is prevented.
The only option available here is to debug the bgRFC unit using an
external
breakpoint.
You therefore have two options for debugging bgRFC units:
● Directly from the bgRFC monitor
● By setting external breakpoints
You always need to use external breakpoints in the following situations:
● The unit is scheduled and started under two different users
● The status of a unit in the monitor is set to “green” (not locked/does not contain errors)
● You can find a detailed description of the two debugging methods under:
● Debugging with the bgRFC Monitor
● Debugging with External Breakpoints