Show TOC

Request-Based Debugging - ConceptLocate this document in the navigation structure

Use

The following steps are executed in order for request-based debugging:

  1. Set one or more external breakpoints.

  2. Send off the request to be rested.

In this way both external breakpoints and requests to be tested are given a special flag, a terminal ID. The ABAP Debugger only starts when the terminal ID of the current request matches the external breakpoint that has been reached.

Note

The end user who sets the breakpoints will later execute the debugging. This is usually the same end user who later sends off the request to be tested. But these can also be different users.

Note

In the context of request-based debugging the term 'end user' refers to a specific Microsoft Windows user with which you are logged on the frontend PC while working with the AS ABAP.

General Rules

The following general rules apply:

  • A terminal ID identifies the Microsoft Windows user who is logged on to the frontend PC while working with the AS ABAP. It is saved in the Windows Registry of the frontend PC.

  • The terminal ID of the end user who sets the breakpoint is used for request-based debugging.

  • The terminal ID is specified in the user session where the breakpoints are set. It is read implicitly from the Windows Registry of the frontend PC. If it not there then it is generated when request-based debugging is activated and stored in the Windows Registry. It remains valid even when the Microsoft Windows user logs on to this frontend PC again until it is deleted manually from the Windows Registry.

    Note

    The registry key is: HKEY_CURRENT_USER\Software\SAP\ABAP Debugging

  • Breakpoints set in the following are automatically identified with the terminal ID of the current end user.

  • The end user who then sends requests must actively associate the outbound requests with the terminal ID (see Procedure).

  • If a request that is flagged with a terminal ID is processed over multiple ABAP systems, then the associated terminal ID is automatically forwarded on. By already setting an external breakpoint with the same terminal ID, the initial request to be tested can be processed over multiple systems before it arrives at the AS ABAP. Debugging is then activated, if necessary.

Technical Requirements

All AS ABAP systems that are involved identify SAP NetWeaver Release 7.02 or higher or 7.11 or higher.