ERPClimb logoERPClimb

SAP TM Integration with SD Interview Questions

Integration with SD comes up in SAP TM interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

This page carries 24 reviewed SAP TM integration with sd interview questions, each with a complete written answer and no sign-in required. The set breaks down into 2 foundational, 16 mid-level and 6 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.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for integration with sd.

24 Integration with SD questions with answers

easyIntegration with SD

1. What SD configuration determines whether a sales order item automatically generates an Order-Based Transportation Requirement (OTR) in TM, and which item category and requirement type settings control this?

The relevant sales order item category must have the transportation relevance indicator set, and the requirement type/schedule line category must be flagged for TM integration so that upon order save the system triggers OTR creation via the integration model. Copy control and item category group also influence whether transportation-relevant data (weight, volume, dates) is passed to TM for OTR generation.
easyIntegration with SD

2. What is an Order-Based Transportation Requirement (OTR) in SAP TM, and how does it get created from an SD sales order to trigger freight unit building?

An OTR is a TM document representing transportation demand derived directly from a sales order line item, used when transportation planning happens before delivery creation. It is generated via the TM integration model (transportation-relevant items flagged on the sales order), transferred through PI/CPI or embedded integration, and TM's freight unit building rules convert the OTR into one or more freight units based on grouping, item category, and scheduling settings.
mediumIntegration with SD

3. After go-live, planners report that the shipment confirmation output for freight orders is not reaching the SD delivery process, causing goods issue to be blocked downstream. How would you troubleshoot this output management issue?

I would start by checking whether the PPF action for the shipment confirmation output is actually triggering on the freight order by reviewing the action log; if the action is not firing, I would verify the start condition against the current execution status. If the action fires but the message fails to reach SD, I would check the integration/queue monitor for errors in the interface between TM and the delivery document, and confirm partner and output type configuration are correctly mapped to the receiving system.
mediumIntegration with SD

4. A customer wants Incoterms captured on the purchase order in MM to automatically determine freight cost responsibility and carrier selection logic in TM. What master data governance and integration considerations must be addressed?

Incoterms location data must be maintained consistently and governed so the same code and location combination exists in both MM and TM master data, since TM freight cost responsibility and carrier eligibility rules can reference Incoterms in condition determination. Governance should define who owns Incoterms location values, ensure they replicate correctly with the purchase order data to TM, and validate that condition records or business rules referencing Incoterms are updated whenever new codes or locations are introduced to avoid incorrect cost allocation or carrier assignment.
mediumIntegration with SD

5. When configuring output management for freight bookings so that an SD-relevant confirmation output is generated automatically upon a specific execution event, what configuration components must a consultant set up?

The consultant must configure a condition record-based output determination procedure using PPF (Post Processing Framework) actions tied to freight booking status events, define the action profile with appropriate start/schedule conditions referencing the SD sales order or delivery data, assign the output type to the freight booking document type, and ensure the processing routine (Smart Form/Adobe Form) references the correct SD fields. Event linkage typically ties output triggering to freight booking status changes such as booking confirmation.
mediumIntegration with SD

6. A customer's transportation cost allocation shows correct freight charges within TM, but when passed to SD-Billing for customer freight recovery, the billed tax amount doesn't match the tax calculated during charge calculation, causing revenue leakage. How would you troubleshoot this?

Compare the tax code and jurisdiction determined in the TM calculation sheet against the tax condition records used in the SD pricing procedure for the billing document. Check business partner and product tax classification consistency, since TM and SD can determine tax differently if master data isn't synchronized. Verify that the forwarding settlement-to-billing transfer maps tax-relevant condition types correctly rather than recalculating tax independently in SD.
mediumIntegration with SD

7. During cutover, GTS export compliance checks integrated with embedded TM freight orders are inconsistently applying legal control results, with some valid shipments blocked and others incorrectly cleared. How would you troubleshoot this during the cutover window?

