SAP EWM in 2026: Modernization, Automation & Future Trends

What Is a Transportation Unit in SAP EWM? (Definition)

Every warehouse has a moment where goods meet the truck. Pallets are ready, the dock door is free, and the driver is waiting. If the system does not know which truck is at which door, or which deliveries belong on it, the whole operation slows down. In SAP Extended Warehouse Management, the Transportation Unit is the object that holds this picture together. It links the physical vehicle, the yard, the dock door, and the deliveries into one record that the warehouse team can follow from arrival to departure.

This guide explains Transportation Units in SAP EWM in plain language. You will see what a Transportation Unit is, how it differs from a vehicle, how the setup works, and how the complete process workflow runs for both inbound and outbound shipments. Whether you are a warehouse consultant, a key user, or a student preparing for a project, the sections below give you a practical view of the SAP EWM transportation unit process.

A Transportation Unit (TU) in SAP EWM is the smallest unit of transport that the system tracks for loading and unloading. It represents the means of transport that brings goods into the warehouse or takes them out, such as a truck, a trailer, a rail wagon, or a container. A TU carries the deliveries or handling units assigned to it, and it records where the transport is, which door it uses, and what status it has at any point in time.

A Transportation Unit can contain one or more vehicles. A vehicle is the physical carrier, for example a tractor and a trailer. The TU is the logical document that groups the vehicles and the cargo. This split is useful because one tractor can pull different trailers on different days, while the transport record stays tied to the shipment.

Quick Facts About Transportation Units in SAP EWM

Topic	Quick Fact
Full Form	TU stands for Transportation Unit
Used In	SAP Extended Warehouse Management (SAP EWM) for inbound and outbound processes
Contains	One or more vehicles and the deliveries or handling units loaded on them
Main Tracking Points	Checkpoint, yard, dock door, and departure
Common Transactions	/SCWM/TU to maintain TUs, /SCWM/VEH for vehicles, /SCWM/CICO for check-in and check-out
Linked Objects	Inbound and outbound deliveries, handling units, warehouse tasks, warehouse orders, doors, and yard bins
Typical Users	Gatekeepers, yard coordinators, dock supervisors, and shipping clerks
Key Benefit	Clear control of every truck from arrival to exit

Why Transportation Units Matter in a Warehouse

Without a TU, a warehouse depends on phone calls, paper slips, and guesswork at the gate. With a TU, the system answers simple but important questions at any moment. Which trucks are in the yard right now? Which door is free? Which deliveries are loaded on this trailer? Has the driver left the site?

The benefits show up in daily work:

Shorter waiting time: Trucks are directed to a free door instead of idling at the gate.
Better dock use: Door assignment follows the planned workload and not whoever arrives first.
Accurate shipping status: Goods issue and goods receipt follow real movements instead of manual updates.
Fewer loading errors: Handling units are scanned to the correct TU, so the wrong pallet does not leave on the wrong truck.
Clear audit trail: Every check-in, door change, and departure is recorded with a time stamp.

Key Terms You Should Know

Before looking at the workflow, it helps to understand the objects that work together with the Transportation Unit.

Term	Meaning
Transportation Unit (TU)	The logical record of a transport that arrives at or leaves the warehouse
Vehicle	The physical carrier, such as a truck, trailer, or container, assigned to a TU
Checkpoint	A gate or control point where TUs are checked in and checked out
Yard	The outside area of the warehouse site where trucks wait, park, or move between points
Yard Bin	A parking position inside the yard where a TU can be placed
Door	A dock position where a TU is loaded or unloaded
Handling Unit (HU)	A pallet, carton, or container that holds goods and is loaded onto or removed from a TU
Activity	A step in the TU life cycle, such as arrival, check-in, loading, or departure

Prerequisites and Basic Configuration

A smooth process starts with good master data and configuration. In most projects, the following items are prepared before any TU is created.

Warehouse structure: Define the warehouse number, storage types, and staging areas where goods wait before loading or after unloading.
Doors: Create doors, link them to a staging area, and mark them for inbound, outbound, or both.
Checkpoints: Set up the gate or control point where drivers register on arrival.
Yard bins: Define parking positions if the site uses yard management.
TU types and vehicle types: Describe the kinds of transport that visit the site, with size and capacity details.
Activities and statuses: Decide which steps are tracked, for example arrival, check-in, start of loading, end of loading, and departure.
Door determination: Define the rules that suggest a door based on the process, the carrier, or the type of goods.

When these settings are correct, the TU life cycle runs with little manual correction. When they are weak, users face wrong door suggestions and statuses that do not match the real situation.

Complete Process Workflow for Inbound

In the inbound flow, the TU arrives with goods from a supplier or another plant. The goal is to receive the goods, put them away, and release the truck quickly. The steps below follow the normal sequence.

Step 1: Create the Transportation Unit

A TU can be created in several ways. It may be created in advance from an advanced shipping notification or an inbound delivery, it may be sent from a transportation planning system, or the gate user may create it manually when an unplanned truck shows up. The record holds the carrier, the vehicle number, the expected arrival, and the linked deliveries.

Step 2: Arrival and Check-In at the Checkpoint

When the truck reaches the gate, the gatekeeper registers the arrival and checks the TU in. At this point the system confirms that the truck is on site and updates the status. Some sites also capture the driver name, the seal number, and the license plate at this step.

Step 3: Yard Movement

If the dock door is not free, the TU is directed to a yard bin. A yard task moves the TU from the checkpoint to the parking position. When the door becomes free, another yard task moves it to the dock. The system records each move, so the yard coordinator always sees where the trailer is.

Step 4: Door Assignment

The TU is assigned to a door. The assignment can be made by the system through door determination or set by the dock supervisor. Once the TU is at the door, the status shows that unloading can begin.

Step 5: Unloading and Goods Receipt

Warehouse workers unload the handling units. Each handling unit is scanned, and the system creates warehouse tasks to move goods from the door to the final storage bin. Goods receipt is posted according to the process design, often after unloading is finished and the delivery is confirmed.

Step 6: Check-Out and Departure

When unloading ends, the TU is closed and the truck leaves through the checkpoint. The gatekeeper checks the TU out, and the status changes to departed. The door is free again for the next truck.

Complete Process Workflow for Outbound

In the outbound flow, the warehouse prepares goods for customers and loads them onto a TU. The sequence is similar to inbound, but loading and goods issue replace unloading and goods receipt.

Step 1: Plan and Create the TU

The TU is created from a transportation plan, a freight order, or manually by the shipping team. The outbound deliveries that belong to this transport are assigned to the TU, either when it is created or later during loading.

Step 2: Picking and Staging

Warehouse orders and tasks guide the pick of goods from storage. The picked goods are packed into handling units and moved to the staging area that belongs to the planned door.

Step 3: Check-In and Door Assignment

The truck arrives and is checked in at the checkpoint. The system or the dock supervisor assigns a door. If the goods are not yet ready, the truck waits in the yard and moves to the door when loading can start.

Step 4: Loading

Workers load the handling units onto the vehicle. Each unit is scanned to the TU. The system confirms that the loaded item belongs to a delivery assigned to this transport. Many sites also create a loading plan so that the last stop is loaded first and unloaded last.

Step 5: Close the TU and Post Goods Issue

When loading ends, the user closes the TU. Shipping documents are printed, and the goods issue is posted for the deliveries on the TU. The delivery status updates in the connected ERP system, and the stock leaves the warehouse in the books.

Step 6: Departure and Check-Out

The truck leaves the site and is checked out at the checkpoint. The TU gets its final status, and the door is released.

Inbound and Outbound Workflow at a Glance

Step	Inbound Process	Outbound Process
1	Create TU from ASN or delivery	Create TU from plan or freight order
2	Arrival and check-in	Pick and stage goods
3	Move to yard bin if needed	Arrival and check-in
4	Assign door	Assign door
5	Unload and post goods receipt	Load and scan handling units
6	Close TU and check out	Close TU, post goods issue, check out

Transportation Unit Statuses

Statuses tell users where a TU stands. The exact list depends on configuration, but the usual pattern looks like the table below.

Stage	What It Tells You
Planned	The TU exists, but the truck has not arrived yet
At checkpoint	The truck has reached the gate and is waiting for check-in
Checked in	The truck is registered on site
In yard	The TU is parked in a yard bin
At door	The TU is positioned at a dock door
Loading or unloading	Work on the handling units is in progress
Closed	Loading or unloading is finished
Departed	The truck has left through the checkpoint

