ERPClimb logoERPClimb

SAP TM Transportation Master Data Interview Questions

Transportation Master Data is a standard block in SAP TM interviews. It is rarely asked as a definition; it is asked as a situation you have to talk your way through.

Foundational and intermediate coverage of SAP Transportation Management master data objects—locations, transportation zones, means of transport/resources, and transportation lanes—that underpin all planning, tendering, execution, and settlement processes in Embedded TM, Decentralized TM, and S/4HANA deployments.

This page carries 39 reviewed SAP TM transportation master data interview questions, each with a complete written answer and no sign-in required. The set breaks down into 3 foundational, 20 mid-level and 16 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

Treat the answers as a starting structure, not a script. Interviewers in SAP TM rounds follow up on whatever you sound least certain about, so the value is in being able to keep going after the first answer.

39 Transportation Master Data questions with answers

easyTransportation Master Data

1. What is the purpose of Transportation Lanes in SAP TM, and how do they support carrier and route determination during freight unit and transportation proposal creation?

A transportation lane connects a source and destination location (or zones) and defines which means of transport, resources, carriers, and rate conditions are valid for moving goods between them. During planning, the TM optimizer and manual planning use lanes to determine feasible routes, transit times, and default carrier assignments. Lanes can be direct, zone-to-zone, or hub-based, and they carry stage-specific attributes like transit duration and default MoT, driving both cost calculation and carrier selection logic.
easyTransportation Master Data

2. In SAP TM, what is a Resource in the transportation network, and how does it differ from a Means of Transport or a Business Partner?

A Resource in SAP TM represents an executable transportation asset such as a truck, trailer, vessel, driver, or rail wagon that can be assigned to a freight order or freight booking for scheduling and capacity planning. Unlike a Business Partner, which represents a legal or organizational entity like a carrier or customer, a Resource is a physical or personnel asset with capacity, availability, and location attributes used in optimization and scheduling; Means of Transport is a type classification (e.g., truck, ship) used to categorize resources.
easyTransportation Master Data

3. In SAP TM on S/4HANA, what is the purpose of Means of Transport (MTr) master data, and how does it relate to the resource type used for actual execution?

Means of Transport represents the general classification of transport equipment (e.g., truck, rail wagon, vessel type) used mainly for capacity planning, scheduling, and default attribute inheritance such as capacity and transportation modes. Actual execution uses TM resources (vehicle, trailer, driver) which reference the Means of Transport to inherit capacity and compatibility settings, ensuring master data consistency between planning and execution, including EWM-relevant vehicle scheduling scenarios.
mediumTransportation Master Data

4. A regional master data team responsible for maintaining locations and zones reports that their assigned Fiori business role does not allow them to create new transportation zones even though location creation works fine. What would you check to resolve this?

I would check whether the assigned business catalog for the Fiori role includes the specific app or authorization for zone maintenance separately from location maintenance, since locations and zones can be governed by different business catalogs or app-level authorizations even when both are conceptually part of the same network master data area. I would also verify the underlying PFCG role's authorization objects for the zone maintenance function and confirm the MDG-driven replication scope actually includes zone objects for that region if zones are also governed centrally.
mediumTransportation Master Data

5. In an embedded S/4HANA TM deployment, how is carrier master data governed against the vendor master in MM, and which configuration elements link the two?

The carrier is maintained as a Business Partner with a carrier-specific BP role, and is linked to a vendor master record through Customer/Vendor Integration (CVI), which synchronizes BP and vendor data using defined mapping and number range assignments. Configuration includes activating the carrier BP role, assigning it to a vendor account group, and defining CVI synchronization settings so that changes to carrier attributes propagate consistently to the vendor master used for freight settlement and payment.
mediumTransportation Master Data

6. How is the transportation planning organizational structure configured in embedded S/4HANA TM, and how does it relate to purchasing organization data used for freight procurement?

Transportation organization is modeled through organizational units in the enterprise structure (org model), typically representing planning/execution groups linked to company codes and plants. Purchasing organization data (from MM) is referenced during freight order/freight booking creation for vendor selection and contract determination, but transportation org structure itself is maintained separately in the TM org model, not directly derived from MM purchasing org hierarchy. Consultants must map org units carefully to ensure correct authorization and freight settlement routing.
mediumTransportation Master Data

7. A global company uses SAP MDG to govern location master data centrally before distributing it to S/4HANA TM. What integration considerations must be addressed to ensure locations used in transportation zones and lane determination remain consistent and error-free?

Locations governed in MDG must be replicated with all TM-relevant attributes (address, geocoding, time zone, transportation zone assignment capability) via the appropriate distribution model or API, ensuring completeness before TM planning uses them. Key considerations include validation rules in MDG to enforce mandatory geocoordinates, timing of replication relative to zone/lane master data creation, and handling of location changes that could invalidate existing lanes or zone assignments. Governance must define ownership for TM-specific extensions not covered by MDG.
mediumTransportation Master Data

8. An MM procurement team wants inbound transportation lanes from key suppliers to automatically restrict carrier eligibility based on preferred supplier agreements, but planners report that lane-based carrier restrictions aren't being respected during freight unit building for certain purchase orders. How would you troubleshoot this?

Check whether the transportation lane connecting the supplier location to the receiving plant has carrier restrictions maintained at the lane level (e.g., specific carrier assignment or exclusion) versus relying only on general rate conditions. Verify the planning profile used for these purchase orders actually enforces lane-based carrier eligibility during freight unit building rather than allowing broader carrier selection logic to override it. Also confirm the purchase order's ship-from location correctly maps to the lane's source location; a mismatch (e.g., using a different supplier plant code) would cause the lane restriction to be skipped entirely.
mediumTransportation Master Data

9. A carrier is created and maintained centrally in SAP MDG, then replicated to SAP TM as a business partner with a carrier role. Planners report that lane determination fails for shipments to a specific region even though the carrier record exists and looks correct. How would you troubleshoot this issue focusing on Locations and Zones master data?

I would first verify that the carrier business partner replicated correctly includes the carrier role and any location/zone assignments needed for lane relevance, since MDG replication sometimes only pushes core BP attributes and not TM-specific zone assignments. Next, I'd check whether the destination region is correctly represented as a Transportation Zone containing the relevant locations, and confirm the Transportation Lane's zone-to-zone or location-to-zone assignment includes that carrier as a valid means of transport/carrier combination. I'd also check validity dates and hierarchy inconsistencies between zones created manually in TM versus those expected from MDG-driven location data.
mediumTransportation Master Data

10. When configuring locations and zones for a global TM implementation integrated with MDG, what unit-of-measure considerations must be addressed to avoid downstream planning and optimizer errors?

You must ensure that dimension UoMs (weight, volume, distance) maintained on location and zone master data are consistent across the units used by MDG-governed business partner and material data feeding into TM, since mismatched or missing base UoM mappings cause conversion errors in freight unit building and optimizer capacity checks. Configuration should define a consistent measurement system per region (metric vs imperial) and validate that UoM conversion tables in customizing cover all combinations used across sourced/distributed location data.
mediumTransportation Master Data

11. A manufacturer wants to design a transportation zone hierarchy that supports procurement-driven inbound planning integrated with MM purchase orders across multiple plants and regions. What design considerations would you apply to the zone hierarchy?

I would structure zones hierarchically to reflect the geographic granularity needed for carrier selection and freight cost estimation at the plant/region level, ensuring each supplying vendor's location can be assigned to a zone consistent with the receiving plant's inbound transportation lanes. Zone definitions should align with MM source-of-supply and scheduling agreement data so that inbound deliveries created from purchase orders correctly trigger freight unit building, and the hierarchy should avoid overly granular zones that create maintenance overhead without adding planning value.
mediumTransportation Master Data

