ABAP - Keyword Documentation →  ABAP - Reference →  program editing →  Testing and Checking Programs →  Checkpoints → 

BREAK-POINT

Quick Reference

Syntax

BREAK-POINT { [ID group]
            | [log_text] }.

Extras:

1. ... ID group

2. ... log_text

Effect

This statement defines a breakpoint. The addition ID controls the activation. Without the addition ID, the breakpoint is always active.

Breakpoints in Dialog Processing

If the program reaches an active breakpoint in dialog processing, the execution of the program is interrupted and ABAP Debugger is opened. An inactive breakpoint is ignored and the program execution continues with the statement after BREAK-POINT.

Breakpoints in Background Processing

In background processing, program execution is not interrupted. When the program reaches a (permanently) active breakpoint (the addition ID is not used), the entry "Breakpoint reached" is written to the system log along with the program name and the location of the breakpoint in the program. Activatable breakpoints (where the addition ID is used) are ignored. The program execution continues in both cases with the statement after BREAK-POINT.

Breakpoints in Updates

During synchronous and asynchronous updates in an update session, the behavior depends on the setting of the ABAP Debugger:

In local updates, a breakpoint behaves as in dialog processing.

Breakpoints in RFC Processing

In RFC processing, an active breakpoint is applied and the ABAP Debugger displayed in SAP GUI whenever an RFC dialog interaction is possible. The ABAP Debugger in the ABAP Development Tools (ADT) can also be displayed if no dialog interaction is possible.

Breakpoints in ICF Processing and APC Processing

In ICF processing and APC processing, an active breakpoint is applied and the ABAP Debugger displayed in SAP GUI only when external debugging is enabled. When programs or procedures are called in ICF processing and APC processing, they are executed in the context of the service context and their breakpoints behave accordingly.

External debugging can be switched on for a limited time period (by default two hours) using transaction SICF or by setting an external breakpoint in ABAP Editor. If external debugging is not switched on, the breakpoints behave as in background processing. The ABAP Debugger in the ABAP Development Tools (ADT) can also be displayed if external debugging is not enabled.

Breakpoints in ABAP Daemon Processing

In ABAP Daemon processing, an active breakpoint is applied and the ABAP Debugger displayed in SAP GUI only when external debugging is enabled. This also applies to non-dialog users and in callback routines.

Breakpoints in System Programs

In system programs, system modules, system subroutines, and system function modules whose name begins with %_ , the statement BREAK-POINT is only respected if system debugging is switched on in ABAP Debugger (this is done in the Settings menu or by entering "/hs" in the command field of the system toolbar). Otherwise, breakpoints are ignored.

Notes

Example

Breakpoint between two program sections.

*Program section
...

BREAK-POINT.

*Program section
...

Addition 1

... ID group

Effect

The following applies when using the addition ID:

Example

Specifies a breakpoint whose behavior is specified using the checkpoint group DEMO_CHECKPOINT_GROUP.

BREAK-POINT ID demo_checkpoint_group.

Addition 2

... log_text

Effect

A supplementary text can be entered for the system log in log_text. log_text is ignored in dialog processing. In background processing and during the update task, the contents of log_text in the system log are inserted between the words "Breakpoint" and "reached". log_text expects a flat character-like data object with a length of 40 characters. If a data object of type string is specified, it is ignored.

Example

Breakpoint with a text specified for the system log.

TYPES log_text TYPE c LENGTH 40.

DATA(log_text) = CONV log_text( |in program { sy-repid }| ).
BREAK-POINT log_text.



Continue
BREAK-POINT - interner Zusatz