SCM Champs Bridging Gap Between SAP EWM & TM for Connected Supply Chain Execution

A truck pulls into the yard at 9 a.m. The load is not ready. The warehouse team is still picking, because a customer added two lines late yesterday and nobody passed that on to transportation. The driver waits ninety minutes. The carrier charges for the wait. The next stop slips. By the afternoon, three people are on a call trying to work out what actually went on that trailer.

Nothing in that story is a software failure. The warehouse system did its job. The transportation system did its job. The trouble sits in the space between them.

That space is where SCM Champs works. We help businesses connect SAP Extended Warehouse Management (EWM) and SAP Transportation Management (TM) so warehouse execution and transportation planning run as one process, instead of two systems that pass data back and forth while people fill the gaps by phone and email.

In short

The problem: Warehouse and transportation each run well, but the handoff between them is coordinated by people — calls, spreadsheets, and email.

The goal: One connected flow from transportation planning through to departure, where a change on one side is visible to the other in time to act on it.

The next step: An SAP EWM–TM integration assessment that shows exactly where your two processes fall out of sync.

1. When Warehouse Execution and Transportation Planning Fall Out of Sync

Most operations teams do not describe this as an integration problem. They describe it as a day.

The truck arrives before the shipment is ready. The carrier is on time. The picking is not finished, or the pallets are staged in the wrong dock area. Someone has to decide whether to hold the truck or cut the load.

Warehouse changes do not reach transportation fast enough. A short pick, a damaged pallet, a change in pallet count — these change the load. If the planner finds out after the freight order is confirmed, the fix is manual.

Planners are working without a current view of warehouse status. They can see what was planned. They cannot always see what is actually picked, packed, staged, or loaded right now. So they plan against yesterday's picture.

Staging and loading delays push the whole schedule. One late load moves the departure, which moves the delivery window, which moves the next collection. The cost lands on service levels and on the freight bill.

People hold the process together by hand. Spreadsheets tracking which loads are ready. Messages to the yard. A call to the dock supervisor before every departure. It works, but it depends on the same few experienced people being at work that day.

The automation runs well, but on its own. Plenty of warehouses have conveyors, AS/RS (automated storage and retrieval systems), shuttles, or robotics working exactly as designed. Material moves fast inside the four walls. What happens outside them is still coordinated manually.

None of this shows up as a red light on a dashboard. It shows up as detention charges, overtime, missed cut-offs, expedited freight, and customers who call before you do.

2. What Should SAP EWM and TM Share?

Before anyone talks about interfaces, it helps to agree on what has to pass between the two sides — and in which direction.

What the warehouse needs from TMWhat TM needs from the warehouseTransportation planning informationDelivery / shipment informationFreight order informationStaging and loading statusTransportation-unit informationActual warehouse execution statusPlanned loading / departure informationExecution updates (loading start, finish, departure)Changes affecting warehouse executionShipment readiness visibility

From TM into the warehouse:

• Transportation planning information — how deliveries are grouped and sequenced, so warehouse execution can be aligned with the planned transportation sequence where the process requires it.
• Freight order information — who is collecting, when, against which stop. This is what lets the warehouse work backwards to a staging deadline.
• Transportation-unit information — in transportation-unit-based scenarios, the trailer or container becomes a physical execution object in EWM that staging and loading are managed against.
• Planned loading and departure times — the warehouse's clock. The single most useful thing transportation can give the floor.
• Changes after planning — a carrier running late, a stop dropped, a load resequenced. Each one changes what the warehouse should be working on right now.

From the warehouse into TM:

• Delivery and shipment data — weights, volumes, handling units, pallet counts. Planning is only as good as these numbers.
• Staging and loading status — staged, part-loaded, fully loaded. This tells a planner whether a truck can be released or needs to be held.
• Actual execution status — not what was planned, but what has happened on the floor.
• Execution updates — loading started, loading finished, vehicle departed. These close the loop so nobody is chasing status by phone.
• Shipment readiness — the plain question every planner asks: is it ready to go?