12. A client wants to onboard a new carrier that will also be paid via FI accounts payable, and the same partner acts as a customer in another business line. How would you structure the business partner and roles to support this in TM, and what risks must you manage?

Create a single Business Partner master record with multiple BP roles: carrier role for transportation planning/execution, vendor role (FI/MM) for accounts payable, and customer role if applicable, all linked via the shared BP architecture in S/4HANA. Ensure role-specific data (bank details, tax data, freight-specific attributes) is maintained correctly and that the vendor role is properly extended for AP postings. Risk areas include duplicate BP creation, inconsistent tax/withholding setup, and unclear segregation for compliance if the same entity has conflicting commercial roles.
mediumTransportation Master Data

13. A logistics company operates in multiple countries with differing public holidays, and planners report that transportation proposals are scheduling pickups on non-working days at certain plants. How would you diagnose and correct the calendar master data setup in SAP TM?

I would first check the factory/working-time calendar assigned to the relevant location (plant/site) master data in TM and confirm it reflects the correct country/region holiday calendar, since TM planning uses calendars linked to locations, not a single global calendar. I'd verify the calendar assignment flows correctly from ERP/MDG-replicated location data, check for outdated or missing holiday entries, and confirm the transportation proposal generation logic references the correct calendar during scheduling. Corrections typically involve updating calendar assignments in location master data and re-triggering replication.
mediumTransportation Master Data

14. What master data and configuration steps are required to define a Means of Transport in embedded TM, and how does this data flow into FI for cost and settlement purposes?

Means of Transport is configured as a resource type in TM with capacity profile, equipment type, and compatibility settings, then assigned to vehicle resources used in transportation unit and freight order execution. Once a freight order is settled, the underlying carrier and equipment references feed into FI via freight settlement documents, linking cost center or profit center assignments from the organizational unit tied to the resource, so costs post correctly against the transportation cost object.
mediumTransportation Master Data

15. A chemical company is extending TM master data to support hazardous goods commodities that require special handling rules during freight unit building and carrier selection. Walk through how you would model products/commodities and enforce these constraints in the transportation network.

Extend the product master (or TM-specific transportation product/commodity data) with hazardous material classification fields (e.g., UN number, hazard class) replicated from MM material master. Configure freight unit building rules to consider hazmat attributes when grouping items, preventing incompatible commodities from being combined. Use carrier profile and resource qualification data to restrict carrier/vehicle selection to those certified for hazmat transport, and incorporate compliance checks (e.g., via GTS or custom BRF+ rules) during tendering to block non-qualified carriers automatically.
mediumTransportation Master Data

16. Describe how Product and Commodity master data maintained for SAP TM supports transportation network design, and where this data intersects with FI for freight cost accounting.

Product master data (transportation-relevant attributes like weight, volume, hazardous class) and Commodity codes define handling, compliance, and packaging requirements used when building transportation networks, lane assignments, and capacity checks in resource planning. These attributes influence charge calculation elements such as freight class or commodity-based scales in freight agreements. When freight costs are settled, cost elements tied to product/commodity attributes flow through freight settlement documents into FI as accounting documents, enabling cost center or profitability segment postings tied to the shipped commodity.
mediumTransportation Master Data

17. Your organization uses SAP Master Data Governance (MDG) to centrally govern location and transportation zone master data before replicating to TM. What integration considerations must be addressed to ensure zone assignments remain consistent across MDG and TM?

Ensure MDG data model includes location coordinates/geocodes and zone hierarchy attributes so replicated business partner locations carry correct zone-relevant fields. Use MDG's distribution model (e.g., via ALE/IDoc or SOA services) to replicate changes to TM, and confirm TM's zone determination logic (postal code ranges, region, country) is fed by governed data rather than manually maintained locally. Establish a change-request workflow in MDG that blocks direct TM-side zone edits to avoid divergence, and implement reconciliation reports to detect drift between MDG source and TM zone assignments.
mediumTransportation Master Data

