Stepping in the AMDP Debugger

AMDPs are usually nested, which means there are multiple procedures along a call hierarchy. The call stack and the current position within that stack is shown within the Debug view in ABAP Development Tools.

If procedures that run in optimized mode (see also: AMDP Debugger Settings) are part of the call stack, these are gray colored, and it is not possible to show the exact code position of the call. Hence, you will see from which procedure your currently debugged procedure was called, but not the actual line of the call statement. Normal black colored entries indicate procedures in debug mode.

To proceed after reaching an AMDP breakpoint, the following functions for navigating in the AMDP debugger are currently available:

Function	Effect
F8 – Resume	Run to the next AMDP breakpoint or to the end of the program.
F6 – Step Over	Execute the next SQLScript statement. If the next step is a procedure call, run the entire procedure.
Disconnect	Cancel the AMDP Debugger while the debugged application resumes execution, ignoring any intervening breakpoints. Remember Disconnect is available for the main debugger instance.
Terminate	Cancel the AMDP Debugger and the execution of the debugged application (debuggee).