Object migration library

SAP Data Migration Object Library

Migration guidance for SAP ECC and S/4HANA objects including the Business Partner model, material and vendor masters, view-based loading, Migration Cockpit objects and reconciliation.

How SAP accepts data

Load order and mechanism apply across every object on this platform.

1. 1Choose the load path per objectThe SAP Migration Cockpit covers standard objects with predefined migration objects and templates; IDoc and BAPI interfaces suit transactional and integration-shaped loads; LSMW remains in older estates. The choice is made per object before mapping is built.
2. 2Establish the enterprise structureCompany codes, chart of accounts, controlling area, plants and organisational units. Nothing transactional can be posted against a structure that does not exist.
3. 3Load master data before transactionsBusiness partners, materials and G/L masters first, because transactional postings resolve against them and SAP will reject a posting whose master record is missing.
4. 4Respect check tablesEvery coded field validates against its check table. Values not present in the target's configuration are rejected outright, so crosswalks are proven before the load rather than during it.
5. 5Post transactional dataOpen items and balances, in the sequence the target's own validations require, with document types and posting keys mapped to the target configuration.
6. 6Work the error log per objectRejections carry object-specific reason codes. They are categorised, corrected in the transformation rules and reprocessed, which is the loop rehearsal cycles exist to shorten.