SAP ABAP Message Class BL Message Number 201 (Log cannot be saved: Object/subobject not specified)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-BAL (Application Component) Basis Application Log
⤷
SZAL_COMMON (Package) Generally-Available Objects
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-BAL (Application Component) Basis Application Log⤷
SZAL_COMMON (Package) Generally-Available Objects 
Attribute
| Message class |  |
BL | |
| Short Description |  |
Application Log | |
| Message Number |  |
201 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20110908 |
Message Text
Log cannot be saved: Object/subobject not specified
Help Document
Diagnosis
Log save cancelled because at least one log contains no object or subobject.
Object and subobject are needed to classify application logs because there are several log types. Only a few logs are managed in main memory at runtime, so this classification is not needed.
If the logs are to be saved in the database, object/subobject must be specified for later retrieval.
System Response
Procedure
Procedure for System Administration
Object/subobject can be passed when a log is created (function module BAL_LOG_CREATE) and changed with BAL_LOG_CHANGE.
The possible values for object and subobject must be configured in transaction SLG0.
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in |
