Error logs (root cause) · Error Log Root Cause
Primary cause group of an error cascade
- Default severity
- Major
- Finding code:
- CAUSAL_PRIMARY_ROOT_CAUSE
- Engine version:
- 1.1.0
What this finding means
Error Log Root Cause reports this finding with the default severity “Major”.
About the engine: Root causes, affected objects and fix order from SAP message logs (Migration Cockpit, SLG1)
How to fix it
Fix the cause of this group first (see the fix order and the sample objects), then re-run the simulation or load: the follow-up messages of its objects are expected to disappear. Do not work through the follow-up messages individually.
How ERP Preflight detects it
The analysis is deterministic: the same exported files and the same knowledge snapshot always produce the same findings. No SAP system connection is required — you upload exports.
- Engine
- Error Log Root Cause
- Accepted formats
- CSV, TEXT, JSON
- What to export
SAP message log export: Migration Cockpit message log (including the Fiori 'SAPUI5-Export' with Typ, Nachrichtentitel, Nachrichtenklasse, Nachrichtennummer, Datum und Uhrzeit), SLG1 application log or any message table as CSV / TSV / semicolon / pipe (ALV list) text with a header row containing a message type column (Type, Msg Type, Typ, Meldungstyp, MSGTY) and a message class + number (ID / Message Class / Nachrichtenklasse / Arbeitsgebiet + Number / No. / Nummer) or a combined message column (Message: 'CNIF_PI 076'); optional object (Instance, Object Key, Source Record, WBS Element / PSP-Element, Project, Material, Customer, Supplier, Order …), parent (Parent, Superior, Higher-Level, Übergeordnet), migration object and timestamp columns. Without an object column the objects are read from the message texts (source-record groups, framework / wrapper message roles). JSON: an array of message objects or {'messages': [...]} with the same keys.
- Required input
- A message log with a message type column and a message id (class + number or combined)
- Evidence
- Each finding points to the artifact path, line and column, the code snippet and the SHA-256 of the uploaded file. Findings without such a pointer are demoted to confidence UNKNOWN.
- Confidence
- Each finding names the knowledge it relies on (SAP message roles (framework / wrapper / relation messages of Migration Cockpit logs)) and is capped by that source’s verification status.
- Knowledge sources
- SAP message roles (framework / wrapper / relation messages of Migration Cockpit logs) — curated, not verified against the source
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- CriticalParent objects referenced by failing objects are absent from the load
- MinorParent references of objects form a cycle
- MinorErrors without an object key cannot be linked to a root cause
- InfoFollow-up message family (never occurs on its own)