ERPClimb logoERPClimb

SAP TM Execution Interview Questions

Interviewers use execution to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

This page carries 20 reviewed SAP TM execution interview questions, each with a complete written answer and no sign-in required. The set breaks down into 5 foundational, 11 mid-level and 4 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.

If you can handle every question here without hesitating, execution is unlikely to be what costs you an SAP TM interview — and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

20 Execution questions with answers

easyExecution

1. In S/4HANA TM, what is the purpose of Loading and Departure execution statuses on a freight order, and how do MM goods movement events at the dock typically influence these status updates?

Loading and Departure statuses track physical progress of freight execution at the dock, feeding operational monitoring dashboards. When integrated with MM, goods issue postings against the outbound delivery can trigger or corroborate the Loading status via status update rules or PPF actions, while Departure is usually confirmed through event messages, EWM confirmations, or manual/carrier updates rather than MM postings alone.
easyExecution

2. In S/4HANA TM, how are MM goods movement postings (e.g., goods issue against an outbound delivery) integrated with freight order execution status updates?

When a delivery-based freight order is linked to an outbound delivery, posting goods issue in MM triggers a status change on the delivery that TM picks up through the delivery-freight order integration, updating the freight order's loading/execution status (e.g., 'Goods Issue Posted'). This does not require Event Management; it uses standard status profile propagation between VL02N/VL06 delivery processing and the TM freight order document flow.
easyExecution

3. In S/4HANA TM, how does the solution support dock appointment scheduling for freight orders, and what role does Event Management play in monitoring appointment adherence?

TM does not natively manage dock appointment slots; it integrates with EWM Yard Logistics or a dock scheduling app to book time slots tied to freight order stops (loading/unloading points). Event Management (or embedded Track and Trace) captures actual check-in/check-out events against the planned appointment window, flags late arrivals or no-shows, and updates the freight order execution status so planners can react to delays or trigger rescheduling.
easyExecution

4. In SAP TM, what is the purpose of Check-In and Check-Out events at a shipping or receiving location, and how do they relate to freight order execution status?

Check-In and Check-Out record the actual arrival and departure of a resource (truck, driver) at a location, typically triggered manually or via yard/gate integration. They update the freight order's execution status and can drive downstream events like loading start or unloading completion. In MM-integrated scenarios, check-in/check-out at a plant gate can be linked to inbound/outbound delivery processing for gate management and dock scheduling.
easyExecution

5. In an S/4HANA Transportation Management landscape, what is the purpose of yard integration and how does it typically interact with Event Management concepts during execution?

Yard integration links TM's transportation orders and freight units with yard processes (often via EWM Yard Logistics) so that truck arrivals, gate check-in, spotting, and check-out are tracked against planned transportation activities. Event Management functionality, delivered through Transportation Event Chains and Event Profiles, captures actual milestones (arrival, loading start/end, departure) and compares them to planned dates, triggering exception handling or status updates in TM when deviations occur.
mediumExecution

6. Which configuration elements determine how Loading and Departure execution statuses are updated on a freight order when integrating with SAP Business Network for Logistics for real-time tracking?

Execution status updates for Loading and Departure are driven by status profiles assigned to the freight order type, mapped event codes, and status determination rules in TM customizing. When integrated with Business Network for Logistics, inbound tracking events (e.g., carrier-reported departure) are mapped via event codes to TM's internal status values, updating the freight order status sequence and triggering subsequent milestones like dock departure confirmation.
mediumExecution

7. What configuration elements govern how execution statuses (e.g., in-transit, delivered) received from SAP Business Network for Logistics are mapped and applied to a freight order's transportation status?

Configuration includes the status profile assigned to the freight order type, status determination rules that map incoming network tracking events to TM execution statuses, and the integration/mapping layer (event codes to status codes) that translates carrier-reported milestones from the network into TM's internal status values. Consultants must also configure event type linkage and ensure the freight order's tendering/collaboration settings allow inbound status updates to be accepted and applied automatically.
mediumExecution

8. A freight order tracks multiple execution milestones via Event Management, and one milestone (goods loaded) should trigger a corresponding MM goods issue confirmation, but the MM posting is not occurring even though the milestone is logged as completed on the freight order. How would you diagnose this?