18. Your client's MM procurement team creates new supplier locations for inbound freight, but TM planners find that transportation planning fails to generate feasible freight units for these new plants. How would you diagnose whether the issue lies in location master data or planning profile configuration?

First verify the MM plant/supplier location was correctly replicated to TM as a business partner location with valid address, UoM, and calendar data. Then check whether the location is assigned to the correct transportation zone used by relevant transportation lanes; missing zone assignment prevents lane determination. Next, review the planning profile used for freight unit building to confirm it references the correct location role (ship-from/ship-to) and that source determination settings include the new location. If location data is correct but lanes/zones are missing, the root cause is master data; if locations and lanes are fine but planning still fails, focus on profile-level source/destination determination logic.
mediumTransportation Master Data

19. A global rollout uses SAP MDG to govern carrier and location master data centrally before distributing it to SAP TM. What design considerations are critical to ensure carrier zone and location assignments remain consistent after distribution?

MDG must govern the location hierarchy (including geo-coordinates and zone-relevant attributes) and carrier BP data with validation rules that prevent inconsistent country/region combinations, since TM zone determination for carrier service area assignment relies on accurate location attributes. Distribution should use a defined replication model so that location and carrier changes reach TM before dependent objects like transportation zones or carrier scales are used in planning, and reconciliation checks should catch cases where MDG-approved data conflicts with existing TM zone hierarchies.
mediumTransportation Master Data

20. When configuring transportation zones and locations for a global SAP TM rollout integrated with MDG, what design decisions ensure consistent zone-to-location assignment across regions?

You define a location hierarchy aligned with business partner and address master data replicated from MDG, then group locations into transportation zones using consistent criteria such as postal code ranges or geographic regions. Governance rules in MDG should enforce naming conventions and mandatory fields before replication to TM, preventing duplicate zones. Zone determination logic in TM should reference standardized region/country codes so lane and area determination behaves predictably across business units.
mediumTransportation Master Data

21. A company ships hazardous materials and wants dangerous goods (DG) classification data maintained centrally in MM material master to flow correctly into SAP TM for freight order compliance checks. What master data integration points must be validated?

Dangerous goods data (UN number, hazard class, packing group) is maintained in the material master DG data and must be replicated to TM, typically via integration with EHS/PLM or embedded DG functionality depending on system landscape, so that freight orders can perform compliance and DG segregation checks. Validation points include confirming DG indicator and classification fields replicate correctly to TM's product master representation, that DG check profiles reference the correct classification data, and that packaging/handling unit data also carries DG attributes for load planning constraints.
mediumTransportation Master Data

22. A procurement team wants to use transportation lanes to control carrier selection for inbound MM shipments from key suppliers. What master data setup is required, and what pitfalls commonly arise when lanes are created without proper coordination with procurement stakeholders?

Transportation lanes must be created between supplier locations and plants, with associated carrier assignments, transportation modes, and validity periods, often linked to freight agreements for rate applicability. Lane data should reflect actual approved carriers per lane and align with procurement's supplier/vendor rate agreements. Common pitfalls include lanes created without valid freight agreements causing rate determination failures, outdated lanes after supplier changes leading to incorrect carrier selection, and lack of coordination causing duplicate or conflicting lane definitions across regions.
mediumTransportation Master Data

23. A global company wants regional planners to maintain transportation zones and locations only for their own business unit, while central logistics IT retains full change authority. How would you design the authorization concept to enforce this segregation?

I would use organizational-level authorization objects tied to business unit or planning group attributes on location and zone master data, restricting regional roles to display and limited maintenance within their assigned scope while granting central IT roles unrestricted change access. Authorization groups on locations combined with structural authorization checks ensure regional planners cannot edit zones outside their business unit. Change history and workflow approval for cross-region changes add an additional control layer, and periodic authorization reviews confirm segregation is maintained as the organization evolves.
hardTransportation Master Data

