Breakpoints, Watchpoints, and
Checkpoints
The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.

In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, …) is displayed for each breakpoint.
If you
double click the Navigation(
) column, the system will display the
breakpoint in the respective source code.
The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.

In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
In this way,
you can always determine what changes have been made to the monitored
variable. For complicated data structures, such as internal tables or
structures, select the pushbutton „Compare Variables“(
) and choose the Diff tool to compare the old and new variable
values.
In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
