Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-BAL (Application Component) Basis Application Log⤷
SZAL (Package) R/3 Central Basis Development: Application Log
Basic Data
| Data Element | BALAUTH |
| Short Description | Application Log: Authorization |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SYSUUID_22 | |
| Data Type | CHAR | Character String |
| Length | 22 | |
| Decimal Places | 0 | |
| Output Length | 22 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Authoriz. |
| Medium | 15 | Authorization |
| Long | 20 | Authorization |
| Heading | 25 | Authorization |
Documentation
Critical functions such as configuration (function module BAL_GLB_CONFIG_SET) and initialization (function module BAL_GLB_MEMORY_REFRESH ) should normally only be performed by the mother program. Lower level routines should not perform these global activities.
Problems can occur when a lower-level routine calls the initialization module, for example because this routine was not originally intended to be called in this context.
You can avoid such effects with authorizations:
The mother program (the first program to have control) can get an authorization at the start with the function module BAL_GLB_AUTHORIZATION_GET, which returns a unique key in E_AUTHORIZATION.
The critical functions can only be performed by specifying the key I_AUTHORIZATION. If I_AUTHORIZATION is not specified, or has the wrong value, the action (e.g. initialize memory) is refused. BAL_GLB_AUTHORIZATION_GET can not be repeated, so you cannot get a second key.
You can return the key with BAL_GLB_AUTHORIZATION_RESET (specifying the key).
All the above function modules can then be called without authorization.
The following function modules require authorization:
BAL_GLB_AUTHORIZATION_GET
BAL_GLB_AUTHORIZATION_RESET
BAL_GLB_CONFIG_SET
BAL_GLB_MEMORY_REFRESH
BAL_GLB_MSG_DEFAULTS_SET
BAL_STATISTICS_GLB_SET
==>Note
To remove the data of a single log from memory use the function module BAL_LOG_REFRESH, which does not require authorization as it only affects one log and not the entire function group memory.
==>Note
Your programs should allow for the fact that an action can be refused and not assume successful performance.
- ==>Example
It is common to initialize memory, call a function and then look for errors in the log. This shifts program exception handling to the log tool, which is not its purpose.
You should not do this because the messages collected by the Application Log and memory reset can be controlled externally, so you cannot control which messages are in the log.
Further information
Overview of the most important function groups
Quick start documentation
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
