Show TOC

Background documentationStarting New ABAP Debugger Locate this document in the navigation structure

 

You start the ABAP Debugger by calling or terminating the ABAP program to be tested in a specific way. Follow the procedure below:

  1. If you have not done so already, log on to the AS ABAP.

  2. The use that you logged on to the AS ABAP with should have Debugging Rights.

  3. ABAP Debugger should be configured as the standard debugger for your user (this is the default setting). You can check it in the following way:

    • Open the Object Navigator (SE80) or the ABAP Editor (SE38).

    • Choose   Utilities   Settings   ABAP Editor   Debugging  .

    • In the ABAP Debugger screen area, select the New Debugger radio button.

    There are many ways to start the ABAP Debugger. The actual procedure depends on the use case. You have the following options:

Procedure

Typical use

Start and ABAP program and set it directly under the control of the ABAP Debugger.

The ABAP Debugger controls the execution of the program from the first row onwards.

Starting and directly debugging function modules, methods, and executable programs (such as transactions and batch jobs) that can be started in the ABAP Workbench in the context of the current user session. You can:

  • Debugging a program from the first row.

  • Debugging program sections where you don't know the source code very well and therefore don't know where it makes sense to set breakpoints.

For more information, see Starting and Directly Debugging ABAP Programs.

Jump directly to the ABAP Debugger while executing an ABAP program. It is not necessary to set breakpoints.

The ABAP Debugger controls further execution of the program.

Stopping and debugging:

  • Dialog applications with Dynpro-based interfaces that run in the context of the current user session

  • Running processes and background jobs

  • Waiting, rolled-out main modes

You can:

  • Directly explore inconsistencies that occur when executing a program.

  • Debugging program sections where you don't know the source code very well and therefore don't know where it makes sense to set breakpoints.

For more information, see Jumping Directly to the ABAP Debugger While Executing a Program.

Set breakpoints in an ABAP program and then execute the program.

ABAP Debugger starts after the program execution has reached a breakpoint.

The ABAP Debugger controls further execution of the program.

Stopping and debugging ABAP programs where you know the source code and which does not run in the context of background jobs or monitoring.

Depending on which user the program to be tested it executed for, there are different types of breakpoints and procedures for stopping and debugging:

  • ABAP programs that are start and executed in the context of the current user sessions (local debugging).

  • ABAP programs that are called using HTTP or RFC (external debugging, external breakpoints).

    Note Note

    Processing an RFC or HTTP request always takes place in the context of a new user session.

    For more information on external debugging, see External Debugging (HTTP and RFC Debugging).

    End of the note.

For further information about the different types of breakpoints and how to use them, see Breakpoints and Breakpoint Statements.

Starting the ABAP Debugger triggers the following actions:

  • Executing the program to be tested is canceled.

  • The ABAP Debugger starts in a main mode of the current user session (local debugging) or in the user session where the breakpoint was set (external debugging).

  • The control goes over to the ABAP Debugger. The inputer-ready window of the ABAP Debugger is displayed.

  • You can now control the further execution of the program using the ABAP Debugger. Use the tools offered in the ABAP Debugger window for this.

  • In the new Debugger, control can be passed from the application to the new Debugger at any time using the function code /h, even if the Debugger was already started.

Note Note

Maximum six main modes are offered in each user session by default. If no other main mode is available when starting the new ABAP Debugger, a message appears and the classic ABAP Debugger starts. You should close main modes you no longer require to be able to work with the new ABAP Debugger. The maximum number of main modes in a user session can be controlled by the adiminstrator using profile parameters of each application server.

End of the note.

Note Note

System programs are excluded from debugging by default and are executed without being stopped.

End of the note.