LESSON 3 / 32
Checkpoint: Scope and Sequence the Migration
Reading · Reinforce the preceding demonstrations.
What belongs in the initial load
Use this supplementary reading to consolidate the preceding videos. A practical migration cycle is extraction, cleansing, transformation, loading, and verification; apply it separately to configuration, master data, and transactional data as relevant.
Define the target operating start point before extracting data. SAP S/4HANA Migration Cockpit is designed for an initial load, not continuous replication. The normal scope is required master data, balances, open items, and open transactions; closed-process historical transactions do not belong in the cockpit load.
- Confirm the migration object exists for the exact SAP S/4HANA release and chosen approach.
- Load prerequisite master data before dependent transactional data.
- Freeze or tightly control source changes, then reconcile the final extraction to the source.
A 2022-specific tool check
For SAP S/4HANA 2022, the cockpit supports staging tables and, for eligible SAP sources in on-premise scenarios, direct transfer. File templates feed the staging-table approach; they are not a separate third approach in this release family.
Treat every template and object definition as release-specific. A field, dependency, or object available in another release is not proof that it exists in your 2022 system.
Progress is saved only in this browser, not to your account. On a shared device, other users may see these marks.
Understand the process
Plan and execute SAP S/4HANA migrations using Migration Cockpit, LSMW and practical cutover controls.
Follow the course contents to move through the lessons in order.