Embedded vs Decentralized SAP TM in S/4HANA: Differences

Embedded TM vs. Decentralized SAP TM in S/4HANA: Important Architectural Distinctions, Deployment Scenarios, and Decision Matrix

The end of life of the Logistics Execution Transportation (LE-TRA) and the last release of SAP TM 9.6 has compelled Enterprise Architecture teams to redesign and update their IT supply chain roadmaps. Modern supply chain requires transport management systems that incorporate automated carrier tendering, real-time logistics visibility, and transport load optimization. Within an SAP S/4HANA landscape, these modern transport management functionalities can only be enabled by a single fundamental decision between deploying Embedded SAP TM or Decentralized SAP TM on S/4HANA.

The decision between an embedded digital core with a decentralized strategy determines system latency, maintenance burden, governance of master data, and the TCO. The following paper delineates the architectural and data flow distinctions, the deployment scenarios, and the decision matrix for the enterprise architecture blueprinting exercise.

2. Embedded SAP TM in S/4HANA

SAP recommends implementing Embedded SAP TM in S/4HANA over traditional implementations of SAP TM.

Both embedded and proprietary (S/4 Transportation Management) logistic service offerings and supporting business processes sit as integral components of the S/4HANA suite providing capability and functionally unique for an enterprise resource planning (ERP) requirement.

Embedded logistics service offerings include: shipping, freight order, settlement, and freight unit management with built-in process and business logic. There are no transport lines to be maintained. As logistics modules have been 'embedded' within the S/4HANA suite, these maintain, read, and/or write data to the Unified HANA In-memory database. Embedded logistics service offerings also provide the functionality to read vendor locations, shipping locations, and carrier addresses through business partners and their master data. Additionally, materials and product hierarchies can be converted to mass units.

Proprietary logistics service offerings provide the same functionality and business processes (e.g. integrated procurement to supply, sales to operations, manufacturing to logistics) as embedded logistics service offerings. These logistics service offerings can also integrate freight settlement transactions to their service execution system (SES).

Direct Freight Unit (FU) Building: When a Sales Order (SD), Purchase Order (MM), or Outbound/Inbound Delivery get saved, S/4HANA triggers internal business object calls for the direct creation of Freight Units.

Synchronous Execution: Updates to sales order quantities or delivery split dates are synchronized with Freight Units in real time, avoiding status sync failures.

Licensing Matrix: Basic Shipping vs. Advanced TM

When Embedded TM is implemented, not all transport-related functions are made available. SAP divides functions into two separate license levels.

1. Basic Shipping Management (Included in S/4HANA Digital Core License): This level comprises order integration, manual planning in the Transportation Cockpit, basic carrier selection, delivery creation through TM, freight job execution, and standard outputs. It offers an operational replacement for the former LE-TRA.
2. Supply Chain for Transportation Management/ Advanced TM (Add-On License): This level offers optimization of automated Vehicle Scheduling & Routing (VSR), dynamic load building (3D layout calculation), carrier tendering, advanced driver management, and dispute management integrated with portals for the management of freight agreements and settlements.

2. Deep Dive: Decentralized (Side-by-Side) SAP TM in S/4HANA

In S/4HANA, decentralized SAP TM is a dedicated instance for TM planning and execution and is deployed as a standalone system. It connects to one or more SAP ERP backend systems (or even non-SAP ERP systems) using web services, OData APIs, or IDocs.

• ERP Backend System 1 (SAP ECC 6.0 or S/4HANA) and ERP Backend System 2 (Non-SAP / Legacy ERP) connect via Web Services / Async APIs / IDocs
• Both connect into the Decentralized SAP TM (Standalone S/4HANA Instance), which contains:
  • Master Data Rep. (API / DRFOF)
  • OTR / DTR Engine (Doc Abstraction)
  • VSR Optimizer & Transportation Cockpit
• All of this runs on a Dedicated HANA Database Instance

Technical Data Flow & Synchronization

• Master Data Replication: As the engine is deployed on a standalone server, continuous synchronization of master data will be required; therefore, either the Data Replication Framework (DRF) or Web Services can be used. Business Partner, Location, and Material data are mirrored from source ERPs into the TM hub.
• Transactional Document Abstraction: Since the system is unable to perform synchronous internal database calls to foreign ERP backends, it uses Order-Based Transportation Requirements (OTR) and Delivery-Based Transportation Requirements (DTR) or normalized API payload structures to convert external orders into internal Freight Units.

