Symptom
Working over a transaction, after pressing 'Enter' or 'Saving', error is raised:
"Log cannot be saved: Object/subobject not specified"
Or below error is raised:
Log cannot be saved: Object/subobject not specified
Message no. BL201
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.
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.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
- SAP R/3
- SAP R/3 Enterprise
- SAP ERP Central Component
- SAP ERP
- SAP Enhancement package for SAP ERP
- SAP Enhancement package for SAP ERP, version for SAP HANA
- SAP S/4HANA, on-premise
Product
Keywords
"Log cannot be saved', BL201, SLG0, SBAL_DB, EXIT_SAPLPC32_001, BAL_LOG_CREATE, MIGO, MIRO, MB01, J1AI, Enhancement, 'user exit', I_S_LOG, E_LOG_HANDLE, I_T_LOG_HANDLE, Maintenance Order, W0017 , KBA , BC-SRV-BAL , Basis Application Log , PM-WOC , Maintenance Order Management , MM-IM-GF , Basic Functions , EP-PCT-MAN-MW , BP for Maintenance Worker , FI-LOC-INF-FI-AA , Inflation in Asset Accounting , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview