What does it do? This statement defines a static logpoint> whose activation is controlled by the addition ID>. Once 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 continues with the statement after LOG-POINT>. During this process, any 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. BEGIN_SECTION VERSION 5 OUT The log can be evaluated using transaction SAAB>> END_SECTION VERSION 5 OUT . No log entry is written for an inactive logpoint and the program execution continues with the statement after LOG-POINT>.
Latest notes:
In addition to the static logpoints defined using LOG-POINT>, dynamic logpoints can be defined using the transaction SDLP>> or in the ABAP Development Tools (ADT)>.
Logpoints are only intended to be used for test purposes using transaction SAAB>>. There is no API for importing the logged data, which means that logpoints are not suitable for general logging purposes. ABAP_HINT_END • ID LOG-POINT
ABAP Addition
What does it do? The addition ID> controls the activation of the logpoint from outside the program using a checkpoint group> group> BEGIN_SECTION VERSION 5 OUT or an activation variant> END_SECTION VERSION 5 OUT . The same rules apply when specifying the checkpoint group as to the statement ASSERT>>. The possible operation modes for logpoints are inactive> and logging>. • SUBKEY LOG-POINT
ABAP Addition
What does it do? If SUBKEY> is specified, the content of sub> is stored in the log as a subkey. Existing log entries of the same LOG-POINT> statement are only overwritten if the subkeys have 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 executed only if the logpoint is active. • FIELDS LOG-POINT
ABAP Addition
What does it do? After the addition FIELDS>, a list of values val1 val2 ...> , except for reference variables, can be specified that are included in the log. val1 val2 ...> are functional operand positions> in which data objects or functional methods can be specified. The methods are executed only if the logpoint is active.