Ansicht
Dokumentation

BAL_CH_INTRO -

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

|---------------------------------------------------------------------|
| Introduction |
|---------------------------------------------------------------------|

Situations can arise at runtime in an application program which must be brought to the user's attention. These are usually errors, but it may also be useful to report a successful procedure (although the user should not be inundated with unimportant information).

We will not distinguish between exceptions, errors, messages, and so on here. These are all situations in which a particular piece of information (usually a T100 message or a message text for an exception) arises, which is displayed in a log either immediately or later. This information is called a message here.

These messages are not displayed individually (ABAP commands MESSAGE and RAISE) and are collected and displayed together later.

This set of messages is a log. Logs usually also contain general header information (log type, creator, creation time, etc.). A transaction can generate multiple logs.

The application log provides a comprehensive infrastructure for collecting messages, saving them in the database and displaying them as logs. This infrastructure and some conventions are described below.

Technical core and simplified shell
======================================================================

The application log has two levels: a technical core of small, flexible function modules and a simplified shell, which uses core function modules for particular scenarios.

Example:
The technical core contains function modules to search the database (BAL_DB_SEARCH), load logs into memory (BAL_DB_LOAD) and output logs which are in memory (BAL_DSP_LOG_DISPLAY). The simplified shell contains the function module APPL_LOG_DISPLAY which uses the core function modules in this order to display logs which are in the database.

Both core and simplified shell function modules can be used.

The simplified shell function modules are generally the old Release 3.0 application log function modules (beginning with APPL_LOG_...) which internally now call the function modules of the new technical core (beginning with BAL_...).

All function groups are in the package SZAL, the simplified shell function groups begin with SLG..., those of the technical core with SBAL...

If you already use the old application log, you need not change, but only some of the new application log functionality is available in the simplified old shell.

Example:
The (old) function module to display logs which are in the database, APPL_LOG_DISPLAY, has the new Importing parameter I_S_DISPLAY_PROFILE, which describes the log display format (see section Display log). This parameter is passed on to the core.

Naming conventions
======================================================================

The following naming conventions apply to the function modules in the new application log:
Function module names:,,Start with BAL for basis application log
Importing parameters: ,,start with I_
Exporting parameters:,,start with E_
Changing parameters:,,,,start with C_

If the function module parameter is a structure, an S_ follows; if a table, a T_ follows.

Example:
I_S_LOG_HEADER is a function module Importing parameter based on a DDIC structure.

Similar conventions apply to DDIC types: They usually start with BAL_, followed by S_ for structures or T_ for table types.

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 3963 Date: 20240510 Time: 223114     sap01-206 ( 60 ms )