TM Foundation: Locations, Resources, Transportation Zones and Master Data

Key takeaway

Understand the master data that makes transportation planning possible: locations, business partners, resources, products, transportation zones, calendars and lanes or distances.

Explanation

📌 KEY POINTS
✅ Locations, resources, zones, and calendars have to be coherent BEFORE optimizer tuning matters at all.
⚠️ Never create duplicate locations for the same physical place — it fragments freight demand and corrupts distance/rate results.
💡 Poor master data produces poor planning regardless of algorithm quality — check data first, always.

━━━━━━━━━━━━━━━━━━━━
▶ 1. THE MASTER-DATA OBJECTS

Locations — plants, shipping points, customers, suppliers, ports, other physical nodes
Resources — trucks, trailers, capacity-constrained equipment
Transportation zones — group locations for planning/rate/strategy purposes
Products/packaging, business partners (carriers), calendars, distances/durations

━━━━━━━━━━━━━━━━━━━━
⚠️ 2. THE DUPLICATE-LOCATION TRAP

A plant in ERP must map to the location TM uses
Duplicate locations for the same physical place fragment demand and corrupt distance/rate results

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP (BEFORE TUNING THE OPTIMIZER)

Verify location data and address/geocode quality.
Verify resource capacity and calendar data.
Verify distance/lane data.
Only then look at optimizer settings.

✅ CHECKPOINT: explain why optimizer tuning is the WRONG first step when planning results look bad.

Real project scenario

A plant existed twice in TM under slightly different addresses after migration. Freight units for the duplicate location were not consolidated and route calculations diverged. Master-data harmonization resolved the issue.

Common mistakes

Duplicate locations for one site.
Missing resource capacities.
Ignoring calendars.
Poor geocoding/address quality.
Tuning optimizer before master data is stable.

Best practices

Maintain one location identity per physical node.
Keep capacities realistic.
Govern calendars and distances.
Reconcile ERP/TM identifiers.
Validate master data before planning tests.

Interview angle

Explain which TM master-data objects are required before freight planning can produce feasible results.

Practice this lesson

Quick check

1. In the lesson "TM Foundation: Locations, Resources, Transportation Zones and Master Data", consider this project situation: A plant existed twice in TM under slightly different addresses after migration. Which statement is correct?

2. While applying Architecting Transportation Master Data Governance Across Embedded, Decentralized and S/4HANA Landscapes to Transportation Management Foundation, Organization and Master Data, a team follows this risky pattern: "Assuming ERP plants and customers automatically appear as fully usable TM locations without verifying generation or replication steps.". Which correction is most appropriate?

3. While applying Transportation Zones, Lanes, and Means of Transport in Planning to Transportation Management Foundation, Organization and Master Data, a team follows this risky pattern: "Confusing means-of-transport-type (generic mode) with means of transport (specific capacity-bearing object) during capacity planning setup.". Which correction is most appropriate?

Interview questions

1. Using this SAP project situation — A plant existed twice in TM under slightly different addresses after migration — explain TM Foundation: Locations, Resources, Transportation Zones and Master Data. What should happen, which concepts or process steps matter, and what common mistake would you avoid?

Answer it in your own words first, then compare.

2. Design the master data and integration architecture needed to enforce dangerous goods compliance checks consistently across TM planning and EWM warehouse execution.