Operational Independence

Decentralization SAP TM from ERP systems enhances operational independence as it decouples the transportation engine from the background maintenance of ERP systems:

• 24/7 High-Availability Operations: Background maintenance of ERP systems eliminates the capability of Warehouses, Distribution yards, and Dispatch centers to undertake planning, tendering, and dispatch of trucks. Decentralized SAP TM ensures planning, tendering, and dispatch of trucks continues to function during ERP backend maintenance windows.
• Isolated Performance: Heavy automated planning runs (e.g., global overnight VSR optimizer runs processing millions of order lines) do not impact the core transactional ERP system with regards to consumption of Central Processing Units (CPU) or memory.

4. Key Business Deployment Scenarios

Architectural decisions should reflect operational requirements, IT landscapes, and organizational scale.

Small Closed Scope Implementations (50 to 100 Users)

Embedded TM incorporates a single instance of the SAP HANA database that covers the operational, hardware, and integration aspects of the system. This lowers the costs associated with implementation and improves flexibility when compared to a Decentralized (Side-by-Side) scenario. The Decentralized scenario requires multiple database instances (ERP + dedicated TM Hub). This would drive costs up for deployment, system maintenance, and increasing complexity for further integrations. As larger implementations would necessitate more elaborate integrations with additional ERP systems, an Embedded solution would continue to remain the more flexible deployment option.

Large Complex Implementations

Large complex implementations would benefit from a side-by-side approach. With a side-by-side scenario, the SAP TM hub can be upgraded independently of the rest of an organization's SAP systems. Maintenance and upgrades of TM would not disrupt the business operations of the enterprise. For large complex implementations, an embedded approach would be less flexible due to the coupling of release schedules.

Medium to Large Multi-ERP Implementations

A multi-ERP scenario would benefit from an embedded approach, whereas a side-by-side approach would benefit from a large complex implementation. A side-by-side embedded approach allows the SAP systems to remain coupled, whereas with a side-by-side approach, multiple ERP systems can be either SAP ECC or third-party.

Evaluating Landscape Requirements

• IF Multi-ERP Environment, Multi-S/4HANA Instances AND Multi-Instance O2C AND Multi-Instance P2P AND 24/7 Non-Stop Shipping? THEN Decentralized SAP TM
• OTHERWISE Embedded SAP TM

Scenario A: Embedded SAP TM

1. Single S/4HANA Digital Core Strategy: Organizations consolidate their worldwide operations under a single S/4HANA system.
2. Simplified IT Footprint: Organizations aim for a smaller IT footprint by eliminating middleware, and removing integration monitoring queues (SAP AIF/PI/PO), as well as by eliminating master data replication overhead.
3. Unified Warehousing & Transportation: Project uses Embedded EWM together with TM using Advanced Shipping & Receiving (ASR), realizing direct, unbuffered handovers at the door and the loading gate.
4. Substantial to High Planning Volumes: The demands on freight planning can be efficiently satisfied without overburdening the resources of the host core database.

Scenario B: Decentralized/Side-by-Side SAP TM

1. Heterogeneous/Multi-ERP Landscape: A company has many SAP ECC legacy systems across the regions as well as non-SAP ERPs or acquired businesses that cannot be easily moved to a single instance of S/4HANA.
2. Global 3PL or Logistics Service Provider (LSP) Activities: Transportation execution is run as a centralized shared-service hub providing freight brokerage or group transport for various corporate divisions.
3. 24/7 Mission-Critical Dispatch: Facilities with high-volume shipping can't afford to have dispatch held up due to maintenance and upgrade intervals of the back-end ERPs.
4. Divergent Release Strategies: The logistics team needs to have the flexibility of implementing new innovations of TM, on-premise or cloud, in a much faster time frame than what is possible for other functions of the organization.

5. Advanced Technical Features & Innovations

ASR (Advanced Shipping & Receiving)

In legacy setups, extending EWM to TM through document mapping using Transportation Units (TUs) meant complex integrations.

In S/4HANA Embedded architectures, SAP introduced ASR (Advanced Shipping & Receiving). ASR allows for simplified integration, enabling EWM and TM to implement a single Freight Order. Warehouse door status (check-in, arrival at the door, start of loading, completion of loading, goods issued) updates are done directly to the Freight Order in real time. This eliminates the need for queuing between warehouse loading docks and freight planners.

