Show TOC

Starting the Classic DebuggerLocate this document in the navigation structure

Procedure

There are two possible strategies for starting the Debugger in the ABAP Workbench:

  • By setting breakpoints then running the program

  • By running the program in debugging mode.

Setting Breakpoints

A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, see Breakpoints.

Direct Processing

You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:

From the Object Navigator

Select a program or transaction and choose Start of the navigation path Program Next navigation step Test Next navigation step Debugging End of the navigation path.

In the ABAP Editor

Choose Start of the navigation path Program Next navigation step Execute Next navigation step Debugging End of the navigation path (or the Debugging pushbutton). In the source code display, you need to select the menu Start of the navigation path Program Next navigation step Test Next navigation step Debugging End of the navigation path.

From any screen

Choose Start of the navigation path System Next navigation step Utilities Next navigation step Debug ABAP End of the navigation path.

From any screen

Enter /h in the command field.

Checking System Programs for Errors

To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose Start of the navigation path System Next navigation step Utilities Next navigation step Debug System End of the navigation path from any screen. To stop the system Debugger, choose Start of the navigation path Debugger Next navigation step Debugging off End of the navigation path.

Displaying Program Attributes

You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Start of the navigation path Goto Next navigation step Further Information Next navigation step Program Attributes End of the navigation path.

Restarting the Debugger

If you choose Start of the navigation path Debugging Next navigation step Restart End of the navigation path, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Start of the navigation path Debugging Next navigation step Restart End of the navigation path will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose the menu Start of the navigation path Program Next navigation step Execute Next navigation step Debugging End of the navigation path or choose the Debugging pushbutton.

Switching Between the Single-Process and Two-Process Debugger

As of Release 6.40, you can preset the call for the new Debugger in the ABAP Editor by selecting the menu Start of the navigation path Utilities Next navigation step Settings Next navigation step Debugging Next navigation step New Debugger End of the navigation path. In the debugging mode, you can switch from the single-process Debugger to the Two-Process Debugger through the menu option Start of the navigation path Debugging Next navigation step Switch to New Debugger End of the navigation path.