SAP EWM and TM Integration: Process Flow and Configuration

SAP EWM and TM integration connects SAP Extended Warehouse Management with SAP Transportation Management in a single logistics flow. It links warehouse picking, packing, and loading with transportation planning through shared, real-time data.

Because SAP S/4HANA can run EWM and TM in the same system (embedded), the entire chain from outbound delivery to vehicle dispatch runs without breaks. This article covers the business value, process flow, architecture options, and core configuration steps of SAP EWM and TM integration.

What Is SAP EWM and TM Integration?

In the supply chain, warehousing and transportation are two links you cannot separate. SAP EWM improves the efficiency of in-warehouse operations, while SAP TM optimizes transportation resources (vehicles, trailers, capacity) to reduce freight costs. Integrating these two modules pushes transportation planning decisions directly into warehouse execution.

In SAP S/4HANA, this integration works through two messaging approaches. The classic LDAP (Loading and Delivery Appointment) based integration handles communication between TM and EWM through messaging between the freight order and the transportation unit. The newer ASR (Advanced Shipping and Receiving) approach merges shipping and receiving processes into a shared data model.

Why Integrate SAP EWM and TM?

When warehouse and transportation systems run separately, data transfer between the two sides is usually manual and error-prone. Integration changes this picture and delivers the following concrete benefits:

• Real-time visibility: Changes in the transportation plan reflect in the warehouse instantly, and the loading status in the warehouse becomes visible on the transportation side.
• Lower freight and labor costs: The system optimizes vehicle capacity and creates warehouse tasks according to the transportation sequence.
• Packaging optimization: The package building function in TM determines the pallets that use vehicle capacity most efficiently and transfers this information directly to EWM.
• Fewer errors and less rework: A shared data model removes the risk of inconsistency between the two systems.
• Simpler landscape: In the embedded scenario, a single S/4HANA system runs everything, so there is no need for separate tools or complex middleware.

The licensing dimension of this integration directly affects project architecture and cost. For guidance on which license model to choose, see our article on the SAP EWM and TM licensing decision.

Process Flow in SAP EWM and TM Integration

The best way to understand how the integration works is to follow a typical outbound delivery process step by step. In SAP S/4HANA with embedded EWM and TM, the flow proceeds as follows:

• 1. Outbound Delivery (OBD): The system creates an outbound delivery in the S/4HANA core based on the sales order.
• 2. Freight Unit: Embedded TM produces a freight unit from the delivery using the Freight Unit Builder rule.
• 3. Outbound Delivery Order (ODO): The system distributes the delivery to EWM, and an outbound delivery order is created in the warehouse.
• 4. Freight Order: Transportation optimization in TM (manual or automatic) creates the freight order and matches it with a vehicle.
• 5. Package planning: The package building function in TM creates pallets with the appropriate packaging material.
• 6. Transportation Unit (TU) and PSHU: When the loading instruction reaches EWM from TM, EWM creates a transportation unit and a planned shipping handling unit (PSHU).
• 7. Picking and loading: EWM creates warehouse tasks and Pick-HUs by referencing the PSHUs, and workers load the picked goods onto the vehicle according to the loading sequence in TM.

The handling units created in this flow also appear in the Package ID field of the freight order on the TM side after they are created in EWM. This gives both modules full traceability. For more on the handling unit concept, see what is a handling unit.

Architecture Options: Embedded and Decentralized

You can set up SAP EWM and TM integration in two main deployment models:

• Embedded (One Client): EWM and TM run in the same S/4HANA system and the same client. Setup and maintenance are simpler, and the two modules communicate within the same system. This is the model SAP recommends for most mid-size and large enterprises.
• Decentralized: EWM runs as a separate system instance and communicates with TM through web services. High-volume warehouses that run 24/7 and require an independent upgrade cycle choose this model.

Even in the embedded scenario, messaging between EWM and TM runs through point-to-point communication and SOA Manager. Therefore, the team must correctly complete steps such as the SLD check, service user definition, and integration scenario configuration on the system side.

Core Configuration Steps

For SAP EWM and TM integration to work reliably, the team must configure a few decisive settings correctly. The key items are:

• EWM Integration Profile: On the TM side, the team defines the integration profile with the Define EWM Integration Profile step. This profile determines how the loading instruction is triggered from TM to EWM.
• Freight Order Type: Three settings in the freight order type must be correct for the integration to work.
• Document Creation Relevance = E: This value means “transportation activity creation in SAP EWM.” Without it, the system cannot communicate with EWM.
• Immediate Processing: If the team does not select this checkbox, the system does not set the update propagation indicator at the freight unit level, which can cause various errors later.
• Output Profile: If this field stays empty, the system does not trigger the PPF action and cannot communicate with EWM. The standard /SCMTMS/TOR profile meets this need.

Beyond these settings, the team also configures vehicle and transportation unit forming parameters, packaging material types, and master data mappings according to the scenario. Completing the configuration steps in the correct order and in full is decisive for preventing message errors after go-live.

The Importance of Expert Support in SAP EWM and TM Integration

SAP EWM and TM integration brings together two powerful modules, so it requires both functional and technical depth. From SLD and SOA Manager setup to freight order type settings, and from packaging optimization to master data synchronization, many details require the correct design. Experienced consulting shortens project time by selecting the right architecture and license model, builds the integration soundly, and manages post go-live optimization. MDP Group stands by you with experienced SAP EWM consultants to integrate your warehouse and transportation processes end to end. To bring your warehouse and transportation operations into a single flow, contact us.

Frequently Asked Questions

What does SAP EWM and TM integration do?

SAP EWM and TM integration combines warehouse operations (picking, packing, loading) with transportation planning in a single data flow. Decisions in the transportation plan reflect in the warehouse instantly; the system optimizes vehicle capacity, reduces freight cost, and removes manual data transfer and error risk between the two systems.

What is the difference between embedded and decentralized EWM-TM integration?

In the embedded scenario, EWM and TM run in the same S/4HANA system and client, so setup and maintenance are simpler. In the decentralized scenario, EWM runs as a separate system and communicates with TM through web services; high-volume warehouses that require an independent upgrade cycle choose this model.

What is the difference between LDAP and ASR integration?

LDAP (Loading and Delivery Appointment) based integration is the classic messaging method between TM and EWM. ASR (Advanced Shipping and Receiving) is the newer approach that merges shipping and receiving processes into a shared data model. For new projects, SAP may recommend the ASR model depending on release compatibility.

Which configuration steps are decisive for the integration?

The most important settings are defining the EWM integration profile, setting Document Creation Relevance to “E” in the freight order type, selecting the Immediate Processing checkbox, and defining an output profile (for example, /SCMTMS/TOR). The team must also complete the SLD check and the integration scenario setup through SOA Manager correctly.

References

SAP Extended Warehouse Management – SAP Help Portal
What Is SAP EWM – MDP Group
SAP EWM and TM Licensing Decision – MDP Group

Birsu Küçükyılmaz

SAP EWM Consultant