
In the ABAP Debugger window you can manage the debugger breakpoints, session breakpoints, and external breakpoints that are active in the current debugging session. For example, you can:
List all breakpoints
Create Debugger Breakpoints
Change the type of a breakpoint, for example, convert debugger breakpoints into session breakpoints or external breakpoints.
Deactivate, activate, or delete all breakpoints with a mouseclick.
Give individual breakpoints breakpoint conditions. The breakpoint that has been reached only then becomes active if the related breakpoint condition is fulfilled at that time.
Define a counter that only activates the breakpoint if it is reached again after a certain number of runthroughs.
Persistently save breakpoints and load them into other debugging sessions.
Related functions can be called:
In the menu bar of the ABAP Debugger, as described below.
In the Breakpoints tool od the ABAP Debugger, see Breakpoints Tool.
Setting Debugger Breakpoints
Follow the procedure below:
To set a row breakpoint on a certain source text row, position the cursor on the relevant line and choose .
The system sets a debugger breakpoint,
with the quick info text
Execution Line appears in the indicator margin, and the corresponding line is highlighted.
To define a breakpoint that is effective in certain situations ( "Breakpoint for..."), execute the following steps:
Choose .
A dialog containing a tabstrip appears.

Choose the relevant tab page and enter the data as required.
If you want to enter more breakpoints than the space provided, choose [PICT] with the quick info text
Copy.
The system sets the specified breakpoints and clears the input fields.
Choose Continue.
Save as Debugger Breakpoints as Session or External Breakpoints
When you finish your ABAP debugging session, debugger breakpoints are automatically deleted unless you have explicitly saved them as session or as external breakpoints. Follow the procedure below:
If you want to save line breakpoints as session breakpoints, choose .
All existing line breakpoints that have not been previously saved are saved as session breakpoints.
Breakpoints are saved as external breakpoints for external breakpoints, for example, if you debug a BSP or Web Dynpro application.
If you want to save all line breakpoints as external breakpoints choose .
All existing line breakpoints that have not been previously saved are saved as external breakpoints.
If you have set three line breakpoints and saved them as session breakpoints, and then you create two more line breakpoints and save them as external breakpoints, the first three breakpoints are still saved as session and the other two as external breakpoints. Saving breakpoints as another type does not convert previously saved breakpoints to that type.
Deleting Breakpoints
Execute one of the following steps:
To delete a row breakpoint, position the cursor on the relevant line and choose .
To delete all debugger breakpoints, session breakpoints, and external breakpoints in the current debugging session, choose .
Activate or Deactivate Breakpoints
Execute one of the following steps:
To activate or deactivate a row breakpoint, position the cursor on the relevant line and choose .
To activate or deactivate all debugger breakpoints, session breakpoints, and external breakpoints in the current debugging session, choose .
The system indicates that a breakpoint is inactive by the
icon.