Processing Logpoints at Runtime

You can set dynamic logpoints at any source code line that contains an executable ABAP statement. Along with the dynamic logpoint definition, you can specify logpoint properties such as condition, key definition, and field values.

The key definition and the field values in dynamic logpoints are quite similar to the SUBKEY and FIELDS addition of the LOG-POINT ABAP statement (static logpoints). When an active dynamic logpoint has been set at a certain ABAP source code position, the ABAP runtime evaluates the logpoint whenever the source line is processed. Logpoint evaluation always takes place before execution of the first ABAP statement in that line.

During evaluation of a logpoint, the ABAP runtime first evaluates the logpoint condition. If the condition is not fulfilled (value = false), the ABAP runtime skips further evaluation of the logpoint and continues to execute the ABAP statement. If the logpoint condition is true, then - as a log event - a log entry is written.

Much like with static logpoints, log entries are aggregated by the values found for the key definition.

For example, if the key definition contains the variable SY-UNAME, there will be only one log entry for each user as a result, regardless of how often the individual user requests ran through the logpoint’s source code location.

Aggregated log entries contain a counter, which represents the overall number of log events for the particular logpoint.

During a log event, the content of the variables specified for field values are logged. Aggregated log entries always contain the variable content of the last log event.