Data migration load files · Migration Template Intelligence
Schema declared by the migration template
- Default severity
- Info
- Finding code:
- MIG_TEMPLATE_SCHEMA_SUMMARY
- Engine version:
- 1.0.0
This is an informational finding: it confirms a state or documents a change and needs no fix.
What this finding means
Migration Template Intelligence reports this finding with the default severity “Info”.
About the engine: Migration Cockpit load files (templates) validated against their declared schema: mandatory fields, lengths, types, keys, hierarchy
How to fix it
No action required: this is the schema (sheets, fields, types, mandatory and key fields) the template declares and the data was validated against. Check that the migration object and version match the target system's migration project.
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
- Migration Template Intelligence
- Accepted formats
- XML, CSV, TEXT
- What to export
SAP data migration template (Migration Cockpit 'Migrate Your Data' load file): the Excel 2003 XML spreadsheet as downloaded from SAP (all sheets, document properties OBJECT_NAME / VERSION / LANGUAGE, field list) or the CSV of one data sheet including its header rows (as converted from an XLSX by the upload): title row, SAP structure names, SAP field names, the type-specification row ('ETE;80;0;C;80;0'), group names ('Schlüssel' / 'Key') and field descriptions ('*' = mandatory), then the data rows. EN and DE templates.
- Required input
- A migration template data sheet with its type-specification row (XML spreadsheet or CSV)
- 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
- The verdict rests on your artifacts only. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN) that shows how strong the evidence is.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- 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