Show TOC

Setting ABAP Debugging PreferencesLocate this document in the navigation structure

Context

You can change how the ABAP debugger behaves with the General Settings.

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. Change debugger settings as required. The settings apply to all of your ABAP projects.
    Enable debugging of system programs Mark this checkbox to make ABAP system programs visible in the debugger. If this option is not activated, then the debugger executes code in system programs without displaying the code. The debugger also does not stop at breakpoints in system programs.

    A program is a system program if its Program Status is set to SYSTEM. A system program is part of the ABAP application server infrastructure. It may, for example, work with client-independent tables or run in special clients, such as the system client or the administrative client.

    Always create exception object Mark this option to have the debugger force creation of an exception object even if the INTO ref addition is missing from the CATCH statement.

    In the event of an exception, you can then examine the attributes of an exception object, in order to help you with the analysis of the exception. More on this: Displaying Exceptions.

    Suspend sending of background RFC requests Mark this option to have bgRFC (background RFC) function module calls recorded by the system, but not executed. You can then debug such calls with transaction SBGRFCMON in the integrated SAP GUI. Since bgRFC calls are deleted after execution, suspending their execution is necessary for analyzing them with the debugger.

    In older releases, this option also works for tRFC (transactional RFC) calls. These are held without being executed, so that you can examine them in transaction SM58 in the integrated SAP GUI.

    Enable debugging of automatic construction of shared object areas Mark this option to have the debugger start on entering the process that creates a shared object memory area.
    Show message if breakpoint cannot be set Mark this option to enable or disable warning messages, if a breakpoint that you have requested cannot be set. Breakpoints cannot, for example, be set on some ABAP statements for source code modularization, such as CLASS or PUBLIC SECTION.

    If this option is marked, then you will be warned that you cannot set a breakpoint at such a statement. Otherwise, the warning is suppressed.

    Show message if breakpoint activation conflict occurs Mark this option to get a notification popup if a different person (IDE / project) is using the same debug scope as you do currently. More on this:
Related Information