24. Describe the end-to-end governance process for maintaining carrier master data (business partner, resources, agreements) when the organization also uses SAP GTS for compliance screening.

Carrier master data is created as a business partner with TM roles, extended with resource records (vehicles, drivers) and freight agreements. Governance requires a defined change process where new carriers are screened via GTS sanctioned-party list checks before activation, with periodic re-screening triggered by master data changes. Ownership typically sits with a master data team coordinating with compliance, and activation is blocked or flagged if GTS screening returns a hit, preventing tender or order assignment to non-compliant carriers.
hardTransportation Master Data

25. You are designing an authorization model for resource master data maintenance across multiple regional TM organizations, with a requirement that regional planners can only edit resources in their own region while GTS compliance officers need read-only visibility across all regions. How would you architect this?

I would design authorization roles based on organizational unit or planning group assignment attached to the resource master, using authorization objects that restrict maintenance access by organizational structure element (e.g., planning/transportation group) so regional planners can only create or change resources tied to their assigned org unit, while a separate compliance role is granted display-only authorization across all org units without maintenance rights. This requires resource master data to consistently carry the organizational attribute used for authorization checks, and role design must be validated against segregation-of-duties requirements to prevent cross-region unauthorized edits.
hardTransportation Master Data

26. You are designing master data governance for transportation resources (drivers, trucks, trailers) across a global enterprise that also uses GTS for compliance screening. What architecture would you propose to keep resource master data consistent and compliant?

I would establish a central master data hub, likely MDG, as the authoritative source for resource master records, with governed workflows for creation and change before replication to TM. Compliance-relevant attributes such as carrier and driver identification must be consistently formatted so GTS screening can execute reliably against sanctioned party lists during order or shipment creation. Regional TM instances or business units should consume replicated data rather than maintain resources locally, with periodic reconciliation jobs to detect drift and a clear escalation process for GTS-flagged resources pending compliance resolution.
hardTransportation Master Data

27. A global manufacturer wants transportation lanes to dynamically reflect changing carrier capabilities and SD sales area coverage without manual lane maintenance for every new ship-to location. How would you architect the transportation lane master data strategy to achieve scalability while integrating with SD sales areas?

Architect lanes at the zone level rather than individual location level wherever possible, using transportation zones aligned to SD sales area groupings so new ship-to locations automatically inherit lane coverage through zone-to-zone lane definitions. Use means-of-transport and carrier profile determination rules layered on top of zone lanes to avoid combinatorial explosion of location-specific lanes. Where customer-specific SD conditions require exceptions, define location-specific override lanes sparingly, and use scheduled data quality jobs to validate new SD ship-to locations are correctly geocoded and zoned automatically via BP replication.
hardTransportation Master Data

28. Design a Resource master data architecture for a global TM implementation where truck and trailer resources must be dynamically assigned during EWM-triggered execution while also remaining eligible for GTS export screening at the means-of-transport level. What architectural considerations apply?

Resources should be modeled with clear resource types (truck, trailer, driver) linked to a default Means of Transport, with capacity and compliance-relevant attributes maintained centrally and replicated consistently to any decentralized TM or EWM instance. Since EWM execution may trigger dynamic resource assignment at loading time, resource availability and status must be synchronized in near real time between TM and EWM to avoid double-booking. For GTS screening, resources acting as MoT (e.g., a specific vessel or truck with export restrictions) need their compliance attributes maintained on the business partner or resource master and checked at both planning and execution touchpoints, not just at initial resource creation.
hardTransportation Master Data

29. You are designing the global TM organizational and resource model for a multinational shipper that moves goods across borders requiring export control screening. Means of Transport resources (trucks, vessels, rail cars) must be usable in planning while also supporting compliance checks via GTS. What design considerations and integration touchpoints would you address for Means of Transport master data and GTS?

