Transportation Management Foundation, Organization and Master Data
TM Foundation: Locations, Resources, Transportation Zones and Master Data
Understand the master data that makes transportation planning possible: locations, business partners, resources, products, transportation zones, calendars and lanes or distances.
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.
TM Master Data Governance and Network Design
Design scalable TM master data for global networks, balancing location granularity, resource classes, zones, calendars and distance/rate structures without creating unnecessary planning complexity.
A global rollout created one zone per postal code even though carrier rates were defined by broader regions. Rate master volume exploded with no planning benefit. Consolidating zones reduced complexity dramatically.
Interview questions covered
- Design the master data and integration architecture needed to enforce dangerous goods compliance checks consistently across TM planning and EWM warehouse execution.
- What deployment options exist for SAP TM functionality within an S/4HANA landscape, and what are the key architectural implications of choosing embedded TM versus a decentralized TM system?
- Your organization is implementing MDG to govern location and business partner master data feeding into TM's transportation network, with a downstream requirement to post freight costs to FI. What governance and integration design points must you address?
- What Fiori business roles are typically delivered or configured for SAP TM in S/4HANA, and how do they map to the main TM user personas such as transportation planner and freight settlement clerk?
- You inherit an existing Transportation Management Foundation, Organization and Master Data implementation covering TM Master Data Governance and Network Design. What would you review before changing it, and what would make you confident the change is production-ready?
- 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?