Debugging ABAP Code

Prerequisites

Debugging of ABAP code in ABAP Development Tools at least requires:

721 Kernel version
SAP NetWeaver Release 7.31 SP04 for ABAP backend.

Context

The ABAP Debugger in the ABAP Development Tools can satisfy most of your debugging requirements. Start the debugger by setting a breakpoint in your code and then running the ABAP program.

The debugger offers, among other features

External Breakpoints in the Debugger: Characteristics, so that you can capture external calls via HTTP or RFC into the ABAP back end system in the ADT debugger
Displaying and Changing Variables
Displaying Exceptions
Navigating in the Debugger
Direct editing in the debugger, so that you can correct a mistake right when you find it, as well as many other comfort and efficiency features
Setting and Managing Breakpoints in the debugger.

It's an ABAP debugger, but the look, feel, and functionality are all Eclipse, with all of the comfort and feature-richness that one associates with Eclipse. For a quick orientation to the Debug perspective, follow this Debug View.

For special purposes – other than observing running code – you may still want to use the ABAP Debugger in the ABAP back end system. For more information see Comparing ABAP Debugging in the Back End System and ABAP Development Tools.

Starting methods and function modules in the debugger

Procedure

You can start ABAP PROGRAMs directly with F8.

You cannot start methods and function modules directly - you can run them only from their test beds. (F8 on a method or function module opens the test bed in the integrated SAP GUI.)

Note It's therefore often helpful to set up ABAP Unit tests for starting these programs. You can set up the ABAP Unit test with representative data, and capture the class or function module in the debugger when you run the ABAP Unit test.