I would model Means of Transport as TM resources with relevant attributes (capacity, equipment type, ownership) linked to carrier business partners, ensuring resource master data carries identifiers needed for compliance screening (e.g., country of registration, carrier party). GTS integration typically screens business partners (carrier, consignee) and the underlying transportation document/party data rather than the vehicle resource itself, so I'd ensure freight orders/bookings trigger compliance checks against sanctioned party lists before execution release. Design considerations include timing of GTS checks (pre-tendering vs pre-execution), handling blocked resources or carriers, and ensuring resource reusability doesn't bypass screening on each transport leg.
hardTransportation Master Data

30. A multinational client reports that after a regional reorganization merged several SD sales areas, transportation zone assignments for affected ship-to locations became inconsistent, causing some freight units to fail zone-based lane determination entirely. As solution architect, how would you diagnose and fix the transportation zone structure?

Start by comparing the current SD sales area/customer hierarchy against the transportation zone hierarchy to identify locations whose zone assignment references outdated sales area groupings. Check whether zone determination rules or BAdIs used zone codes tied to the old sales area structure, causing orphaned or duplicate zone assignments. Rebuild the zone hierarchy to reflect the merged sales areas, reassign affected locations, and validate that transportation lanes referencing the old zones are updated or recreated. Finally, test freight unit building for a sample of affected ship-tos to confirm lane determination succeeds post-fix.
hardTransportation Master Data

31. For a multinational client with SD-driven order-to-cash and TM-driven transportation, how would you architect the location master strategy so that SD ship-to/ship-from partners align correctly with TM locations without creating duplicate or conflicting master data?

I would design TM locations to be derived from and linked to the underlying business partner and customer/vendor master used by SD, using the standard location type mapping so that a single BP-based location represents the same physical site across both modules rather than maintaining separate, disconnected TM-only locations. Governance should assign clear ownership (typically MDG or a central master data team) for location creation, enforce consistent address and geocoding data, and use location roles to distinguish ship-to, ship-from, and TM-specific planning locations while keeping the underlying BP as the single source of truth.
hardTransportation Master Data

32. A global company uses SAP GTS for export compliance screening, and departure calendars maintained on TM locations control when freight orders can be tendered. After a recent calendar update, GTS compliance screening is intermittently skipped for shipments departing from certain locations on days that were newly marked as non-working in the factory calendar. How would you investigate whether this is a calendar master data issue or a GTS integration configuration issue?

First verify the factory calendar assigned to the location in TM and confirm working/non-working day flags align with actual business operations; incorrect calendar assignment can cause freight orders to be created or rescheduled outside the expected screening trigger window. Check whether GTS screening is triggered by document creation/save events independent of the calendar, or if a custom enhancement ties screening timing to planned departure dates derived from the calendar. Review transportation lane and location calendar consistency, then validate the GTS interface configuration for triggering events versus calendar-dependent scheduling logic.
hardTransportation Master Data

33. Carrier business partner data changes are not reflected in time for outbound shipments, causing SAP GTS compliance checks to run against outdated carrier information. As the solution architect, how would you diagnose and resolve this?

I would first verify the BP change document and replication timing to confirm whether carrier updates are synchronized to GTS via the standard interface or delayed by batch jobs, then check whether GTS compliance checks are triggered before or after the relevant BP change reaches the GTS system. Resolution typically involves reviewing replication scheduling, ensuring critical carrier attribute changes (address, country, blocking status) trigger immediate synchronization, and confirming that compliance re-checks occur if carrier data changes after initial screening rather than relying on a single point-in-time check.
hardTransportation Master Data

34. During go-live, a cross-border carrier's shipments are being blocked at customs clearance despite valid GTS master data, and freight orders show inconsistent carrier resource assignment across regions. As solution architect, how would you diagnose whether the root cause lies in TM carrier/resource master data or GTS integration configuration?

I would first verify carrier BP data consistency (roles, addresses, compliance attributes) and resource assignments (means of transport, capacity) across the affected regions, checking for regional org unit misalignment causing inconsistent resource determination. Then I would validate GTS integration by tracing whether customs-relevant master data (legal control classifications, compliance data) is correctly replicated and whether the block originates from GTS screening results versus TM planning logic. Isolating whether the block occurs pre-shipment (GTS screening) or during resource assignment (TM) determines the fix path.
hardTransportation Master Data

