ASSERT , BREAK-POINT , LOG-POINT ) can be activated or
deactivated from the checkpoint group. An activation setting consists of
the following components:
Validity area - Checkpoints specified in the checkpoint group or
compilation unit
Context - User and/or application server specified
Operation mode - System behavior of the various checkpoint types
(assertions, breakpoints, or logpoints)
If the checkpoint statements are activated from the compilation unit,
then the association with a specific checkpoint group no longer has any
meaning.
Latest notes: If the checkpoint statements are activated from the
compilation unit, it is necessary to specify a checkpoint group, since a
checkpoint statement without the addition ID is always active.
The validity period of activation settings with active operation modes
is limited.
Example ABAP Coding See Checkpoints and Checkpoint
Groups .
ABAP_ADDITION_2 ... SUBKEY sub
What does it do? The addition SUBKEY only takes effect if the
statement ASSERT writes entries to a log. If SUBKEY is
specified, the content of sub is stored in the log as a subkey.
Any existing log entries of the same ASSERT statement are
overwritten only if the subkey has the same content. If SUBKEY is
not specified, the subkey is initial.
sub is a character-like
expression position of which the first 200 characters are evaluated.
An expression or function specified here is evaluated only if the
assertion is active and the logical expression is false.
ABAP_ADDITION_3 ... FIELDS val1 val2 ...
What does it do? After the addition FIELDS , a list val1 val2
... of any values (except reference variables) can be specified. If
the statement ASSERT writes entries to a log, the content of the
data objects val1 val2 ... is included in the log. If an
unhandleable exception is raised, the content of the first eight
specified data objects is displayed in the associated
short dump . The addition FIELDS is
ignored when a jump to ABAP Debugger is performed.
val1 val2 ... are
functional operand positions at which data objects or functional
methods can be specified. The methods are executed only if the assertion
is active and the logical expression is false.
If the FIELDS addition is specified, the CONDITION
addition must be specified before the log_exp logical expression.
Latest notes: The log to which assertions write is not the system log to
which breakpoints write during
background processing . It is a
special log that can be read in transaction SAAB
.
If functional methods are specified after SUBKEY and FIELDS
, code for formatting log entries can be executed only after an
assertion is violated.
ABAP_ADDITION_4 ... CONDITION
What does it do? The CONDITION addition triggers the logical
expression. It has to be specified before log_exp if one of the
other additions is specified; otherwise, it can be omitted.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved