Transportation Managementbeginner

TM Integration with Sales Orders and Deliveries

Key takeaway

Understand how SD sales or delivery documents become transportation demand and how TM planning feeds transportation execution back into delivery and goods-issue processes.

Explanation

📌 KEY POINTS
✅ A transport plan cannot compensate for unrealistic SD scheduling — the whole chain (availability, loading, transport duration, freight-order dates) must be feasible together.
⚠️ When a sales order/delivery changes after planning, determine explicitly: update FU, replan, or is execution status blocking change?
💡 Trace one customer order through delivery → freight unit → freight order using common references — that's the real support path.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT CREATES DEMAND

Transportation-relevant sales orders/deliveries → ship-from, ship-to, quantities, dates, product attributes → transportation demand and freight units

━━━━━━━━━━━━━━━━━━━━
▶ 2. THE FLOW

TM plans freight units into freight orders
Plan coordinates with delivery and warehouse execution; delivery can occur before or after planning depending on scenario

━━━━━━━━━━━━━━━━━━━━
⚠️ 3. THE SCHEDULING CHAIN

Requested delivery date, material availability, loading, transport duration, freight-order dates must form ONE feasible chain
A transport plan can't fix unrealistic SD scheduling upstream

━━━━━━━━━━━━━━━━━━━━
▶ 4. AFTER A CHANGE

Determine: update FU, replan, or is execution status blocking the change?

✅ CHECKPOINT: name the five elements that must form one feasible scheduling chain.

Real project scenario

A customer changed delivery quantity after the freight order was tendered. The delivery updated but the transport load was not revalidated. A change-monitoring rule was added for tendered freight.

Common mistakes

Treating SD and TM dates independently.
Losing source references.
Ignoring post-planning delivery changes.
Replanning after warehouse/loading cutoff without coordination.
Assuming TM creates supply or ATP confirmation.

Best practices

Keep common references.
Align scheduling assumptions.
Govern late SD changes.
Revalidate capacity after quantity changes.
Define freeze points with warehouse/carrier.

Interview angle

Trace a sales order or delivery into TM demand and back to delivery execution.

Practice this lesson

Quick check

1. In the lesson "TM Integration with Sales Orders and Deliveries", consider this project situation: A customer changed delivery quantity after the freight order was tendered. Which statement is correct?

2. An Order-based Transportation Requirement (OTR) in SAP TM is created based on which source document?

3. A Delivery-based Transportation Requirement (DTR) in SAP TM is generated from which ERP document?

Interview questions

1. Using this SAP project situation — A customer changed delivery quantity after the freight order was tendered — explain TM Integration with Sales Orders and Deliveries. 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. 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?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.