• Sales Order / Delivery flows into Freight Unit (TM)
• Freight Unit (TM) flows into Freight Order
• Freight Order shares a single object via ASR with the EWM Warehouse Door
• On the Freight Order side: Vehicle Check-In, Door Assignment, Departure Confirmation
• On the EWM Warehouse Door side: Loading Started, Goods Issue Posted

BN4L (SAP Business Network for Logistics)

Both Embedded and Decentralized deployments connect natively to BN4L (SAP Business Network for Logistics). BN4L broadens a company's internal TM processes to external transport partners:

• Automated Tendering: Freight orders in TM propagate to BN4L where a cloud portal is used by carriers for viewing, accepting, or rejecting bids.
• Automated Exception Management: Real-time truck positions are integrated with TM's Freight Order.
• Digital Freight Claims: Carriers digitize their invoices in order to dispute potential charge discrepancies and initiate workflow approvals in TM Freight Settlement documents.

Decision Matrix & Blueprinting Checklist for Enterprise Architects

This framework can be used during the early stages of project blueprinting to determine the appropriate deployment model:

Criteria	Condition	Score
1. Landscape Diversity	Single S/4HANA instance?	+1 Embedded
1. Landscape Diversity	Multiple ERPs (ECC, S/4, Non-SAP)?	+1 Decentralized
2. Operational Uptime	Standard maintenance windows acceptable?	+1 Embedded
2. Operational Uptime	24/7 non-stop logistics execution required?	+1 Decentralized
3. Data & Process Simplicity	Zero-interface architecture preferred?	+1 Embedded
3. Data & Process Simplicity	Isolated processing for high volume preferred?	+1 Decentralized
4. Warehouse Execution (EWM Integration)	Simplified Advanced Shipping & Receiving (ASR) planned?	+1 Embedded
4. Warehouse Execution (EWM Integration)	Complex legacy TU-based EWM cross-system links?	+1 Decentralized
5. TCO & Governance	Tight budget, simple maintenance, unified licensing?	+1 Embedded
5. TCO & Governance	Independent release budgets, flexible upgrade schedules?	+1 Decentralized

Frequently Asked Questions (FAQs)

1. Is Basic Transportation Management in S/4HANA License Independent?

No. Basic Transportation Management is a part of SAP S/4HANA Digital Core, and it replaces LE-TRA for standard shipping, manual planning, and baseline freight agreement execution. Other advanced features—such as VSR optimization, automated tendering, 3D load planning, and carrier disputes management—need the license of SAP Supply Chain for Transportation Management.

2. What happens to legacy LE-TRA processing in S/4HANA?

In new releases of S/4HANA, LE-TRA shipment processing (VT01N, VT02N) falls under SAP's compatibility scope and is thus deprecated. When migrating from SAP ECC to S/4HANA, organizations are obligated to move shipping execution to Embedded Basic TM, or Advanced TM.

3. Can I migrate from Embedded TM to Decentralized TM later if my company acquires new divisions?

Yes. Both models rely on the same core underlying TM data structures (Freight Units, Freight Orders, Freight Agreements), so logic and custom routines would be relatively easy to migrate. Switching to a decentralized landscape would require the configuring of the DRF (Data Replication Framework) along with the inter-API and data mapping.

4. How does Embedded TM affect database sizing on my S/4HANA host instance?

For Embedded TM, transactional data are stored directly in the primary S/4HANA database. Although master data deduplication helps with saving storage space, high volumes of real-time GPS tracking data or automated planning runs can increase both CPU and memory resources. Calculations in S/4HANA QuickSizer need to consider volumes of Freight Units and Freight Orders.

Why Choose ERPVITS?

• Practical Training with Live S/4HANA Sandbox: Gain and refine your S/4HANA skills by configuring the Embedded TM, Freight Units, VSR Optimizers, and Settlement Documents on actual SAP S/4HANA servers.
• Instructor-Led Training with Experts: Learn with SAP Certified Senior Supply Chain Architects who have global implementation experience.
• Included Case Studies: Analyze end-to-end Order-to-Cash and Procure-to-Pay logistics flows and integrate EWM-TM, as well as configure ASR.
• Convenient Training: Live, pre-booked weekend or weekday sessions, ready for working professionals worldwide.

Advance your career and acquire SAP S/4HANA Logistics. Sign up for demos at ERPVITS and enroll in our upcoming SAP TM Training sessions.