Work through this list before an integration project starts. If the business cannot agree on what moves and in which direction, the technical design will fill the gap with assumptions.

3. Why Having SAP EWM and TM Is Not Enough

Owning both products is not the same as running a connected process. There are a few common reasons the gap stays open.

Process design. Warehouse and transportation processes were often designed by different teams, at different times, sometimes years apart. Each one is sound. Neither was designed with the other in mind.

Integration design. The connection is live. Messages move. But the end-to-end business process was never mapped, so the systems exchange data at points that do not match how the operation actually works.

Data and status flow. Information arrives, but late, or partial, or in a form the other side cannot act on. A status that updates at end of shift does not help a planner deciding at 11 a.m.

Warehouse automation. MFS, which connects EWM with warehouse automation and PLC-controlled equipment, along with conveyors, AS/RS, scanners, and robotics, is usually designed around throughput inside the warehouse. If the automation layer does not report the events transportation depends on, the last step stays manual no matter how automated the rest is.

Exception handling. The standard flow usually works. The exceptions pull people in — a late truck, a quantity change, a partial load, a last-minute customer request. If exceptions were not designed for, every one becomes a conversation.

Customization. Heavy custom development sometimes solves a short-term problem and then becomes the reason nothing can be upgraded or changed later.

This is not true in every SAP environment, and it is not a sign that something was implemented badly. It is usually what happens when two large processes grow up separately.

4. Which SAP EWM–TM Integration Approach Fits Your Operation?

There is more than one way to connect these processes. Here is how they compare.

Embedded EWM with TM in S/4HANA

Best suited when:
Both capabilities run in one S/4HANA system; warehouse and transportation scope fits what embedded deployment supports; you want one system to maintain and upgrade

Watch out for:
Embedded EWM does not cover every function of decentralised EWM. Check your specific warehouse requirements against embedded scope before committing

EWM and TM integrated across the landscape

Best suited when:
Decentralised EWM, a separate TM system, or a mix; multiple sites or logistics systems in play; warehouse and transportation run on different release cycles

Watch out for:
The process has to be designed across system boundaries. Interface timing, error handling, and status latency all become design decisions, not afterthoughts

Transportation-unit-based integration

Best suited when:
Heavy loading activity, dock and door scheduling, yard movements; the trailer or container is the unit the warehouse plans and loads against

Watch out for:
This changes how staging and loading are structured in EWM. It is a process redesign, not just a configuration switch

Advanced Shipping and Receiving (ASR)

Best suited when:
You want an integrated end-to-end shipping and receiving process between TM and EWM built on the freight order, rather than on warehouse-side transportation objects

Watch out for:
ASR is freight-order-based and does not use the EWM transportation unit or EWM vehicle. Freight-order-based and TU-based integration can run in parallel, so review which of your existing EWM and TM processes each one should cover before adopt.

5. How SCM Champs Connects SAP EWM and TM

Here is the work we actually do, in order.

1. Assess the current landscape. We look at what is running today — EWM, TM, S/4HANA, the automation systems, the existing interfaces, and the process flows people follow in practice, not just the ones in the design document.

2. Map the end-to-end execution process. Order, delivery, transportation planning, warehouse execution, staging, loading, departure. One map, both sides on it. This is usually the first time some teams see the whole thing on a single page.

3. Define what needs to be integrated. From that map, we identify the specific business information, events, statuses, and dependencies that have to move between EWM and TM, and when each one has to arrive to be useful.

4. Connect warehouse automation into the process. MFS, conveyors, AS/RS, and robotics should support the SAP execution flow, not run alongside it. We identify where automation events need to feed warehouse execution and transportation processes, so the automated part of the operation is part of the process rather than a separate one.