I would first confirm the Event Management milestone is actually mapped to the specific execution status expected to trigger MM integration, since a logged event doesn't automatically mean the status update fired correctly on the freight order. Next, check whether the freight order-to-outbound delivery link is intact and whether the integration configuration (e.g., automatic goods issue posting rules) is active for that document flow. I'd also verify there's no blocking exception or incomplete predecessor status preventing the MM posting trigger, and review application logs for failed BAPI/IDoc calls between TM and MM.
mediumExecution

9. A freight order's execution status shows the shipment as delivered based on an Event Management milestone, but the corresponding MM goods receipt for the linked purchase order has not posted, leaving inventory understated at the receiving plant. How would you troubleshoot this?

First verify the delivered milestone actually mapped to the correct execution status and that the freight order-to-PO linkage is intact; check whether the event was configured to trigger downstream MM posting automatically or whether goods receipt requires manual confirmation at the plant. Review event rule configuration for the milestone-to-status mapping, confirm the PO and freight order reference the same delivery/shipment, and check for blocked or incomplete goods receipt due to quality inspection or tolerance issues before assuming an integration failure.
mediumExecution

10. Dispatchers rely on freight order execution statuses to know when a truck has arrived at the yard and is ready for loading, but truck arrival milestones captured by the yard system are not reflected as 'Arrived at Yard' status updates on the freight order, even though the carrier is connected via SAP Business Network for Logistics. How would you troubleshoot the missing status update?

Check whether the yard system's arrival event is actually being published to Business Network for Logistics or routed separately, since yard management and carrier network tracking may be distinct integration points that don't automatically converge. Verify the status profile mapping on the freight order includes an 'Arrived at Yard' status tied to the correct event type from Business Network for Logistics, and confirm the carrier's tracking device or check-in process is generating the expected milestone. Review integration logs for message failures between the yard system, network, and TM.
mediumExecution

11. A freight booking's execution status is not updating in SAP TM even though the carrier has confirmed pickup and provided tracking updates through SAP Business Network for Logistics. How would you investigate and resolve this event-to-resolution gap?

First check whether the carrier's confirmation was actually transmitted and mapped correctly through the Business Network for Logistics integration, reviewing message monitoring for failed or unmapped events. Verify the freight booking's event profile is configured to consume the specific milestone (e.g., pickup confirmed) and that the tracking ID/reference numbers match between the network message and the TM booking. If mapping is correct but status still doesn't update, check whether the status profile allows that particular status transition and whether any manual confirmation step is still required.
mediumExecution

12. A freight order receives a valid arrival event from Event Management, but the corresponding goods receipt does not post automatically in MM, leaving inventory understated at destination. As the consultant, how would you diagnose this event-to-MM integration gap?

I would first confirm the event definition and milestone mapping correctly identifies the arrival milestone as GR-relevant, then check whether the freight order's linked purchase order and item are properly referenced in the event's application object. Next, review whether the automated goods movement posting configuration (linked to the milestone) is active and whether the purchase order still has open quantity. Finally, check for exception logs or blocked postings due to tolerance or account assignment errors that would silently prevent the GR.
mediumExecution

13. Walk through how carrier check-in and check-out are handled during tendering execution when integrated with SAP Business Network for Logistics.

After tender acceptance, the carrier or driver performs check-in at the loading point, which is captured through Business Network for Logistics and reflected as a status update on the freight order (e.g., 'Checked In'). Check-out on completion of loading/unloading similarly updates execution status and can trigger downstream events like POD capture. These statuses feed the freight order's execution status profile and can be visualized on the transportation cockpit for dispatchers monitoring yard activity.
mediumExecution

14. Check-In and Check-Out events are being captured correctly at the shipping location for a freight order, but the expected output document confirming carrier arrival (used downstream by SD to release delivery processing) is not generated. How would you troubleshoot this output management gap?

Verify the output determination configuration is linked to the check-in/check-out event as a trigger condition, not just to freight order status changes. Confirm the output type's access sequence and condition records include the relevant partner (carrier) and location, and check that the event actually updates the freight order status field the output condition depends on. Review NAST or the output application log for failed determination, then confirm the SD delivery is correctly referencing the freight order so the output can propagate downstream.
mediumExecution