First verify the GTS-TM communication is stable and messages are reaching GTS with complete, correct freight order data (destination country, incoterms, item classification). Check GTS legal control master data (denied party lists, embargo settings) was fully migrated and activated before cutover, not partially loaded. Confirm timing sequencing—freight orders shouldn't be released before GTS classification data sync completes. Isolate whether inconsistency is data-driven (missing classification) versus timing-driven (race condition), and hold a manual review gate for flagged shipments until root cause is confirmed.
mediumIntegration with SD

8. A procurement scenario requires TM to determine route and transit time for inbound deliveries created from MM purchase orders, using capacity planning constraints from a shared carrier pool. What integration and configuration points must align for accurate route determination?

The purchase order's vendor and plant addresses must resolve correctly to TM locations for route determination to calculate accurate distances and durations, typically leveraging the transportation network or an external GIS provider. Transportation lanes must be maintained for the vendor-to-plant relationship with appropriate means of transport and capacity profiles reflecting the shared carrier pool's available capacity. I'd also verify that MM scheduling agreement or PO delivery dates translate correctly into TM requested pickup/delivery windows, since misaligned dates cause infeasible route proposals despite correct distance data.
mediumIntegration with SD

9. An ocean freight shipment requires a bill of lading output triggered after booking confirmation, and the underlying sales order data originates in SD. How would you design the output management flow to ensure document accuracy?

The design should trigger bill of lading output only after the ocean freight booking status reflects carrier confirmation, using an output condition tied to that status rather than order creation. Since commercial data such as incoterms, ship-to, and product details originate in SD, the output form must pull validated fields from the linked sales order via the freight unit, and any changes in SD after booking confirmation should trigger a re-validation or reissue workflow to prevent inconsistent B/L data.
mediumIntegration with SD

10. A subcontracted freight order's output document is generated correctly, but the linked SD delivery is not receiving the expected follow-on status update needed to release invoicing. How would you troubleshoot this output-to-SD gap?

I would first confirm whether the freight order output is only a print/document action versus one that also triggers a status or IDoc-based update back to SD; often the two are configured separately. Then I'd check the subcontracting document flow to see whether the freight order's confirmation status (e.g., goods issue/POD) is correctly propagating to the delivery, since output generation itself doesn't automatically update delivery status. Finally, I'd review whether the integration relies on an interface (IDoc/API) that may have failed silently, requiring reprocessing via the relevant monitoring transaction.
mediumIntegration with SD

11. When configuring output management for freight orders that must trigger a shipment confirmation document upon carrier acceptance in an SD-integrated scenario, what are the key configuration components a consultant must set up?

The consultant configures a PPF (Post Processing Framework) action profile assigned to the freight order type, defines a condition that triggers on the relevant status change (e.g., carrier confirmation or tendering completion), links the output type to a form template (Adobe/Smart Forms), and sets the processing time and partner determination for the recipient. The action profile must be activated in the freight order type customizing so the system evaluates it automatically.
mediumIntegration with SD

12. During cutover weekend, cross-border freight orders integrated with GTS are failing legal control checks intermittently, blocking shipment release. How would you troubleshoot this under time pressure?

I would first check whether the failure is consistent (master data/config gap) or intermittent (timing/connectivity issue between TM and GTS feeder). I'd review the GTS application log for the specific block reason, verify the affected business partners/materials have complete legal control classification, and check RFC connection stability to the GTS system. If it's a genuine legal control hit requiring compliance review, I'd escalate to the compliance team rather than bypass the block.
mediumIntegration with SD

13. During cutover weekend, an embedded TM to GTS integration for export customs checks is failing for a subset of shipments with a specific destination country, while other countries process normally. How would you troubleshoot this without broadly disabling GTS checks?

I'd isolate the failing shipments and compare their master data (legal regulations, classification data, business partner customs data) against a successfully processing shipment to the same country pattern, checking whether a specific legal regulation or embargo list assignment is missing or misconfigured for that destination. Review the GTS communication log for the specific error code returned rather than assuming a generic connectivity issue, since only one destination failing points to configuration/master data rather than integration plumbing. I would avoid a blanket bypass of GTS checks given the compliance risk.
mediumIntegration with SD

