Application log objects are defined in the system. The object definition assigns a work area. An object can be divided into sub-objects.
Logging is performed object-specifically, via function modules.
An object log entry has the following structure:
The log data are initially collected in local memory, and are then written to the database. This procedure speeds up processing and reduces the number of database accesses. It is also possible to write log data to the database individually, to avoid losing the log records collected up to that point in the event of termination of the application, for example if the system crashes.
The logged data can be read in the database and displayed on the screen. It is also possible to read and to display the log data which is buffered in local memory with a log number (Message collector).
The logs have an expiry date, by which time at the latest they must be in the database. They can later be removed from the database again, by a delete program.
Detailed information, either for the whole log or for each individual log message, can be saved in two ways:
When the log is analyzed either the text module with the specified parameters is displayed, or the user exit is performed, on request.
Additional information can be saved in an INDX-type table, which is used by the user exit analysis.
In this way it is possible, for example, to save lists which can be displayed when the log is analyzed, with the help of the user exit.
Classifying attributes can also be specified (importance of the log, or of the message).
If you want to perform your own log analysis, you can use the function modules to read from the database or from local memory.
Logs can be deleted if necessary.