An open reference for the S/4HANA migration objects almost every project needs.
The migration objects almost every project needs
SAP publishes the list of available migration objects. What it does not publish in one place is what you actually need on a project: which staging structures a given object generates, which fields are genuinely mandatory, what the T-code equivalent is when you have to fix something by hand, and which Fiori app proves the load was correct. This page is that reference, built from the objects we load on real ECC to S/4HANA projects.
Three ways data reaches S/4HANA
The Migration Cockpit supports more than one route, and the choice changes what your ETL layer has to do. Availability per object and per approach varies by release — always check the object list for your own release before committing scope.
Staging tables
The cockpit generates one table per source structure in a HANA schema. You fill them with any ETL tool, then simulate and load. The only realistic option for high volumes, complex transformation or repeated test cycles.
File (XML template)
Download a spreadsheet template per object, fill it, upload it. Excellent for small objects and for letting key users own their own data. Poor for anything above a few thousand rows or with real transformation logic.
Direct transfer from SAP
Read straight from a supported SAP source system with no file in between. Fast where it fits, but the object coverage is narrower than staging and the source system needs the prerequisite add-on and release level.
What each entry gives you
Every object below expands into the same structure, so you can compare objects rather than re-learn a new layout each time.
Structures and fields
The staging structures the object generates, their cardinality, the classic ECC source tables that feed them, and the fields with ABAP type, key flag and mandatory flag.
Deployment and approach
Whether the object exists in public cloud, private cloud and on-premise, and which transfer approaches it supports.
T-codes and Fiori apps
What to use to view, edit and mass-edit the result. T-codes apply to private cloud and on-premise; the Fiori apps work in both cloud editions and are how you validate a load.
Extensibility and pitfalls
How to add customer fields in each deployment model, and the failure modes we actually hit — including the silent ones that only surface weeks after go-live.
Browse the objects
Search matches object names, components, staging structures, field names, table names, T-codes and Fiori apps. Filter by module or by deployment model, then expand an object for the full detail.
34 objects
Need this applied to your own data?
Knowing the field list is the easy half. Extracting, transforming and reconciling it against the legacy books is where projects run long. That is the part we do.
Compiled from SAP standard behaviour and our own project experience. Object availability, staging structure names and mandatory fields vary by S/4HANA release, activated scope and your own customizing — always verify against the migration object list and templates in your own system. Fiori app names change between releases; app IDs are deliberately omitted. This reference is provided for information and does not replace binding advice.