LOG-POINT ID group
[FIELDS val1 val2 ...].
This statement defines a logpoint whose activation is controlled via the addition
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 to, a counter for the entry is increased. The log can be evaluated using transaction SAAB.
No log entry is written for an inactive logpoint and the program execution proceeds with the statement after
... ID group
ID controls the activation of the logpoint from outside the program via a
group or an
For the specification of the checkpoint group, the same rules apply as to the
ASSERT statement.The possible operations modes for logpoints are active and logging.
... SUBKEY sub
When you specify
SUBKEY, the content of
stored as sub-key in the log. Already existing log entries of the same
statement are only overwritten if the sub-keys have the same content. Without specifying
SUBKEY, the sub-key is initial.
sub is a
position of which the first 200 characters are evaluated. An expression or function specified here is executed only if the log point is active.
... FIELDS val1 val2 ...
After the addition
FIELDS, you can specify a list of values
val1 val2 ... (no reference variables) that are used in the log.
val1 val2 ... are
functional operand positions at which data objects or functional methods can be specified. The methods are executed only if the log point is active.
The size of each data object saved in the log with the
FIELDS addition is restricted by the
abap/aab_log_field_size_limit. The value of the profile parameter specifies
the size in bytes. The default value is 1,024. The value 0 means there is no restriction. When a log
entry is generated, the content of each data object is truncated when this limit is reached, and full lines are removed from internal tables.