14. During cutover, GTS export compliance checks integrated with embedded TM are failing for freight orders belonging to a single sales organization, while all other sales organizations process normally. How would you troubleshoot this during the cutover window?

I'd first check whether the affected sales organization has distinct plant, shipping point, or partner master data configured differently from working ones, since GTS checks often depend on customer/vendor classification and country data completeness. I'd verify the GTS control settings and legal regulation assignment for that sales organization, check for missing or incomplete business partner classification synced from ERP, and review interface logs for that specific org's transactions to isolate whether it's a master data or mapping configuration gap.
mediumIntegration with SD

15. A freight order requires replanning because SD notifies TM of a customer-requested delivery date change after the dock appointment output document was already generated and sent to the carrier. Dispatchers report the carrier is still working from the outdated dock schedule. How would you configure output management to ensure a revised dock appointment output is triggered automatically upon replanning?

Set up an output condition record tied to a change-relevant status or field change on the freight order (such as delivery date or dock slot) so that any replanning event re-triggers output determination for the dock appointment document. Use output type versioning or a 'revised' indicator to distinguish updated documents from originals, and ensure the SD delivery date change propagates to TM promptly via the integration model. Test that carrier-facing channels (email, portal, EDI) receive the corrected output, not just an internal log update.
mediumIntegration with SD

16. You are cutting over an embedded TM implementation for a customer that also uses SAP GTS for export compliance checks on freight orders. During the cutover weekend, GTS connectivity checks are failing intermittently for open shipments. How do you approach resolving this without delaying go-live?

First triage whether the failures are transient (network/queue backlog) or configuration-related (missing legal control settings or plant/customs data), using integration monitoring on both TM and GTS sides. If transient, allow queue reprocessing and validate a sample of shipments end-to-end; if configuration-related, decide with the business whether affected shipments can be manually released with compensating controls while a fix is deployed post-cutover, documenting the risk. Escalate to a defined fallback procedure agreed in the cutover plan rather than improvising during the go-live window.
mediumIntegration with SD

17. A single execution event received for a freight order triggers duplicate goods receipt postings in MM, causing inventory overstatement. How would you investigate and resolve this event-to-MM design flaw?

I would check whether the event is being processed multiple times due to duplicate event messages from the source system or reprocessing of the same milestone without idempotency checks in the automated posting logic. I'd review the event application object linkage to confirm it isn't matched to multiple PO items unintentionally, and verify that the automatic goods movement configuration includes a check for already-posted quantities against the referenced PO item before triggering another GR. Adding an idempotency/duplicate-check control at the event handler level would prevent recurrence.
mediumIntegration with SD

18. An air freight forwarder complains that the Air Waybill output is not generated automatically when an air freight order is created from an SD sales order shipment, though ocean and road outputs work fine. How would you troubleshoot this?

I would first check output determination configuration for the air freight document type, confirming a condition record exists for the AWB output type with the correct access sequence (transportation mode = air). Next, verify the freight order actually carries the air mode of transport and that the SD-to-TM integration correctly transferred the transportation-relevant shipment data with mode air, not defaulting to another mode. I would also check the output channel (print, email, EDI) and any BAdI logic filtering by mode of transport before concluding it is a customizing gap.
hardIntegration with SD

19. During a global TM implementation, Incoterms maintained in SD sales orders are not consistently reflected in the corresponding freight orders, causing disputes over freight cost responsibility between shipper and carrier. As solution architect, how would you troubleshoot and resolve the root cause?

I would trace the integration flow from the SD sales order through the freight order creation process (via forwarding order or direct freight order creation in TM) to confirm whether Incoterms are mapped in the transfer logic, since Incoterms on the sales order don't automatically propagate unless explicitly configured in the copy/determination rules for the corresponding TM document. I would check customizing for Incoterm transfer at document creation, verify BAdI/enhancement logic used for field mapping, and validate that location/partner determination isn't overriding Incoterm-derived responsibility fields, then correct mapping rules or custom logic causing the gap.
hardIntegration with SD

