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

BREAK-POINT

Other versions: 7.31 | 7.40 | 7.54

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:

If ABAP Debugger is not set to update debugging, a breakpoint behaves as in background processing.
If ABAP Debugger is set to update debugging, a breakpoint behaves as in dialog processing. The update is executed in a dialog work process of the current AS Instance.

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 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

A breakpoint in SELECT loops can raise an exception due to the loss of the database cursor. This is because a database commit may be triggered during debugging.
Breakpoints that are always active are used solely for test purposes and are not permitted in production programs. The statement BREAK-POINT without the addition ID therefore causes an error in the extended program check.
BREAK followed by a user name is not a statement, but a predefined macro.
The statement BREAK-POINT defines a checkpoint that is part of an ABAP program. In the ABAP Editor and ABAP Debugger, you can set and manage the following breakpoints without changing the source code:

Session breakpoints
are set in ABAP editor. Session breakpoints are valid in all ABAP sessions of the current user session.

External breakpoints
are set in ABAP Editor or in transaction SICF. External breakpoints have the same validity as session breakpoints, but remain valid for other user sessions when the current session is ended. This makes them particularly well suited for debugging RFC, ICF, and APC processing.

Debugger breakpoints
are set in the ABAP Debugger window. They are valid for the current debugging session and for all internal sessions and ABAP sessions of the debuggee. Debugger breakpoints can be saved as external breakpoints.

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:

In dialog processing, activation from outside the program is controlled by a checkpoint group group or an activation variant. The rules that apply to the statement ASSERT also apply when the checkpoint group is specified. However, only inactive or break can be chosen as operation mode.
In background, update, ICF, and APC sessions without external debugging, the breakpoint is always inactive if the addition ID is used.

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