Migration & Clean Core
SAP migration templates: mandatory fields, keys and hierarchy
Migration Template Intelligence reads a Migration Cockpit template (XML spreadsheet or the CSV of a data sheet), derives the schema it declares and validates every data row against it — with the record keys the load will report.
Detected by:Migration Template Intelligence
Documented problems
- BlockerDuplicate record key
MIG_TEMPLATE_DUPLICATE_KEY
- BlockerHierarchy references form a cycle
MIG_TEMPLATE_HIERARCHY_CYCLE
- BlockerHierarchy parent is not part of the load
MIG_TEMPLATE_HIERARCHY_PARENT_MISSING
- CriticalReferenced record is missing on the parent sheet
MIG_TEMPLATE_CROSS_SHEET_REFERENCE_MISSING
- CriticalMandatory template field is empty
MIG_TEMPLATE_MANDATORY_FIELD_EMPTY
- CriticalValue does not match the field type declared by the template
MIG_TEMPLATE_TYPE_MISMATCH
- CriticalValue exceeds the field length declared by the template
MIG_TEMPLATE_VALUE_TOO_LONG
Informational findings
These findings confirm a good state or document a change. They are listed for completeness and are not problems.
- InfoSchema declared by the migration template
MIG_TEMPLATE_SCHEMA_SUMMARY
Terms used in this area
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.