20. In a large multi-country TM organization design integrated with SD, what number range design decisions must be made for organizational units and transportation documents, and what risks arise from poor design?

Number ranges must be defined per organizational unit or company code grouping for freight orders, freight bookings, and forwarding orders, deciding whether ranges are internal or external and whether they are shared globally or segmented per region to support parallel document creation without collisions. Poor design causes number range exhaustion, gaps that break audit trails, or conflicts when SD sales orders trigger TM document creation across multiple systems, requiring careful buffer sizing and coordination with SD order number ranges to avoid duplicate or blocked document numbers.
hardIntegration with SD

21. A global consumer goods company wants to consolidate multiple sales orders from different plants into a single order-based transportation requirement (OTR) prior to EWM warehouse execution, in a decentralized TM deployment being cut over from a legacy system. What migration and architecture risks must be addressed?

Key risks include ensuring open sales orders from legacy are correctly represented as OTRs post-cutover without duplicating consolidation that already occurred manually in the legacy system, validating that plant-to-TM-location mapping supports cross-plant consolidation logic, and confirming decentralized TM's data replication to EWM correctly reflects consolidated freight units rather than plant-level fragments. I would also stage a parallel run comparing consolidated freight unit counts against legacy consolidated shipments before full cutover to catch mapping gaps.
hardIntegration with SD

22. During an event-to-resolution process for a freight booking, an MM-integrated ocean freight order fails to trigger creation of the follow-on purchase order after the carrier booking confirmation event is received. Walk through the likely root causes and resolution steps.

Likely causes include a missing or misconfigured event code mapping so the confirmation event doesn't trigger the expected status change on the freight booking, incorrect subcontracting/PO relevance settings on the freight order item, or a failed integration call to MM due to missing purchasing info records or vendor master data. Resolution involves checking event management configuration for the correct status update rule, verifying freight order item settlement/PO relevance flags, and reviewing the MM integration log for error messages before reprocessing.
hardIntegration with SD

23. Planners report that freight orders created from SD deliveries consistently show incorrect loading and departure dates after a recent factory calendar change. As the solution architect, how would you diagnose and resolve this in a production TM environment?

I would first check whether the factory calendar change was replicated consistently to all organizational units and locations referenced by the affected shipping points, since SD delivery scheduling and TM date determination both depend on calendar assignments. I would trace a failing freight order back to its source delivery, verify the calendar assigned to the shipping point/location and the transportation planning point's organizational role, and check whether the change was applied only in ERP calendar maintenance without corresponding TM location calendar updates, causing a mismatch in scheduling logic.
hardIntegration with SD

24. A freight order contains multiple transportation units (TUs), each linked to a separate MM purchase order for goods receipt purposes. An execution event confirming arrival is received for one TU and correctly triggers a goods receipt in MM, but the other TUs on the same freight order remain without goods receipt even after their own arrival events are logged. As the architect, how would you diagnose and correct the event-to-MM integration design?

Investigate whether the event integration is scoped at the freight order header level rather than the TU level, causing only the first TU's event to be processed for MM posting while subsequent TU events are suppressed or misrouted. Verify the event profile and milestone mapping reference the correct TU-to-purchase-order assignment, and confirm the integration model correctly maps each TU's arrival milestone to its distinct PO/delivery combination. Correct the event determination to fire independently per TU and validate goods receipt posting for each linked PO.

Related topics

Integration with EWMFreight SettlementCharge CalculationTransportation PlanningTenderingTransportation Master DataFreight UnitsEmbedded TM, EWM Integration, Migration and SupportExecutionCarrier CollaborationEmbedded/Decentralized TM, EWM Integration, Migration and ArchitectureFreight Orders

Next practice step

Practice with Interview AITake a mock test