Main Keyboard Shortcuts When Working with the ABAP Debugger

In this note, I’ll go over the main keyboard shortcuts used in the ABAP debugger and describe a few actions that can be useful during debugging in general.

The most common and simple way to start debugging is by entering the system command /h. This command should be executed before you plan to start debugging. For example:

Debugging can also be initiated through other interesting techniques.

See also:

• How to start ABAP program debugging for a user?
• How to set an external breakpoint for a user?
• SAP Workflow. Debugging Background Tasks

In some ABAP programs, a popup window may appear. If you want to start debugging right after that popup appears, you need to create a simple text file with the following content:

[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand

Then drag and drop this file onto the popup window in the ABAP program.

Use F5 to step through the program line by line, including into function modules, class methods, conditions, etc. For example:

Use F6 to skip over code blocks. For example, if you're at a function module call, F6 will execute the FM and show the result without stepping into it.

Use F7 to return to the main program from the depths you've entered using the other step functions. For example:

F8 will continue execution until the next breakpoint or the logical end of the program. For example:

Shift + F12 allows you to jump to a specific line in the code, skipping over code that won’t be executed. For example:

To make a breakpoint persistent across debugging sessions:

1. Start the debugger
2. Navigate to the desired line
3. Set a breakpoint
4. Press Ctrl + S to save it
5. Restart debugging

If you frequently view the same set of variables, you can pin or save them in the watch panel to avoid adding them every time. Just press the Save button after adding them. For example:

See: How to Set a Watchpoint for a Variable in the ABAP Editor?

See: How to start ABAP program debugging for a user?

To see the call stack that led to the current point in the code, open Desktop 2.

See: Layout of the User Interface

You can also navigate through the call stack, which is very handy.

Admittedly, not the most elegant title. But you may have encountered this layout issue when launching the debugger in a new system, and the layout looks “off.”

This layout can be annoying. To fix it, follow the guide in:

See: Designing Work Areas

To quickly search through component controller methods in a Web Dynpro app without opening each method, go to SE80 → Utilities → Settings…

See: The Controllers of a Web Dynpro Component

Then go to the Web Dynpro tab and uncheck Method-Based Editor.

This will allow faster navigation. There's also a video showing the before/after effect.

See: New ABAP Debugger

That was awesome! Thanks for your time and attention. Hugs, ignatov.