Transportation Managementintermediate

Freight Unit Lifecycle: Creation, Change and Planning Relevance

Key takeaway

Understand how freight units are created from transportation demand, updated when source documents change and consumed by planning without losing source-document traceability.

Explanation

📌 KEY POINTS
✅ Freight units are the planning-relevant demand objects — TM doesn't plan raw source documents directly.
⚠️ A freight unit already assigned to a freight order may need REPLANNING rather than a simple rebuild.
💡 When a planner says "demand is missing," trace: was the source transportation-relevant? Did FU building succeed? Is it inside the active selection profile?

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHERE FUS COME FROM

Sales orders, POs, stock transport orders, deliveries create requirements
Freight Unit Building Rules split or combine those into freight units

━━━━━━━━━━━━━━━━━━━━
▶ 2. WHAT AN FU CARRIES

Locations, dates, quantities, products, planning relevance
Source-document changes can trigger updates depending on process state

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP (WHEN DEMAND "IS MISSING")

Verify the source was transportation-relevant.
Verify FU building actually succeeded.
Verify the active selection profile includes the resulting object.

━━━━━━━━━━━━━━━━━━━━
⚠️ 3. GRANULARITY

Too many tiny FUs = planning overhead; excessive consolidation = unrealistic vehicle planning

✅ CHECKPOINT: what three things do you check, in order, when demand appears to be missing?

Real project scenario

A sales-order change increased quantity after the freight unit had already been planned. The unit required update and capacity revalidation rather than creating an unrelated second shipment.

Common mistakes

Treating freight unit as the same object as a delivery.
Ignoring source-document changes.
Rebuilding demand without checking planning status.
Over-splitting units.
Troubleshooting cockpit selection before proving FU creation.

Best practices

Preserve source references.
Design FUBR with real volumes.
Revalidate planned FUs after material changes.
Monitor creation failures.
Distinguish demand creation from planning.

Interview angle

Explain the FU lifecycle and how source changes interact with planning status.

Practice this lesson

Quick check

1. A project team faces this situation in "Freight Unit Lifecycle: Creation, Change and Planning Relevance": A sales-order change increased quantity after the freight unit had already been planned. Which action is the most appropriate next step?

2. A planner notices that after a source sales order is changed in ERP, the corresponding freight unit in SAP TM automatically reflects updated quantities. Which mechanism enables this behavior?

3. Which source document types can trigger the automatic creation of freight units in SAP TM via transportation requirements?

Interview questions

1. A project encounters this situation while working on Freight Unit Lifecycle: Creation, Change and Planning Relevance: A sales-order change increased quantity after the freight unit had already been planned. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.

Answer it in your own words first, then compare.

2. Freight units built from SD sales orders are intermittently missing transportation requirement dates, causing planning runs to skip them entirely, and this only occurs for orders with certain delivery types. As solution architect, how would you troubleshoot this freight unit building issue?

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.