Show TOC

Setting ABAP Project-Specific Debug Settings Locate this document in the navigation structure

Context

You can use project-specific debug settings to change the user for which ABAP breakpoints are in effect.

Note Debugging SAP public services: HTTP services that are defined under sap/public in transaction SICF are handled without an explicit logon. (They are processed under a special system user). This means that the breakpoints that you set in ADT do not work for debugging of sap/public services; a request does not run under your user, and you cannot set an external breakpoint to catch processes of the special system user. One workaround for debugging such services is to make a copy of your service under a different SICF path, sap/bc, for example. Then requests to the service run under your user, and you can stop in the debugger in your ABAP service handler.

Procedure

  1. Open the debugger preference page. (Choose Start of the navigation path Window Next navigation step Preferences Next navigation step ABAP Development Next navigation step Debug End of the navigation path.)
  2. Choose Configure Project Specific Settings... and choose the ABAP Project for which you wish to change the customizing.
  3. [Optionally:] Specify the validity scope of ABAP breakpoints that have been created in ADT.
    Option Description
    This project only Enables debugging of requests from within this ABAP project only. With this option, you can only debug requests that are started from within this certain project but no external requests (RFC, HTTP).
    Note If this option is chosen you will not experience any issues that are reported in the topic: .

    Logon user Enables debugging of any request for the logon user (default option).

    This means that for server-requests that have been processed on the ABAP server, only the ones running under your logon user (SY-UNAME) are able to start a debug session - if they reach a breakpoint. Requests that are executed under a foreign user will not start a debug session and just ignore the breakpoint. Therefore you will not be able to stop/debug the requests of your colleagues with this option.
    User Enables debugging of any request for the specified user.

    If you want to debug requests of a foreign user you can choose this option and enter the respective user name.

    This allows you to debug also external requests like RFC and HTTP, as long as they are processed under the specified user on the ABAP server.
    Terminal ID Enables debugging of any request with a Terminal ID.

  4. [Optionally:] Use Advanded Settings and mark Allow debugging of tool requests if you are developing ABAP components for ABAP Development Tools itself.
  5. [In case of AMDP debugging: ] You have the option to view or change the settings for AMDP debugging. More on this: AMDP Debugger Settings
Related Information