Key Definition in Logpoints

Similar to the SUBKEY addition of the (static) LOG-POINT statement in ABAP, the key definition in dynamic logpoints is used for aggregation of the result set. While in static logpoints the SUBKEY has to be specified using a single character-like ABAP data object, in dynamic logpoints you can specify a list of data objects. For the key definition of the dynamic logpoint, you can enter a list of ABAP data objects (including literals), which are valid at the current source code position at runtime. The particular data objects in the list have to be separated by a SPACE or comma. In addition, you can specify special built-in functions, which may be called to execute a specific functionality (for example: trace). Each built-in function has a specific return value that is added to the key definition.

A syntactical validation of the given key definition is performed, when the dynamic logpoint is created.

Logpoint events with identical KEY values are aggregated into one and the same log entry (result). A new log entry will only be created after the key value has changed.

More on this: Processing Logpoints at Runtime

Restriction Do not use references, internal tables, or deep structures in the key definition as they cannot be converted into a STRING representation. The resulting key of a dynamic logpoint is built by concatenating the STRING representation of all specified data objects in the key definition. The STRING representation of each data object is determined by following the ABAP conversion semantics.

Examples:

	

  sy-uname sy-host
				
  name,street, city zip_code

  stack_hash( ), sy-uname