Application Log: Log: Create with Header Data
ctionality
The function module BAL_LOG_CREATE opens the Application Log whose
header data is in the Importing parameter I_S_LOG_HEADER, which has the
structure BAL_S_LOG.
The function module BAL_LOG_CREATE returns the log handle (LOG_HANDLE,
CHAR22).
The LOG_HANDLE is a GUID (globally unique identifier) which uniquely
identifies a log. You can access this log with this handle, for example,
to subsequently change the header data ( BAL_LOG_HDR_CHANGE) or to add a
message (BAL_LOG_MSG_ADD) or an exception text (BAL_LOG_EXCEPTION_ADD)
to the log.
The LOG_HANDLE has its permanent value straight away, so it remains
valid after saving.
==>Note:
Logs in memory and in the database are referred to in the new
Application Log by the log handle (LOG_HANDLE), but the previous
LOGNUMBER, which is assigned from number range interval 01 of number
range object APPL_LOG when you save, still exists. A lot of applications
have a reference to this LOGNUMBER in their structures, so it is still
supported. The LOGNUMBER is also more understandable for users than the
LOG_HANDLE. There is a 1:1 relationship between LOG_HANDLE and
Related function modules
Simple log creation call
Methods of collecting messages
BAL_DSP_LOG_DISPLAY displays the collected messages. It can be called
without parameters, in which case all messages in memory are displayed
in a standard format (this standard format is also used in the
transaction SLG1).
==>Note
The log handle is optional for function modules such as BAL_LOG_MSG_ADD,
BAL_LOG_MSG_CUMULATE, BAL_LOG_MSG_ADD_FREE_TEXT, etc.
If it is not specified, the default log, which can be set, with other
default data, with BAL_GLB_MSG_DEFAULTS_SET is used. If no default log
is defined, it is set automatically by BAL_LOG_CREATE (see here).
The 'Application Log' is a tool for collecting messages, saving, reading
and deleting logs in the database, and displaying logs. It is introduced
and described in the following documentation.
Bluesky
