S/4HANA TM Migration: Master Data, Open Freight and Cutover

Key takeaway

Plan TM cutover by reconciling locations, carriers, rates and transportation demand while defining safe ownership for planned, tendered and in-transit freight.

Explanation

📌 KEY POINTS
✅ Segment open objects by execution state — unplanned demand, planned FUs, tendered loads, in-transit shipments each need a different cutover treatment.
⚠️ Don't casually duplicate freight already tendered or physically executing in the new system.
💡 A shipment completed in the legacy system may still need settlement completion after cutover — plan for that in finance too.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SEGMENT BY STATE

Unplanned demand, planned freight units, created freight orders, tendered loads, loaded/departed shipments, unsettled freight — each treated differently

━━━━━━━━━━━━━━━━━━━━
⚠️ 2. THE DUPLICATION RISK

Future demand can usually be recreated/migrated
Freight already tendered or physically executing should NOT be duplicated casually — decide which system stays authoritative until completion

━━━━━━━━━━━━━━━━━━━━
▶ 3. MASTER DATA RECONCILIATION

Location identity, carrier/BP mapping, resources, zones, calendars, charge/rate master data, external IDs
Duplicate locations or missing geocodes distort routes immediately after go-live

━━━━━━━━━━━━━━━━━━━━
▶ 4. DON'T FORGET SETTLEMENT

A shipment completed pre-cutover may still need invoice/settlement completion afterward

━━━━━━━━━━━━━━━━━━━━
▶ 5. REHEARSE REALISTICALLY

Real daily shipment volume, carrier tender windows, warehouse hours — transportation rarely pauses for a migration

✅ CHECKPOINT: name the six execution states that need their own cutover decision.

Real project scenario

A global cutover moved all future deliveries to S/4HANA but also recreated freight orders that had already been accepted by carriers in the old system. Duplicate tenders followed. Classifying objects by execution state eliminated the duplicate ownership.

Common mistakes

Treating every open freight object the same.
Duplicating tendered or in-transit loads.
Migrating unclean location/carrier master data.
Forgetting open freight settlement.
Rehearsing only technical load, not operational carrier windows.

Best practices

Classify by execution state.
Preserve one system of record per shipment.
Clean locations/rates before go-live.
Include settlement in cutover.
Rehearse with production operating hours.

Interview angle

Describe the cutover treatment for unplanned, planned, tendered and in-transit transportation demand.

Practice this lesson

Quick check

1. A project team faces this situation in "S/4HANA TM Migration: Master Data, Open Freight and Cutover": A global cutover moved all future deliveries to S/4HANA but also recreated freight orders that had already been accepted by carriers in the old system. Which action is the most appropriate next step?

2. For Embedded/Decentralized TM, EWM Integration, Migration and Architecture, consider this mapped project scenario from Configuring Transportation Lanes and Zone-Based Determination: During a European rollout, a logistics team noticed that freight orders for a newly acquired customer in a border region were consistently missing mode-of-transport and carrier data, forcing planners to fill in details manually every day. Which response best addresses the underlying risk?

3. For Embedded/Decentralized TM, EWM Integration, Migration and Architecture, consider this mapped project scenario from Architecting Transportation Master Data Governance Across Embedded, Decentralized and S/4HANA Landscapes: A global manufacturer consolidating three regional decentralized TM systems into a single S/4HANA embedded TM instance faced conflicting zone and lane structures per region: one region modeled zones at country level, another at postal-code cluster level. Which response best addresses the underlying risk?

Interview questions

1. A project encounters this situation while working on S/4HANA TM Migration: Master Data, Open Freight and Cutover: A global cutover moved all future deliveries to S/4HANA but also recreated freight orders that had already been accepted by carriers in the old system. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.

Answer it in your own words first, then compare.

2. During cutover migration of historical freight orders and shipments from a legacy TM system into S/4HANA embedded TM with integrated EWM, the migration load is running far slower than planned and risks missing the cutover window. What performance factors would you investigate?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.