BREAK-POINT

Short 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 during dialog processing, the execution of the program is interrupted and the ABAP Debugger is opened. An inactive breakpoint is ignored and the program execution continues with the statement after BREAK-POINT.

Breakpoints in background processing

During background processing, the program execution is not interrupted. If the program reaches a breakpoint, the entry "Breakpoint reached" is written to the system protocol under which the program name and the location of the breakpoint in the program are recorded. An inactive breakpoint is ignored. The program execution continues in both cases with the statement after BREAK-POINT.

Breakpoints in updating

During synchronous and asynchronous updating, the behavior depends on the setting of the ABAP Debugger:

• If the ABAP Debugger is not set to update debugging, a breakpoint behaves as in background processing.
  
• If the ABAP Debugger is set to update debugging, a breakpoint behaves as in dialog processing. To do this, the update is carried out in a dialog work process on the current application server.
  

During local update, a breakpoint behaves as in dialog processing.

Breakpoints in HTTP-Sitzungen

In HTTP sessions (BSP),the system only stops at an active breakpoint and goes to the ABAP Debugger if external debugging is switched on. External debugging can be switched on for a limited time period (by default two hours) via transaction SICF or by setting an external breakpoint in the ABAP Editor. If external debugging is not switched on, the breakpoints behave as in background processing.

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 considered if the system debugging is switched on in the ABAP Debugger (via the menu settings or via entering "/hs" in the input field of the system toolbar). Otherwise, all breakpoints are ignored.

Addition 1

... ID group

Effect

When using the addition ID, note:

• Without the addition ID, the breakpoint is always active. When the addition ID is used, the activation of the statement is controlled from outside the program by a checkpoint group group or an activation variant. The same rules apply to the specification of the checkpoint group and the activation settings as to the ASSERT statement. However, you can only choose between inactive and break as operation mode.
  
  
• When using the breakpoint with the addition ID during background processing, during update in the update work process, and during HTTP sessions without external debugging, the breakpoint is always inactive.
  

Without the addition ID, the breakpoint is always active.

Addition 2

... log_text

Effect

In log_text, a supplementary text for the system log can be specified. During dialog processing, the specification of log_text has no effect. During background processing and during the update task, the content of log_text in the system log is inserted between the words "Breakpoint" and "reached". For log_text, a flat, character-type data object with a length of 40 characters is expected. The specification of a data object of the type string is ignored.

Notes

• A breakpoint in SELECT loops can cause an exception through the loss of the database cursor. The reason for this is that, during debugging, a database commit could be triggered.
  
• In the ABAP Editor and in the ABAP Debugger, dynamic breakpoints can be used and managed without changing the source code. These are effective, at maximum, to the end of a user session.
  
• A breakpoint that is always active is used solely as a test help and is not allowed in productive programs. The BREAK-POINT statement without the ID addition therefore causes an error in the enhanced program check.
  
• BREAK, followed by a user name, is not a statement, but a predefined macro.