User-based debugging is a variant of external debugging. User-based debugging makes it possible to interrupt and debug the processing of HTTP requests and RFC requests on an AS ABAP. The validity range of external breakpoints can be restricted as follows:
An external breakpoint can be valid for all user sessions of a specific user of the AS ABAP.
If the program is running in the user session of another user, then the breakpoint is ignored - the program execution is not interrupted.
New in AS ABAP under SAP NetWeaver 7.0 EHP2 and 7.2: An external breakpoint can either be valid in the entire AS ABAP or only on the application server where it was set.
User-based debugging is therefore intended for the following cases:
External requests are distributed using load balancing mechanisms on the application server of the AS ABAP.
The user where the request to be tested is to be processed is known.
No general system user is involved.
General Procedure
Proceed as follows to implement user-based debugging:
Log on to the AS ABAP that is to be used for checking HTTP or RFC requests.
The AS ABAP user that you used to log on to the AS ABAP with, and the user of the AS ABAP that is to process the requests that are to be checked should both be available using the Rights for Debugging.
Open the Object Navigator ( SE80 or the ABAP Editor ( SE38).
Choose
.In the screen area ABAP Debugger, ensure that the new ABAP Debugger os the standard Debugger of the current user session: Select the radio button New Debugger.
In the Debugging External Requests screen area, specify the required debugging variants:
Specify user-based debugging as the debugging variant: Select the User radio button.
Specify the user for whose session external breakpoints are to apply. Enter the user name in the entry field to the right of the User radio button.
Specify whether external breakpoints are to be activated in the entire AS ABAP or only on the current application server:
External breakpoints are valid in the entire AS ABAP as standard: The Current Application Server Only checkbox is not selected.
Alternatively, external breakpoints can only apply for those application servers where you are currently logged on. For this, select the Current Application Server Only checkbox.
If a request is processed on another application server then the debugger also does not stop if the user matches that user that was set for the breakpoint.
Apply the settings: Choose Transfer (Enter).
Open the source code of the program to be tested in the ABAP Editor ( SE38, SE80, SE37, SE24,…) and set external breakpoints. See External Beakpoints for this.
New external breakpoints, as well as all those previously set by the current user, are flagged according to the debugging variant that was last selected (user-based debugging here) and their related settings (the user for whose sessions the breakpoints is valid). Related information appears in the status row of the ABAP Editor:
Do not log off from the AS ABAP. This retains the dialog session in which the breakpoints were set so that the ABAP Debugger can start later within the framework of this session.
The requests to be checked can only be sent using HTTP or RFC to the AS ABAP.
After executing the program has achieved an external breakpoints and the conditions of the user-based debugging are fulfilled, the ABAP Debugger starts in the new main mode of the dialog session where the breakpoint was set. The ABAP Debugger window is focussed and you can check and control the remaining program process flow as normal and then cancel the debugging session.