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 | BALMSGVSRC |
| Short Description | Application Log: Origin of a message variable |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR15 | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| 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 | Origin |
| Medium | 15 | Origin |
| Long | 20 | Origin |
| Heading | 15 | Origin |
Documentation
Definition
This flag indicates where a message variable comes from (e.g. the request number) when a message is sent to the application log.
This information can, e.g. be used later to replace temporary message variable contents by permanent values.
Example:
Message variable 1 contains the temporary document number $0005 when the message is sent. When this document is saved, the permanent number 12345 is assigned. The value $0005 has little meaning in the log and should therefore be replaced by 12345. This is difficult if the log contains other messages with temporary contents, perhaps even $0005, although this document number is not meant, (e.g. it could be the number of an implicitly created, dependent document).
Specifying the origin of a message variable in this field makes replacement safer, because you know where the contents come from.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