35. In a global TM rollout requiring integration with GTS for customs-relevant transportation, how do resource and schedule master data (e.g., transportation lanes and departure calendars) need to be structured to support compliance checks without disrupting planning performance?

Departure/arrival schedules and transportation lanes must carry accurate location and transit-time data since GTS compliance checks (sanctioned party, embargo, license determination) are typically triggered at freight order or shipment creation using location and partner data. Schedules should be maintained at a granularity that reflects actual customs checkpoints (border crossings) so GTS calls occur at meaningful points, not excessively per leg, to avoid unnecessary API calls impacting planning performance. Master data governance should centralize location/country data via MDG to ensure consistency feeding GTS.
hardTransportation Master Data

36. Describe the end-to-end process of setting up business partners as locations and carriers to support transportation network design, including how conditions (rates) are attached at the business partner level.

Business partners are created with roles such as Carrier, Ship-to, or Location depending on function, using BP transaction with TM-specific roles (e.g., FLTM000, TM carrier). Locations are represented as BP with location role and linked to a geocode; carriers are BPs with carrier role and vendor extension. Rate/condition records (e.g., freight agreements) are attached at BP level using condition technique in the Freight Agreement or Rate Table, allowing rates to be resolved during charge calculation based on carrier, location zone, and transportation mode combinations.
hardTransportation Master Data

37. For a multinational manufacturer with hundreds of ship-to locations across multiple sales organizations, how would you architect the transportation zone hierarchy to balance planning granularity with maintainability, while remaining aligned with SD organizational structures?

I would design a multi-level zone hierarchy, using country/region-level parent zones with more granular sub-zones for high-density areas, mapped to postal code ranges or geographic clusters rather than individual ship-to locations. Zone structure should align conceptually with SD sales areas for reporting consistency but need not mirror them exactly, since transportation zones serve planning/optimization purposes distinct from sales org structure. Governance should limit zone proliferation by setting clear ownership and periodic review criteria to prevent unmanageable granularity.
hardTransportation Master Data

38. In a Global Template rollout to multiple countries on Public Cloud TM, master data such as locations and resources migrated for one country causes duplicate or conflicting EWM integration mappings when the second country goes live. How would you diagnose and prevent recurrence?

I would review the master data migration templates for hardcoded country-specific values that were not templatized correctly, and check integration mapping tables for location/resource identifiers that clash across country instances or organizational units. The fix involves enforcing unique key naming conventions per country/rollout wave in the global template design, validating mappings in a sandbox before each wave, and adding automated duplicate-detection checks in migration validation reports.
hardTransportation Master Data

39. For a multi-carrier network with negotiated freight agreements, how should freight agreement master data (rate tables, validity periods, scales) be architected to support both tendering and EWM-triggered execution scenarios without creating rate conflicts?

Freight agreements should be structured with clear validity periods and scale-based rate tables tied to specific transportation lanes, carrier, and business share allocations to avoid overlapping applicability. For EWM-triggered execution (e.g., outbound delivery-based freight order creation), the agreement determination logic must resolve to a single applicable agreement using selection settings (e.g., most specific lane/carrier combination) to prevent conflicting rates. Governance should include periodic validity checks and clear tie-breaking rules in charge calculation to avoid ambiguous rate selection during high-volume execution.

Related lesson

Configuring Transportation Lanes and Zone-Based Determination

Related topics

Integration with EWMFreight SettlementTransportation PlanningCharge CalculationTenderingFreight UnitsIntegration with SDEmbedded TM, EWM Integration, Migration and SupportCarrier CollaborationExecutionEmbedded/Decentralized TM, EWM Integration, Migration and ArchitectureFreight Orders

Next practice step

Practice with Interview AITake a mock test