Today I’ve received a great tip by SAP Netweaver consultant Frans van Gelderen regarding checkpoint(s groups).
Checkpoints define points in a program, at which the state of the program can be tested during program execution. You can activate and deactivate checkpoints as well as break points from outside of the program by assigning them to a checkpoint group via the transaction code: SAAB.

A checkpoint group is a repository object which can be used to group and activate checkpoints. The activation settings of a checkpoint group are valid for all checkpoints assigned to the group. Checkpoints are either conditional and unconditional.

Conditional checkpoints are defined by ASSERTions (as seen by the screengrab below),

unconditional checkpoints by BREAK-POINTS or LOG-POINTS.

The ASSERTION statement defines an assertion. You can specify any logical expression for log_exp. When the program reaches an active assertion, the logical expression is evaluated and the program execution continues from the statement after ASSERT only if the result of log_exp is true. After an inactive assertion, the logical condition log_exp is not evaluated and the program execution continues at the statement after ASSERT.

The BREAK-POINT statement defines a breakpoint. The addition ID controls the activation. Without the addition ID, the breakpoint is always active.
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.

The LOG-POINT statement defines a logpoint whose activation is controlled via the addition ID.
When the program reaches an active logpoint, an entry is created in the log that is also used by the statement ASSERT and the program execution proceeds with the statement after LOG-POINT. During this process, an already existing entry of the same LOG-POINT statement is overwritten by default. Each time an entry is written, a counter for the entry is increased. The log can be evaluated using transaction code: SAAB.