5. Test real-world exceptions. Not just the happy path. Late trucks. Partial loading. Quantity changes after planning. Shipment changes after staging. Blocked dock doors. These situations decide whether the integration reduces manual work or just moves it.

6. Is Your EWM–TM Integration Creating These Problems?

Read through these. Answer yes or no for your own operation.

• Warehouse teams do not find out when transportation plans change.
• Transportation planners do not have accurate shipment-readiness information.
• Trucks wait because warehouse execution is not lined up with the transport schedule.
• Loading changes have to be coordinated by phone, email, or in person.
• Warehouse automation runs well but is not connected to SAP transportation processes.
• Spreadsheets or email threads are being used to track what is ready to ship.
• Exceptions regularly need someone to step in manually.
• Warehouse and transportation teams have to reconcile what actually shipped after the fact.

Several "yes" answers can be a useful signal that warehouse and transportation need to be reviewed together, as one process, rather than managed as two separate workflows. This is particularly common where EWM and TM were implemented as separate projects and later had to work with each other.

7. Before Starting an SAP EWM–TM Integration Project, Ask These Questions

These are worth answering internally before you bring in any partner.

1. Are our EWM and TM processes designed as one end-to-end flow, or as two flows joined by an interface?
2. Which warehouse events should update transportation execution, and how quickly does each one need to get there?
3. Is our automation layer included in the integration design, or sitting outside it?
4. Are we using standard SAP capability where it fits, and do we know why each custom development exists?
5. What happens when warehouse execution changes after transportation planning is complete? Who decides, and in which system?
6. Who owns exception handling across warehouse and transportation — one team, two teams, or nobody in particular?
7. Where is the current setup creating manual work that should be handled by the process?

8. The Goal Is Connected Execution—not Just System Integration

It is easy to define success as "EWM sends data to TM and TM sends data back to EWM." That is a technical result, and it can be true while the operation still runs on phone calls.

Connected execution means something different. It means this runs as one flow:

┌──────────────────────┐
│ Transportation       │
│ Planning             │
└──────────┬───────────┘
          ↓
┌──────────────────────┐
│ Warehouse Readiness  │
└──────────┬───────────┘
          ↓
┌──────────────────────┐
│ Staging              │
└──────────┬───────────┘
          ↓
┌──────────────────────┐
│ Loading              │
└──────────┬───────────┘
          ↓
┌──────────────────────┐
│ Departure            │
└──────────┬───────────┘
          ↓
┌──────────────────────┐
│ Execution Status     │
└──────────┬───────────┘
          │
          └───────────────↩ Status Back to Transportation Planning

Each step informs the next. Each change in one step is visible to the others while there is still time to act on it.

Depending on the starting point and how the process is designed, a better-connected execution flow can help a business achieve:

• Better coordination between warehouse and transportation teams
• Less manual intervention day to day
• Clearer visibility of which shipments are ready
• Fewer delays that could have been avoided
• More consistent execution across shifts and sites
• Better return on the warehouse and transportation automation already in place

9. SCM Champs Helps Businesses Connect Warehouse and Transportation Execution

SCM Champs works in SAP supply chain execution. Our focus is SAP EWM and SAP TM, and the point where the two meet — integration, implementation, migration, configuration, and ongoing support, including warehouse automation and the systems around it.

The approach is straightforward: we look at warehouse and transportation together. Treating them as two separate systems is how the gap appears in the first place, so that is not where we start.

10. Is Your SAP EWM–TM Process Ready for Connected Execution?

If your business has warehouse automation, SAP EWM, SAP TM, or several SAP logistics systems, and your teams are still coordinating execution through spreadsheets, calls, and email, the issue is probably not the technology you own. It is more likely a gap in how the processes were designed and connected.

Request an SAP EWM–TM Integration Assessment

We review your current EWM, TM, warehouse automation, integration flows, and execution gaps, and show you where warehouse and transportation are falling out of sync.

Prefer to start with a conversation? Talk to an SAP EWM & TM expert at SCM Champs.