Message log
SAP message log (application log, Migration Cockpit messages)
Also known as: application log, SLG1
The list of messages an SAP process writes while it runs — for example the application log (SLG1) or the messages of a Migration Cockpit run.
Each message has a message type (E error, W warning, S success, I information; A and X terminate the process), a message class and a three-digit message number that together identify the message text, and usually the object it refers to.
One cause rarely produces one message: when an object fails, the objects that depend on it fail as well, and generic follow-up messages accompany the specific one. Reading such a log row by row means reading the same cause many times.
In ERP Preflight
Error Log Root Cause reads a message log export (CSV, text or JSON) and reduces it to the primary root causes with the affected objects, the exact log rows and a fix order; it does not interpret message texts.
Problems that involve Message log
- MinorErrors without an object key cannot be linked to a root cause
- BlockerDuplicate record key
- BlockerHierarchy references form a cycle
- BlockerHierarchy parent is not part of the load
- CriticalReferenced record is missing on the parent sheet
- CriticalMandatory template field is empty
- CriticalValue does not match the field type declared by the template
- CriticalValue exceeds the field length declared by the template
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.