Transportation Managementadvanced

Freight Units: Building Transportation Demand from Orders and Deliveries

Key takeaway

Understand freight units as the planning-relevant transportation demand objects built from sales, purchase, stock-transfer or delivery requirements according to Freight Unit Building Rules.

Explanation

📌 KEY POINTS
✅ TM optimizes Freight Units, not raw sales-order items — the FUBR is what creates the atomic planning demand.
⚠️ A poor FUBR creates planning noise either direction: too many tiny FUs, or unrealistic over-aggregation.
💡 Whether an FU is still changeable, already planned, or execution-relevant decides what a source-order change actually does to it.

━━━━━━━━━━━━━━━━━━━━
▶ 1. THE BUILDING CHAIN

Source documents → transportation requirements → Freight Units (via FUBR) → assignable to freight orders/bookings

━━━━━━━━━━━━━━━━━━━━
▶ 2. WHAT THE FUBR CONTROLS

Splits/combines demand by source/destination, dates, product, quantities, or other supported attributes

━━━━━━━━━━━━━━━━━━━━
⚠️ 3. THE GRANULARITY TRAP

Too many tiny FUs → optimizer/planner overload
Over-aggregated → unrealistic vehicle/delivery planning

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP (TROUBLESHOOTING)
Source document → transportation requirement → FU → assigned freight order (trace in this order).

✅ CHECKPOINT: state the four-step trace path for troubleshooting a freight-unit problem.

Real project scenario

A company generated one freight unit per sales-order item, creating tens of thousands of tiny planning objects. Redesigning the FUBR to consolidate compatible items drastically simplified the Transportation Cockpit.

Common mistakes

Treating FU as the same object as a delivery.
Designing FUBR without volume testing.
Over-splitting demand.
Ignoring source-document changes after planning.
Troubleshooting freight order without tracing FU origin.

Best practices

Design FUBR using real shipment patterns.
Trace FU to source document.
Monitor FU granularity.
Test change propagation.
Keep planning/execution lifecycle clear.

Interview angle

Explain transportation requirement, FUBR, freight unit and how FUs become planning demand.

Practice this lesson

Quick check

1. Scenario — A company generated one freight unit per sales-order item, creating tens of thousands of tiny planning objects. For the lesson "Freight Units: Building Transportation Demand from Orders and Deliveries", which response shows the strongest architecture and production judgment?

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

3. In SAP Transportation Management, which customizing object determines how many freight units are created from a transportation requirement and how items are grouped into those freight units?

Interview questions

1. You are the senior consultant/architect responsible for Freight Units: Building Transportation Demand from Orders and Deliveries. The project situation is: A company generated one freight unit per sales-order item, creating tens of thousands of tiny planning objects. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

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.