SAP Transportation Management Solutions

SAP S4 Hana SAP Transportation Management Event Management

Order Based Automated

Optimizer
SO/PO/STO Transportation SO/PO/STO
Freight Unit
Planning Scheduled
Requirement Building

Best Carrier Assign Load Begin

Freight Order
Creation Automatically
Load End
Delivery Based
Freight Unit Update
Delivery SAPTransportation
S4 Hana
Building Freight Order
Requirement Departure

Arrival

Upload
Begin

Upload End
 New S4 System with Embedded TM
TM in SAP S/4 HANA

SO/PO/STO

Delivery/Movement
Freight Units
Delivery proposal TM Operations
Charge Management
Freight Settlement
Carrier Invoice
S4 HANA TM Standalone S4 Embedded TM

Outbound
Delivery DTR
Delivery

EWM Freight Unit Freight Unit

Shipment Optional Freight Order Freight Order

Billing Freight Settlement Freight Settlement

Send to S4 Save &Transfer

FI Document
Invoice PO+SES Created
Posted
SAP Transportation Standalone

V/S

SAP TM S4 HANA Embedded

SAP Transportation Management

The main advantages of S4 HANA TM can be summarized as follows:

•Smaller database and hardware footprint

•Reduction in Total Cost of Ownership (TCO) due to smaller replication and monitoring effort
•Enhanced user experience leveraging S/4HANA "look and feel" and Fiori UI
•Remove the need to duplicate ERP customer, vendor and material master data into business partners and
products in TM, thereby removing the need for the Core Interface (CIF). ERP and TM share a single set of
harmonized master data objects.
•Real-time embedded analytics
•Integration with new S/4HANA Enterprise Management for managing transportation-related equipment
•Remove the need to duplicate ERP orders and deliveries into Order-based Transportation Requirement (OTR)
and Delivery-based Transportation Requirement (DTR) documents in TM. OTR and DTR documents are no
longer necessary. Orders and deliveries are able to convert directly into Freight Units, Freight Orders, etc.
SAP Transportation Management

Compared to SAP TM Standalone: The following functions are discontinued (“Simplification”) and
are not available in S/4HANA TM
• Integration into Customer Relationship Management(N/A)
• Integration of TM Resources to Enterprise Asset Management Objects (Equipment/Functional
Location)
• Selected Planning Functionality
• Condition-Based loading and unloading duration determination
• Fixed Loading and unloading duration determination per requirement document
• Condition-Based filtering for Transportation Cockpit (via Profile)
• Take away Load Cost Function from UI (Usage is possible via BAdI)
• Option for Time-Related Selection of Documents based on All Stop Times
• Transportation Proposal for multiple Freight Units at once
The usage of Package Building functions for Freight Order and Transportation Unit is not released for
S/4HANA TM 1809 until further notice (setting "Enable Pkg Building" in Freight Order Type and
Transportation Unit Type customizing).
SAP Transportation Management

Compared to SAP TM Standalone: The following functions are not yet released in S/4HANA TM :

• Integration of Forwarding Order/Forwarding Settlement Document with SAP S/4HANA Credit

Management
• Internal Settlement for Resources (other Internal Settlement Management scenarios are released)
• Group Logistics is only supported for side-by-side scenarios, but not yet for system internal processing
• Delivery Update (for example Delivery Split, Trigger of Goods Receipt/Goods Issue postings, Update of
Planning Status, Update of dates) is only supported for side-by-side scenarios, but not yet for system
internal processing
• Creation of Freight Units out of Scheduling Agreements (inbound and outbound) is only supported for side-by-side scenarios,
but not yet for system internal processing
• Sales Order Scheduling
• Business Partner hierarchy(Business Partner hierarchy is removed in SAP S/4HANA to avoid redundancy as customer hierarchy
is already available for the applications to consume).
SAP Transportation Management

1. One key limitation is the current absence of tools for migration of historical transaction data (Freight Units, Freight
Orders, etc.) You will need to deal with the conversion of open documents in the same manner as you would do so with
any other TMS implementation, doing so either manually or using custom scripts/programs to help with the conversion.
2. Fresh TM Implementation in S4 HANA with perplexed challenges which is currently unknown.

3. Currently on daily basis 15000 to 19000 FU are creating & 500 to 700 Freight orders
4. Event Management applications must be installed independent of S/4HANA TM as an add on for SAP S/4HANA is not
supported.

5. Large amount of event management data

6. S/4HANA TM 1809 not using single-system integration with EWM is done via A2A services in the
same way as cross system communication
Why we recommed SAP TM Standalone V/S SAP TM HANA:

Questions?

1. What is the Scope and Timeline for the Development of the Migration Tool?
2. What are the current limitations of the Migration Tool?
3. Why is the tool only available for SAP TM releases 9.5 and 9.6?
4. Using EM with SAP TM, is this also working with SAP S/4HANA? Is it also working in the phase
where SAP TM and SAP S/4HANA TM are running in parallel?
5. Why transactional documents are not supported by the Migration Tool?
6. The Migration Tool returns the warning "Invalid migration object xyz", when trying to start a
Simulation Run
7. Party Role Codes are not migrated to SAP S/4HANA
8. Some Business Partner Roles are missing in SAP S/4HANA
9. Is the Core Interface (CIF) still relevant for Master Data integration with TM in SAP S/4HANA?
10. How can customers phase-out the SAP TM system and at the same time switch-over to TM in
SAP S/4HANA in a side-by-side scenario?
11. In the side-by-side scenario some customizing settings of ECC are needed in TM in SAP
S/4HANA, which are not TM-specific, and so not part of the TM migration objects. How can those
settings be transferred to SAP S/4HANA?
12. How to migrate Custom Code and other Custom Objects to SAP S/4HANA?
13. How can customers start to determine, which custom development could be replaced by
standard features and functions, now being available in SAP S/4HANA?
S/4HANA TM 1809 not using single-system integration with EWM

• S/4HANA EWM 1809 to S/4HANA TM 1809 system internal integration is done via A2A services in the
same way as cross system communication

• General scope description of TM EWM integration applies

Event Management applications must be installed independent of S/4HANA TM 1809.

 SAP Event Management 9.2 SP05 onwards can be used with SAP S/4HANA and is compatible with SAP NetWeaver 7.50.
 You can use SAP Event Management 9.2 SP05 onwards  to track processes in SAP S/4HANA,in this case SAP Event
Management must be installed as a separate instance (side by side approach).
 Deploying SAP Event Management as an add on for SAP S/4HANA is not supported.