Freight unit building in SAP TM (Transportation Management) is the process that turns incoming orders and deliveries into freight units — the smallest pieces of cargo that SAP TM can plan, tender, and execute. With automation switched on, SAP TM builds these freight units the moment an order arrives, using a Freight Unit Building Rule (FUBR) that splits or combines cargo based on limits you set — weight, volume, and quantity. No planner touches anything. The order lands, the freight units appear, planning begins.
TL;DR
- A freight unit (FU) = the smallest plannable piece of cargo in SAP TM.
- The FUB Rule (FUBR) is the “recipe” that tells SAP TM how to build FUs automatically.
- Automation fires as soon as an order or delivery reaches TM — once switched on in the integration profile.
- Split criteria (weight, volume, pieces) and consolidation settings decide how many FUs you get.
- Get the rule wrong and you get chaos: tiny FUs, failed planning, frustrated planners.
The numbers that matter:
- 45% less manual planning effort after FUB automation — SCM Champs client project, 2025
- 0.5–3.6% of manually entered data contains errors, per peer-reviewed research on general data entry — every wrong weight or quantity becomes a wrong freight unit (source: Behavior Research Methods, link.springer.com/article/10.3758/s13428-019-01207-3)
- 10 hours per week — what one client’s planners spent creating transport demands by hand
| Manual FU creation | Automated FUB | |
|---|---|---|
| Trigger | Planner creates demand by hand | Order arrives → FU appears instantly |
| Speed | Minutes per order | Seconds, zero touch |
| Errors | Typos, missed orders, wrong splits | Consistent, rule-based |
| Scale | Breaks at high volume | Handles thousands of orders |
| Planner’s day | Data entry | Actual planning & exceptions |
What Is a Freight Unit in SAP TM?
A freight unit is like a packed suitcase. The airline doesn’t plan around your socks and shirts — it plans around the suitcase. SAP TM works the same way: it plans around freight units, not order lines.
A customer orders 12 pallets. TM checks the rule, sees they fit one truck, and creates one freight unit. A 30-pallet order? The same rule creates two.
Freight Unit vs Freight Order vs Freight Booking
Three documents, three jobs:
| Document | What it is | Who creates it | When it appears |
|---|---|---|---|
| Freight Unit (FU) | The cargo — demand that needs moving | Created automatically from orders | The moment an order arrives |
| Freight Order (FO) | The trip — a truck moving one or more FUs | Planner or automated planning run | During planning |
| Freight Booking (FB) | Reserved carrier capacity (ocean/air) | Planner or booking process | When space is booked with a carrier |
How Automatic Freight Unit Building Works
Every incoming order makes the FUB Rule answer three questions: What freight unit type do I create? When do I split? When do I combine? Define those answers once, and the rest runs itself:
- An order or delivery is created in SAP S/4HANA (or a connected ERP).
- It reaches SAP TM as a transportation demand.
- TM picks the right FUB Rule — a default, or a condition choosing different rules per customer, product, or lane.
- The rule checks split limits (max weight, volume, pieces) and consolidation settings.
- Freight units are created automatically — ready for planning.
- The order changes later? Change processing updates the freight units — if configured.
The logic is identical in embedded TM (inside S/4HANA) and standalone TM. The difference is where demand comes from: embedded TM reads sales orders and deliveries directly, while standalone TM receives them through integration as OTRs and DTRs (order- and delivery-based transportation requirements).
The Settings That Make or Break Automation
Five settings do almost all the work:
| FUBR setting | What it does | Simple example |
|---|---|---|
| FU document type | Which kind of FU gets created | Standard FU for road freight |
| Split criteria (weight/volume/pieces) | Caps the size of one FU | Max 24 t → a 30 t order becomes 2 FUs |
| Consolidation | Combines items/orders into one FU | 3 small items → 1 FU |
| Rule determination (condition) | Picks different rules for different scenarios | Customer A splits by pallets; Customer B by weight |
| Incompatibilities | Keeps wrong things apart | Food never builds with chemicals |
The SCM Champs FUB Automation Maturity Model
Across our FUB projects, every client sits at one of four levels:
| Level | Name | What it looks like | The pain |
|---|---|---|---|
| 0 | All Manual | Planners create demands by hand | Slow, error-prone, doesn’t scale |
| 1 | One-Rule Automation | A single default FUBR for everything | Works until volume or variety grows |
| 2 | Smart Rules | Condition-based rules per customer/product/lane | Needs expertise to design & test |
| 3 | Exception-Only | Rules + incompatibilities + monitoring tuned so planners only handle exceptions | The goal state |
The self-check: if your busiest planner quit tomorrow, would freight units still get created correctly? If no, you’re at Level 0 or 1.
Common FUB Problems & How We Fix Them
| Symptom | Likely cause | The fix |
|---|---|---|
| No FU created for a new order | FUB rule not found (missing condition/default) | Check rule determination + application log |
| Hundreds of tiny FUs | Split limits too low / consolidation off | Raise split quantities, enable consolidation |
| One giant unplannable FU | No split criteria vs truck capacity | Set split limits to match vehicle capacity |
| Wrong products mixed in one FU | Missing incompatibility settings | Define incompatibilities |
| ERP order changed, FU didn’t | Integration/change handling issue | Check integration settings, reprocess |
When we walk into a broken FUB setup, we don’t start with settings. We assess: pull the application log, trace ten live orders end-to-end, map which rule fired — or didn’t. Then we redesign, test against a week of real order data, and stay through hypercare until the exception rate settles.
Real Results From Real Projects
A building materials distributor (details anonymized) running 300+ orders a day had planners spending ~10 hours a week creating and fixing transport demands by hand — wrong splits forced ~7% of shipments into re-planning. We rebuilt their FUB rules with condition-based determination per product line. After go-live: demand creation fully automatic, re-planning under 1.5%, and those 10 hours went into carrier negotiations.
Experts & the Community
Expert Corner
David Chen, SAP TM Lead at SCM Champs, 12 years in SAP logistics: “Nine times out of ten the problem isn’t SAP — it’s a split limit somebody set in year one and nobody has questioned since.”
Sarah Lin, Senior SAP TM Consultant at SCM Champs, 8 years in SAP logistics: “The day automation went live, the planners stopped doing data entry and started doing planning. That’s the whole point of TM.”
You Asked, We Answered
Real questions from the SAP community:
“I’m on embedded TM (S/4HANA). The sales order shows the TM Status tab, but no freight unit gets created — and my FUBR is maintained in the logistics integration profile. What’s wrong?” A visible TM Status tab means integration found your control key, so the blocker sits further down: a delivery block removing schedule-line confirmation, zero weight or volume, or automatic FUB not flagged in the logistics integration profile. Run /SCMTMS/CHK_DOC_INT_TM_INTEGR and read the application log; it names the missing piece.
“We’re on S/4HANA Public Cloud TM and freight units aren’t created from sales orders — and I can’t run check reports there. How do I even diagnose it?” In Public Cloud, skip the reports: open the Manage Order-Based Transportation Requirements app, find your OTR, and trigger freight unit building manually. The error it throws — no FUBR, missing location, missing weight — is your root cause. Fix it and rebuild.
Your turn: what’s your biggest freight unit headache? Tell us in the comments — the best become future articles. Quick poll: What % of your freight units are created automatically today? → 0% / Under 50% / 50–90% / 90%+
About SCM Champs
SCM Champs is a US-based SAP supply chain consulting company headquartered in Wilmington, Delaware. Founded in 2018, the company is an official SAP Partner specializing in SAP Transportation Management (SAP TM), SAP Extended Warehouse Management (SAP EWM), SAP Logistics Management (SAP LGM),and warehouse automation.
SCM Champs has delivered more than 10 SAP supply chain implementations across the pharmaceutical, e-commerce, semiconductor, and manufacturing industries.
Every engagement follows a structured delivery approach that includes assessment, solution design, testing with real business data, go-live support, and hypercare. This same implementation methodology is reflected in the Freight Unit Building Maturity Model described in this article.
How we work: Every SAP implementation follows a structured delivery approach: assessment, solution design, testing with real order data, go-live support, and hypercare. This same methodology is used in the Freight Unit Building Maturity Model presented in this article.
FAQ
1. What is a freight unit in SAP TM? It’s the smallest bundle of goods that travels together through your transport network — the “unit of demand” between an order and a truck. All TM planning runs on it.
2. What’s the difference between a freight unit and a freight order? The freight unit is the cargo that needs moving; the freight order is the vehicle trip that moves it. One truck (freight order) often carries several freight units.
3. What is a Freight Unit Building Rule (FUBR)? The stored decision logic behind FU creation: which document type to use, at what weight, volume, or piece count to split, and when to merge items into one unit.
4. Where do I configure the FUB rule in SAP TM? In the Profiles and Settings area (on older releases: NWBC → Application Administration → Planning → General Settings → Freight Unit Building Rule). Freight unit types live in customizing under Transportation Management → Planning → Freight Unit.
5. Why are my freight units not being created? Most often the system can’t find a FUB rule (missing condition or default), the item has no weight or volume, or automatic FUB isn’t activated in the logistics integration profile. The application log tells you which.
6. Is freight unit building the same in embedded and standalone TM? The rule logic is identical — only the demand source differs. Embedded TM builds FUs straight from S/4HANA orders and deliveries; standalone TM builds them from integrated transportation requirements (OTRs and DTRs).
7. How long does it take to set up FUB automation? Expect roughly 3–5 weeks of rule design and testing inside a wider TM project, depending on how many scenarios need their own rules.