Integration With Other SAP Components

The Transportation Unit does not live alone. It exchanges data with several other parts of the SAP system environment.

SAP ERP or S/4HANA: Inbound and outbound deliveries come from the ERP side. Goods movements post back to it after receipt and issue.
SAP Transportation Management: Freight orders and bookings from planning can create or update TUs, and execution status flows back to the planner.
Handheld and radio frequency devices: Workers scan handling units and confirm tasks on the floor.
Yard systems and gate hardware: Barcode readers or plate recognition can support the check-in step.

This connection explains why TU data must be accurate. A wrong status in the warehouse can delay a goods issue, and that in turn can hold up invoicing.

Common Problems and How to Fix Them

Problem	Likely Cause	Suggested Fix
TU cannot be checked in	Checkpoint not defined or TU status is wrong	Check checkpoint setup and current TU status
No door is suggested	Door determination rules are missing	Review rules and door-to-staging links
Delivery cannot be assigned to TU	Delivery is blocked or not yet released for the process	Check the delivery status and warehouse process
Goods issue does not post	TU not closed or loading not complete	Complete loading and close the TU
Truck shows wrong location	Yard task not confirmed	Confirm the open yard task

Best Practices for Using Transportation Units

Create TUs early: Advance information lets the team plan doors and labor before the truck arrives.
Keep statuses honest: Update each step on time so the yard view matches reality.
Train gate and dock teams: Most errors start at the checkpoint, so a short practice session saves hours later.
Use scanning: Scanning handling units to the TU removes manual typing mistakes.
Review door rules often: As volumes change, door determination should follow.
Monitor dwell time: Track how long trucks stay on site and look for repeated delays.

Frequently Asked Questions

Q1. What is the difference between a Transportation Unit and a vehicle in SAP EWM?

A: A vehicle is the physical carrier, such as a truck or a trailer. A Transportation Unit is the logical record that groups one or more vehicles with the cargo and tracks its status. Think of the vehicle as the body and the TU as the file that follows it through the site.

Q2. Can I create a Transportation Unit without a delivery?

A: Yes. A TU can exist on its own, for example when an unplanned truck arrives at the gate. You can assign deliveries to it later, once the paperwork is clear.

Q3. Do I need yard management to use Transportation Units?

A: No. Many sites use TUs only for check-in, door assignment, and loading. Yard bins and yard tasks are added when the site has enough parking and movement to justify them.

Q4. Which transaction do I use to maintain a TU?

A: The transaction /SCWM/TU is commonly used to create and change Transportation Units. Vehicles are maintained with /SCWM/VEH, and check-in or check-out is done with /SCWM/CICO.

Q5. Can one TU carry deliveries for different customers?

A: Yes. A TU can hold several outbound deliveries, even for different ship-to parties, as long as the transport plan allows it. The loading plan then decides the order of loading.

Q6. When is goods issue posted in the outbound flow?

A: In a typical setup, goods issue is posted after loading is complete and the TU is closed. The exact trigger depends on how the warehouse process is configured, so always confirm it with your project design.

Q7. What happens if a truck leaves before the TU is closed?

A: The status will not match reality, and goods issue may stay open. Most sites set rules so that a TU cannot be checked out until loading is finished, or they require a supervisor to confirm an exception.

Q8. How can I learn the SAP EWM transportation unit process hands-on?

A: Practice in a training system, create a TU, check it in, assign a door, load a handling unit, and check it out. Repeating the full cycle several times builds confidence faster than reading alone.

Conclusion

Transportation Units in SAP EWM give the warehouse one clear record for every truck on site. From the first check-in at the gate to the last scan at the dock door, the TU keeps the vehicle, the yard, the door, and the deliveries connected. When the setup is right and the team follows the process, trucks move faster, dock doors stay busy, and goods receipt and goods issue post on time.

If you want to work on real projects with confidence, a structured learning plan helps. Enrolling in SAP EWM training lets you practice the full TU workflow, from check-in and yard moves to loading and departure, with guidance from experienced trainers. Start with the basics, repeat the process in a system, and build your skills one step at a time.

About the Author

The TechBrainz AIOps Team has written this article. Our team of IT and SAP practitioners shares practical guides on warehouse management, automation, and enterprise technology to help professionals grow their careers.