15. How does integration with SAP Business Network for Logistics update the execution status of rail freight orders, and what should be validated when statuses appear delayed or missing?

Business Network for Logistics enables carriers to submit tracking events (departure, arrival, delays) electronically, which are mapped to TM execution statuses via configured event codes rather than manual status entry. When statuses are missing or delayed, I would check whether the carrier is properly onboarded and connected on the network, that the event mapping configuration translates network events into the correct freight order status, and whether the message actually arrived versus being stuck in an interface queue or rejected due to reference mismatches.
mediumExecution

16. What configuration considerations must be addressed when enabling dock appointment scheduling in a scenario where compliance screening from GTS must occur before a carrier appointment is confirmed?

Dock appointment scheduling configuration must define appointment types, time slots, and resource capacities aligned to the receiving/shipping location, typically integrated from EWM. Where GTS compliance screening is required, the sequencing must ensure that sanctioned-party or embargo checks occur on the freight order or delivery before the appointment status moves to confirmed, so a blocked carrier or partner cannot secure a slot. This usually requires status dependencies or workflow checks tying compliance release to appointment confirmation logic.
hardExecution

17. A freight order already in 'loading in progress' status must be replanned after the assigned carrier reports a truck breakdown, requiring reassignment to a new carrier while an MM-related goods issue is already partially posted. How would you approach this replanning scenario?

I would first assess what quantity has already been loaded and whether a partial goods issue exists in MM, since replanning cannot simply cancel a freight order with posted movements. The freight order would need to be split or adjusted to reflect the already-loaded portion, with a new freight order created for the remaining quantity assigned to the new carrier. Execution statuses must be reset carefully to avoid orphaned statuses, and the new carrier's tendering and confirmation cycle must run again before continuing execution, ensuring MM delivery quantities stay reconciled with TM freight order quantities.
hardExecution

18. Describe how execution events on a freight order (such as loading confirmation or POD) integrate with MM purchase order and goods receipt processes in a plan-to-execute transportation scenario.

When a freight order is created against an MM-driven inbound process, execution events like loading start/end, arrival at destination, or proof of delivery can trigger status updates that feed back into MM through delivery confirmation or goods receipt posting. Typically the freight order references the inbound delivery linked to the purchase order; confirming freight execution status updates delivery status, which MM then uses to release goods receipt processing. Event Management or embedded event handling propagates milestone completion to keep procurement and warehouse teams synchronized on inbound shipment progress.
hardExecution

19. A road freight order created from a purchase order does not update its execution status after goods receipt is posted in MM, leaving planners unable to confirm delivery completion. As the solution architect, how would you diagnose and resolve this?

I would verify the PO-to-TM integration scenario is active and that the freight order's status profile includes a status dependent on MM goods movement events. Then check whether the goods receipt posting actually triggers an event message back to TM through the configured integration (e.g., via the transportation requirement or delivery-based process) and that the event mapping updates the correct freight order status. I would also confirm the freight order is linked to the right delivery/PO reference, since a broken reference silently prevents status propagation, and check for missing customizing of status determination rules.
hardExecution

20. An air freight execution milestone event fails to trigger a corresponding goods receipt posting in MM, delaying inventory visibility at destination. As the solution architect, how would you diagnose the root cause?

I would first confirm whether the milestone event (e.g., arrival at destination) was actually confirmed in TM and whether the event profile is correctly mapped to trigger a status update on the freight order or freight unit. Next, I'd check whether the integration model linking the freight unit to the inbound delivery/purchase order in MM is active and whether the status change is configured to propagate goods receipt-relevant confirmation. Finally, I'd review interface logs or monitoring for failed IDocs or API calls between TM and MM.

Related topics

Integration with EWMFreight SettlementCharge CalculationTransportation PlanningTenderingTransportation Master DataFreight UnitsIntegration with SDEmbedded TM, EWM Integration, Migration and SupportCarrier CollaborationEmbedded/Decentralized TM, EWM Integration, Migration and ArchitectureFreight Orders

Next practice step

Practice with Interview AITake a mock test