How to translate

LE-TRA Features to Basic TM in S/4HANA

Christina Reutter, SAP
October 17, 2023
Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.

Public 2
How to use this presentation

Objective:

• Initial comparison of LE-TRA and basic Transportation Management in S/4HANA

• Suggestion how you could use main features of LE-TRA with basic Transportation Management
in S/4HANA

Target Customers:

• LE-TRA customers which want to move to S/4HANA

Public 3
Preview

• Which LE-TRA capabilities are available in basic Transportation Management and at which
time?

• Comparing processes of LE-TRA and basic Transportation Management

• Upselling chance:
What is the value of full-blown S/4HANA TM compared to LE-TRA?

• Business value of S/4HANA TM compared to LE-TRA

• Further Information on SAP Transportation Management

Public 4
 Transportation Management @ SAP (on premise solutions)
SAP Business Suite:
SAP Business Suite

SAP Business Suite * End of Mainstream

Maintenance 2027 * Mainstream Maintenance depends on the SAP Netweaver components
https://support.sap.com/en/release-upgrade-maintenance/maintenance-information/maintenance-strategy.html

SCM SAP Transportation Management - SAP Transportation Management (last Release SAP TM 9.6)

ERP LE-TRA
- SAP ERP with Logistics Execution - Transportation

S/4HANA Supply Chain for SAP S/4HANA:

Products
Transportation Management
SAP S/4HANA OP

- Supply Chain for Transportation Management

Completely use of all TM features – requires Advanced TM license
Transportation Management
Digital Core
- Transportation Management
LE-TRA
** Compatibitily Scope Main features released for basic use of Transportation Management
with no additional engine License

- Logistics Execution – Transportation

** Compatibility Scope planned for 2030
2269324 - Compatibility Scope Matrix for SAP S/4HANA on-premise

Public 5
 Transportation Management in SAP S/4HANA (on premise)

S/4HANA Enterprise Management S/4HANA Enterprise Management S/4HANA Enterprise Management

License View

Basic Transportation Advanced Advanced

Transportation
Basic Shipping Shipping Management Transportation Transportation
Management**
Management Management**
Technical View

SAP S/4HANA Supply Chain for transportation management

SAP S/4HANA Supply Chain for transportation management

S/4HANA code line S/4HANA code line

LE-TRA LE-TRA

Compatibility Scope Compatibility Scope S/4HANA code line

Prior to September 2017 Today Planned long term

**Requires engine license

This is the current state of planning and may be changed by SAP at any time.
Public 6
Basic Shipping and Transportation Management within SAP S/4HANA (OP)
• Defined collection of business processes relevant for shipping within
SAP S/4HANA Enterprise Management

• The processes can be implemented with SAP S/4HANA Release 1511 with LE-TRA
Product S/4HANA Supply Chain for
and used until end of life of the compatibility scope (Solution Capability: Basic
Transportation Management
Shipping) 2269324 - Compatibility Scope Matrix for SAP S/4HANA on-premise

Digital Core Transportation Management

• The main functions of LE-TRA will be eventually replaced with the Transportation
Management functions within SAP S/4HANA Enterprise Management. Due to the
development of the freight processes in Transportation Management, the functions
LE-TRA
might have been realized differently than they did in LE-TRA.
Compatibility Scope It is planned that the processes can be implemented with selected functions of
SAP S/4HANA TM* -> (Solution Capability: Transportation Management).

• Both technical applications are independent of each other and can then be used
next to each other on the same S/4HANA database instance. They have no data
Enterprise Management exchange / integration within the shipping process

• Long term the collection of basic shipping processes will only be realized by using
selected functions of SAP S/4 HANA TM* -> (Solution Capability: Transportation
Management).

• As of the 2020 release Basic Shipping is the name for the LE-TRA compatibility
scope. Basic transportation functionality included in the S/4 HANA license is
Transportation Management

*SAP S/4HANA Supply Chain for Transportation Management

Public 7
 basic Transportation Management Vs Advanced Transportation Management
basic Capabilities LE-TRA basic Advanced
Capabilities LE-TRA Advanced
Transportation Transportation
Management TM Management TM

Delivery based Transportation Management Automated Carrier Selection

Combine Inbound and outbound deliveries Scheduling

Order based Transportation Management Dangerous Goods Management

Manual Planning Charge Calculation

Automatic Planning with Transportation Planning Cost distribution

Cockpit
(incl. VSR Optimizer, Gantt charts, map based planning, Freight Cost Settlement
package building, load planning, scheduling, etc.)
Customer billing for Shipper scenario
Driver Management

Mode specific capabilities for air, ocean, rail planning Self Billing / Credit Memo

Strategic Freight Management (Procurement/Selling) Incoming invoice verification

Group Logistics Management Analytics

Event Management Integration Data Aging

GTS Integration Forwarding Order Management

Tendering Forwarding Settlement

LBN Integration (e.g. GTT & Freight Collaboration) Internal Settlement

ASR – direct integration TM-EWM Interfaces (including ASN, Prod Compl, GTS)
Public 8
Consignment (additional hierarchy in freight order) Dispute Management
Which LE-TRA capabilities are available in S/4HANA basic Transportation
Management and at which time?
LE-TRA capabilities at a glance (1/2)

Available in basic LE-TRA functional

Overall Process LE-TRA Capability Transportation realization in basic
Management Transportation Management

Order Management Creating Shipment 1709 Equivalent

Order Management Delivery based shipment creation 1709 Equivalent

Planning Manual Planning with selection criteria 1709 Different

Planning Manual Planning in Cockpit 2022 Equivalent

Planning Planning with Collective Processing 2022 Different

Planning Scheduling 1709 Different

Planning Event based Triggering or preceding documents 2020 / 2023 Equivalent

Planning External Planning 2023 Equivalent

Public 10
LE-TRA capabilities at a glance (2/2)

Available in basic
LE-TRA process/ functional
Overall Process LE-TRA Capability Transportation
realization in embedded TM
Management

Freight Execution & Monitoring Subcontracting 1709 Equivalent

Freight Execution & Monitoring Maintaining Deadlines/Events 1709 Equivalent

Freight Execution & Monitoring Status Info 1709 Equivalent

Freight Execution & Monitoring Delivery Split 2022 Different

Freight Execution & Monitoring Dangerous Goods Management 1709 Equivalent

Freight Execution & Monitoring Output Management 1709 Different

Charge Calculation Charge Calculation, Cost distribution 1709 Equivalent

Freight Settlement Credit Memo / Self Billing 1709 Equivalent

Freight Settlement Incoming invoice verification for freight invoices 1709 Equivalent

Public 11
Comparing processes of LE-TRA and basic Transportation
Management
How do LE-TRA processes work now in basic Transportation Management?
Legend

• LE-TRA stands for the transportation component in Logistic Execution module

• basic Transportation Management stands for the basic functionalities within SAP S/4HANA
Transportation Management module

• The words in yellow means planning only - subject to change.

• The words in blue means that basic Transportation Management has the advantages over
LE-TRA.

Public 13
Overview of the processes

 Basic Settings

 Transportation Planning

 Shipment Execution

 Monitoring Shipments

 Shipment Cost Processing

 Interfaces

 Miscellaneous

Public 14
Basic Settings
 Enterprise Structure

LE-TRA basic Transportation Management

Client

Company Code

Sales Purchase Plant

Organization Organization (Storage Location)

Purchase Warehouse
Distribution Group Number
Division
Channel

Shipping Point
Sales Area

Transportation
Planning Point
Sales Office Sales Group
• In S/4 TM, the organizational structure can be based on the structure of a
connected S/4 ERP system:
• A Company Code is a legal entity & independent accounting unit. ‒ Corporate Organization
‒ Company Organization
• Sales Organization distributes goods & services. ‒ Sales Organization, Office and Group
• Purchase Organization is responsible for external procurement. ‒ Purchase Organization and Group
‒ Planning and Execution Organization and Group
• Warehouse Number, Shipping Point and Transportation Planning Point are
organizational units in Logistics Execution. • S/4 TM maps its own Org. Units with S/4 ERP Org. Units through the field
“BSG Org. Unit.”
Public • Plant and Shipping Point are created as Locations in S/4 TM 16
Transportation Planning Point

LE-TRA basic Transportation Management

• Planning and Execution Organization is responsible for

• The transportation planning point is an organizational unit,
which consists of a group of employees responsible for
organizing transportation activities.
Public
transportation planning.
• Purchasing Organization is responsible for procuring the
necessary services from the carriers.
• Derived from Purchasing Organization, Company Code is
enabled on Freight Documents relevant for subcontracting (in
release 2020). 17
Transportation Relevance

LE-TRA basic Transportation Management

• Shipments do not need to be planned for all deliveries. • Activation of S/4 TM integration for deliveries is
• The delivery type, the delivery item category, and the controlled by the combination of Shipping Point,
route in the delivery uses transportation relevance to Delivery type and Shipping Condition.
control whether a shipment can be created or not.

Public 18
Non-stock Material

LE-TRA basic Transportation Management

• Delivery with non-stock material can be planned • Freight Unit will not be created for the non-stock
in the LE-TRA Shipment. material in the standard system.

• Use BAdI /SCMTMS/BADI_LOGINT_CHG_TTRQ

to change the standard logic and set transportation
relevance for non-stock items.

Public 19
Information Relevant for Transportation

LE-TRA basic Transportation Management

• Mode of Transport • Transportation Mode (TM specific)

• Shipping Type • Transportation Mode Category

• Transportation Connection Point • Location

• Shipping Conditions • Shipping Conditions

• Transportation Groups • Transportation Groups

• Route and Route Determination by Transportation • TM Default Route / Transportation Lane

Zone / Shipping Condition / Transportation Group /
Weight Group

• Route Schedule
• Road Carrier Schedule
• Material Freight Groups
• Material freight groups / Product Freight Groups
• Freight Code Sets and Freight Codes
• Freight Code Sets and Freight Codes

Public 20
LE-TRA: Route (latest change can be seen on next slide)

• A route is the journey to be covered between a departure point and a

destination point. A route can be defined in great detail and consists of
individual stages, but it can also be a quite general description or even
simple a destination area.
• A route can contain many pieces of information that are important for the
shipment, such as distance, transportation lead time, travel duration,
shipping type, service agent, and so on.
Route Information
• Route determination:
‒ The system determines the route for each order item.
‒ The route can be adopted from the order item or redetermined in the
outbound delivery.
‒ In the shipment, a different route can be entered. This route does not
have to be identical to one of the routes in the deliveries. It is also
possible to transfer the route from the deliveries to the shipment (if it is
the same for all deliveries).

Route Determination

Public 21
Compatibility Scope for LE-TRA - What is changing?

• LE-TRA Route and corresponding objects are removed from the compatibility scope.
In other words: The customers can use those objects after 2030 in SAP S/4HANA without
Product S/4HANA Supply Chain for additional license costs.
Transportation Management
• That allows the customer to use these objects for existing funcionality in other
applications e.g. scheduling in sales order / stock transport order / delivery, etc.
Digital Core Transportation Management
• Important: All other objects from LE-TRA which are used for the Transportation
functionality will remain in the Compatibility Scope. And cannot be used after 2030.
LE-TRA Route LE-TRA -Transportation

Compatibility Scope This would primarily be the shipment document + shipment cost document and all
corresponding objects / customizing / master data / interfaces.

• The LE-TRA Route in SAP S/4HANA is no strategic object:

SAP does not plan further innovations for those objects. As well no integration into new
Enterprise Management innovations e.g. Product Compliance.
In particular no integration into SAP S/4HANA Supply Chain for Transportation
Management is available or planned.

• The strategic GO-TO solution for an integrated, TM based scheduling for sales order /
deliveries is on the SAP S/4HANA Roadmap:
The new Sales Order Scheduling which allows to plan via the TM Freight Unit.

*SAP S/4HANA Supply Chain for Transportation Management

Public 22
basic Transportation Management: Default Route

• A default route defines a location sequence for a given

source and destination, which can be locations or zones.
• For a transport from a source to a destination, the default
route serves as a template guiding the transportation
through the network. For example, for the intermodal
transports, default routes can predefine the sequence of
transhipment locations.
Default Route defined in S/4 TM
• In the default route, you can specify the transportation
mode, carrier, and so on, for each transportation stage.
• During freight unit building, freight unit stages can be
automatically generated based on a default route. Then the
freight unit stages are created according to the default
route’s location sequence.

Default Route applied in the Freight Unit

Public 23
basic Transportation Management: Transportation Lanes
Distribution
Center Transportation Lanes

• Transportation lanes describe the reachability of locations within the

transportation network. A valid transportation lane indicates that the
destination can be directly reached from the source with certain
means of transport and certain carriers. Location
Customer

• A transportation lane can be maintained between:

‒ Two locations Supplier

‒ A location and a transportation zone

‒ Two transportation zones Transportation
Zone

‒ A transportation zone itself

• Information assigned to a transportation Lane:
‒ Start location and destination location
‒ Means of transport
‒ Carrier per means of transport

Public 24
Transportation Lane defined in S/4 TM
LE-TRA: Transportation Connection Point

• Point or location at which the leg of a route begins or ends.

A transportation connection point can represent an address, a load
transfer point or a border crossing. It can also refer to a location
defined in the master data (shipping point, plant, customer, supplier)
• You can define a transportation connection point in more detail by
assigning features to it:
Load transfer point as port, airport, train station, etc.
Border crossing point with customs office
Train station data
Duration of stay
Address or reference to master data location

Route Determination

Public 25
basic Transportation Management: Service Items

• It is possible to have LE-TRA like fields on the service item

- duration of service
- location of service (independent from the transportation route)
- a deviating service provider (vendor)
- assign charge types to service types
• The information ca be used as additional basis for freight cost
calculation (new calculation bases for location, duration)
• The introduction of deviating service provider for service items,
service location and service duration allows charges similar as for
additional freight agreement parties in separate freight settlement
documents
• Enhanced ‘Service item only’ view
• Runs embedded only

Public 26
Transportation Lane defined in S/4 TM
basic Transportation Management: Service Items

Carrier Dependent Service Type Search Help Carrier Service Code adapted to alternative
considers Deviating Service Provider Service Provider

Public 27
Partner Determination

LE-TRA basic Transportation Management

• To define the rules that should be used to perform • To enable the system to automatically determine the
automatic partner determination. business partners in different business document types.

Public 28
Transportation Planning
LE-TRA: Creating Shipments

• Shipments are collections of inbound or outbound deliveries that are

shipped together, according to different grouping criteria.
• Transportation-relevant information is stored for each order item, as
agreements made with the customer regarding the shipment. The same
data can be defined in the header of the delivery document.
• The transportation-relevant information is copied from the order to the
outbound delivery header, and thus provides the split criteria for outbound
deliveries. Copying Transportation-Relevant Information

• The transportation-relevant information can be used as selection criteria

when creating shipments. The information can also be copied from the
outbound deliveries to the shipment, if it is unique.
• System contains different options for creating shipments:
‒ Manual creation using the “create shipment” function (TA: VT01N)
‒ Use a collective processing run to create shipments automatically
‒ If the shipments are created and optimized by an external
transportation planning system, you can link this to the ERP system
with an interface.

Options for Creating Shipments

Public 30
LE-TRA: Manual Planning

• Create shipments by combining outbound or

inbound deliveries

• Manually plan deliveries that are chosen using

different selection criteria. Define selection variants
to simplify the selection procedure

• Selected delivery documents are listed in the

shipment screen. Manually assign shipments. LE-TRA shipment screen

• Manual shipment creation with planning proposal:

‒ Select deliveries due for transportation manually
‒ Combine selected deliveries in shipments
‒ Change or edit the created shipments manually before
saving

Public 31
basic Transportation Management: Freight Order Creation

• Plan a Freight Order by

assigning Freight Units.
Freight Unit can either be
derived from outbound or
inbound deliveries. (No
combined inbound and
outbound delivery.)

• Manually plan via personal

worklists (POWL).

• System default Freight

Order type will be applied.

• Choose selection criteria

via query

Public 32
basic Transportation Management: Planning in Transportation Cockpit

• Pre-defined page layouts for basic TM

Public 33
Insert additional Capacity Document into Planning Screen
LE-TRA
• Insert additional shipment into shipment delivery
planning screen
‒ Button ‘Shipments’ (Ctrl+F7) can select and add
further shipments into the screen
‒ Button ‘New Shipment’ can create a new shipment
document
Public
basic Transportation Management
• In basic TM standard page layout
‒ ‘Insert’ button can add additional Freight Orders /
Freight Bookings
‒ ‘New’ button can create new Freight Orders / Freight
Bookings. Freight Order type is defaulted as the
definition in the Planning Profile and can be manually
overwritten.
34
Move DeIiveries

LE-TRA basic Transportation Management

• Move deliveries from one shipment to another via:
‒ Drag and drop
‒ Using functions in TA VT01 / VT02
‒ Re-sort functionality
• Freight units can be moved from one freight order to
another in the basic TM standard page layout via:
‒ Drag Freight Units to another Freight Order
‒ Drag Freight Order to another Freight Order
‒ Select Freight Units and Freight Order, then choose
‘Reassign’ button

Public 35
Remove DeIiveries from a Shipment

LE-TRA basic Transportation Management

• To remove a delivery from a shipment: • Delete the Freight Units from the Freight Order
‒ Drag and drop
‒ Use button ‘Remove delivery from shipment’

Public 36
Subsequent Delivery Split in Shipments
LE-TRA
• The split can be carried out in outbound deliveries
• The delivery split could also take place during loading
or transportation planning. The system automatically
generates further outbound deliveries for the split
quantities when saving the shipment
Public
basic Transportation Management
• The delivery split can be done in S/4 ERP and trigger the
required changes in S/4 TM
• The delivery split and update can also be triggered by S/4
TM based on planning changes. Partial quantities of the
Freight Unit items can be manually split to create new
Freight Unit. If Freight Units of a delivery are planned on
different Freight Orders with respect to their first or last
stage, an automatic delivery split will be triggered in S/4
ERP after relevance check.
37
Creating Shipment Documents for Individual Deliveries

LE-TRA basic Transportation Management

• To create one shipment document for each delivery • Set up the freight building rule to ensure 1 v.s. 1
relationship between delivery and Freight Unit
• Create multiple Freight Orders for the selected Freight
Units

Public 38
LE-TRA: Planning with collective processing

• From shipment screen select deliveries and create

desired shipments based on specific rules

• Specify rules determine:

‒ type of shipments
‒ selection of deliveries
‒ creation of the shipments: grouping deliveries, data and
options etc.

• Determine sort order of the deliveries within the

shipments and consequently the itinerary (sort order
through leg determination)

• Within collective processing, you can also define a

transportation chain consisting of multiple shipments to
be created. For example, all selected deliveries are
grouped together into main leg, preliminary and
subsequent leg shipments.
Public 39
LE-TRA: Manual Shipment Creation with Planning Proposal

• The process is that first select the deliveries manually, then

choose the planning proposal, which engages the system
to automatically combine the selected deliveries in the
shipment and complete them with data.

• Unlike Collective Processing, you can change or edit the

created shipments manually before saving.

• The planning proposal arises from a planning profile saved

in Customizing.

• The profile variants is shared for planning profile and

collective processing, as the planning profile is regarded in
technical terms as a variant of Collective Processing for
creating shipments.

Public 40
basic Transportation Management: Create Capacity Document based on
Grouping criterias – with capacity limits

• The system first groups requirement document stages, such as freight unit stages, based on a
list of attributes (e.g. source location or carrier). The attributes are represented by grouping
rules and a set of grouping rules is bundled in a requirement grouping profile. You can define a
requirement grouping profile. A requirement grouping profile can be created for each capacity
document category.

• It is possible to create capacity documents based on requirements groups by

manual and automatic creation of freight order / freight bookings by either triggering this feature
out of Transportation Cockpit or by Background Processing.
• The user can define lower and upper capacity limits
Requirement groups above the upper limit are split
Requirement groups below the lower limit are not assigned to a capacity document, thus they
remain unplanned
• Dimensions of capacity limits e.g.:
Gross Weight, Gross Volume, Quantity

Public 41
Basic Transportation Management: Background Processing

Background processing: Create Capacity Document Based on Groups

Transaction: /SCMTMS/PLN_REQ_GRP

Public 42
Automatic Leg Determination according to the Itinerary
Leg Determination Category 1

LE-TRA basic Transportation Management

• The goods are sequentially picked up at the shipping
points and sequentially delivered to the ship-to parties.
‒ The itinerary is derived from the sort sequence of the
deliveries in the shipment document
‒ The sequence can be changed in a dialog box
‒ No intelligent route determination with geographic
optimization
Public
• Sequence of Freight order stages is “Defined and Linear”
‒ By default, stop sequence are automatically determined
according to the shortest route (via heuristic ABAP
program).
43
Automatic Leg Determination for preliminary and subsequent leg
Leg Determination Category 2 & 3

LE-TRA basic Transportation Management

• Non-linear stage FO cannot be created via planning

(manual and automatic)

• Leg determination 2 & 3: Preliminary leg per loading

point, subsequent leg per ship-to party.
• When there are several points of departure, a
preliminary leg is created for each point of departure,
which links the point of departure to the beginning of
the main leg.
• Similarly when there are several destination points
Public 44
Transportation Chain in a single shipment
Leg Determination Category 2, 3, 4
LE-TRA
• Leg determination categories 2,3,4 can form a
transportation chain to be illustrated in a single shipment.
• Limitation that the outputs (also the shipping units, texts,
dates, etc.) must be defined for the whole shipment.
• Recommend to use several shipments of the separate
legs to form a transportation chain.
Public
basic Transportation Management
Different objects of Freight Orders / Freight Bookings for
varied transportation mode, e.g. road, rail, air and ocean.
We have different modelling concept: need to create a set
of FOs / FBs to represent the transportation chain, that’s
how S/4 TM model the multi-modal transportation.
For automatic creation of a set of documents , please
refer to the feature ‘ Create capacity documents based
on grouping criteria’.
45
Create Transportation Stages manually

LE-TRA basic Transportation Management

• Entering stages manually in the shipment document • Freight Order stages can be maintained manually
‒ Leg ‒ Insert new stages
‒ Load transfer point ‒ Merge the existing stages
‒ Border crossing point ‒ Remove stages

Public 56
Assignment of DeIiveries to Stages

LE-TRA basic Transportation Management

• The deliveries in a shipment may only to be assigned • The assignment is automatically determined in the
to a few rather than all stages of the shipment stage details of the Freight Order.
‒ The system analyzes the point of departure and
destination for each delivery, one after the other.
‒ The system then looks for the legs that connect
these two locations.

Public 57
Scheduling

LE-TRA basic Transportation Management

• The system determines the LE-TRA Route • The Freight Unit contains the start location
for each order item (sales order / stock derived from plant and destination location
transport order).* derived form consignee

• The LE-TRA Route can be re-determined in
the outbound delivery. The shipment can
adopt the route from the delivery or a route
can be manually entered. *
• System can propose planned deadlines for
individual shipment activities. They are
copied from the outbound deliveries
belonging to the shipment via copy routine
*Note: LE-TRA route and corresponding objects are removed from compatibility
scope that allowed the customers to use existing functionalities outside of LE-
TRA transportation functionality.
Public
• The Freight Unit contains delivery date
• During scheduling, the system considers a set
of constraints, to adjust the departure and
arrival dates/times in the Freight Order and
determines the loading/unloading dates/times
for the related Freight Units
• ABAP scheduler can be used for Freight
Order scheduling in basic Transportation
Management(release version 2020 onwards)
58
Assigning Service Agents in the Shipment Document

LE-TRA basic Transportation Management

• Service Agents can be maintained in the shipment: • Carrier can only be maintained at the header level of
‒ At header level the Freight Order.
‒ At stage level • Different Executing Carriers can be maintained at the
stage level in rail Freight Order, but not possible in
other types of Freight Orders. It is not a gap due to
Public
different modelling concept in S/4 TM. 59
Tendering for Service Agents

LE-TRA basic Transportation Management

• A created shipment can be subcontracted and offered
to a service agent.
• Shippers and service agents communicate for the
shipments acceptance, rejection and further
information if necessary.
Public
• To use direct tendering process to send a road Freight
Order directly to a specific carrier without creating a
freight RFQ.
60
Automatic Assignment of the Service Agent
LE-TRA
• Route can be transferred from the deliveries to the
shipment (if it is the same for all deliveries). When the
status is set to “planned” in the shipment document,
the route and some other information, e.g. service
agent, are copied.
Public
basic Transportation Management
• Via the default route, the carrier can be determined to the Freight
Unit stage, and taken over to the Freight Order after Freight Units
assignment in the freight order.
• S/4 TM randomly chooses one if there are multiple applicable
default routes. Implicit enhancement can be done in the method
VSR_ROUTE_DEF_POST of class /SCMTMS/CL_SCH_PLN to
include decision parameters such as zones, shipping condition,
61
transportation group and weight.
Mass changes

LE-TRA basic Transportation Management

• Mass changes enables to change the data in several • Select multiple Freight Orders from the POWL and
shipment documents at once apply Mass Change
• Select the shipments required according to certain
criteria and make the changes at header level

Public 62
Packing in the Shipment Document

LE-TRA basic Transportation Management

• The packing hierarchy, which is setup in the delivery, is
continued in the shipment document.
• Delivery items packed into crates and loaded on pallets can be
packed into containers and loaded on trucks in the shipment
document.
• Cross delivery handling units is supported.
Public
• S/4 handling units can be integrated to create the packaging
information in S/4 TM (as package items).
• Further package items can be created in Freight Unit, Freight
Order.
• Cross delivery package items can be supported manually.
63
Delivery Item Generation in the Shipment

LE-TRA basic Transportation Management

• Packaging material are mostly cost items and are
managed as stock. For goods receipt from supplier
and goods issue to customers, it is important to
generate delivery items for the packaging materials
so that these can be seen in the delivery note,
posted in stock, and then invoiced as required.
• If an ASN is received with the packaging material, it
is possible to automatically create the packaging
material in the freight unit and in the corresponding
LE inbound delivery (when the customizing is
done).

• System can automatically generate separate

delivery items for packaging materials that are only
yet in planning for the shipment.
• Some information:
‒ Delivery items generated from packaging materials are not updated if
there is a change to the handling unit(plant, weight , and son on).
‒ Generated delivery items are deleted only if the handling unit is deleted
‒ The generation of packing materials in deliveries already posted for
goods issue is not possible.
‒ Any change in the HU content does not affect the generated item, even
if the new contents do not have any reference to this delivery.
‒ For technical reasons, the delivery update can only be called up during
the update of the shipment. Issuing a log is no longer possible at this
point.

Public 64
Maintaining Texts in the Shipment Document

LE-TRA basic Transportation Management

• Texts are maintained manually at header level in the • Texts are maintained on the Notes tab page in the
shipment document. Freight Order.

Public 65
Output Control

LE-TRA basic Transportation Management

• The Logistics Execution application uses output • S/4 TM uses output management to print, fax, email
control for printing and interfaces. documents and sending information via EDI.

Public 66
Dangerous Goods Check

LE-TRA basic Transportation Management

• The dangerous goods check applied is part of the • The system checks dangerous goods in different ways
standard dangerous goods management package in and at different process steps to ensure safety
the SAP System. precautions are observed.
• The check happens automatically or can be initialed • The system also prints the required dangerous goods
manually. information if required settings is made.
Public 67
Completing Transportation Planning

LE-TRA basic Transportation Management

• You can set the Planned status in the shipment header • The status ‘Ready for Transportation Execution’ can be
after completing all the necessary planning activities. manually set in the Freight Order.
• The shipment document is then ready for shipment • The system runs condition check of readiness for
completion. starting transportation execution.

Public 68
Shipment Execution
Activity Profiles
LE-TRA
• With the activity profile, when you set the
status of a shipment document, the system
executes activities and check for certain
data automatically.
• Possible activities include:
‒ Add to the data in the dialog box for completion
‒ Post goods issue for the deliveries
‒ Calculate the shipping costs
‒ Create invoices for the deliveries in the
shipment
‒ Print certain outputs
Public
basic Transportation Management
• Status ‘Ready for Execution’ can be
checked via condition.
• Goods movement (GI / GR) of deliveries
can be automatically triggered when a
customizable expected event is set in the
Freight Order.
• Automatic charge calculation can be
enabled when saving the Freight Order.
• Print documents via PPF output profile with
condition check.
70
Setting a Status

LE-TRA basic Transportation Management

• When transportation activities such as planning, • When transportation activities such as planning,
checking in, and loading are finished, you can set a departure/arrival, and loading/unloading are finished,
status you can set a status

Public 71
Tracking Events

LE-TRA basic Transportation Management

• Recording planned and actual deadlines for planning, • Events and actual event dates are executed manually
checking, loading, shipment start, shipment end at in the Freight Order Execution tab.
header level of shipment
• When Freight Order Execution Status is set, the
• Planned data taken from deliveries related event will also be derived automatically.
• Actual dates are executed manually or coming from
Eventhandler

Public 72
Posting Goods Issues for Shipments

LE-TRA basic Transportation Management

• The system can automatically selects all the deliveries • Trigger goods movement (GI / GR) of deliveries when
belong to the shipment and then posts goods issue for expected event is set in the Freight Order.
them.

Public 73
Monitoring Shipments
Shipment Information in List Form

LE-TRA basic Transportation Management

• Different list types for shipment processing: • Query, filtering and personalizing the Freight Orders
‒ Transportation planning list Worklist
‒ Utilization list
• Tendering Worklist
‒ Free capacity list
‒ Tendering status list • Freight Orders can be queried via administration data of
‒ Check-in list ‘Changed By’ and ‘Changed On’.
‒ Shipment completion list
‒ Change list
Public 75
Graphical Shipment Information
LE-TRA
• The information of the itinerary or the transportation
network for the shipment can be displayed graphically
or in the list form.
• Further details can be shown for selected objects.
• This information can be called up from within the
order, the delivery or the shipment.
Public
basic Transportation Management
• Predecessor and successor documents are displayed in
the tab ‘Transportation Dependencies’ of the Freight Order.
• The list of stops for a Freight Order is displayed in the tab
‘Overview’.
• ‘Cross-Document Time Conflicts’ can be checked in the
Freight Order.
76
Transport Execution Monitor

LE-TRA basic Transportation Management

• To monitor the processing status of shipment • Personalization settings in the Freight Orders Worklist
documents for a specified time span.
• To provides an overview of how much potential work is
required based on the number of shipment documents.

Public 77
Shipment Tendering Status Monitor

LE-TRA basic Transportation Management

• To monitor the tendering status of shipment • Personalization settings in the Tendering Worklist
documents for one or more transportation planning
points.

Public 78
Transportation Information System (TIS)

LE-TRA basic Transportation Management

• Various analysis and statistics on shipments

‒ General shipment characteristics
‒ Shipment routes • Personalization settings in the Freight Orders Worklist
‒ Means of transport
‒ Transportation shipping data
‒ Stages of shipment
‒ Transportation Material
Public 79
Displaying Transportation Change Documents

LE-TRA basic Transportation Management

• If an existing shipment is changed, a change • All changes made to a Freight Order can be viewed on
document is created when those changes are save. the tab page “Change Documents”

Public 80
Shipment Cost Processing
Shipment Cost Document
LE-TRA
• Shipment Cost Document
‒ Create individually from front end
‒ Collective processing online
‒ Collective processing in Background
Public
basic Transportation Management
• Freight Settlement Document
‒ Create individually from Freight Order
‒ Create from Freight Order worklist (multi-selection)
‒ Create Freight Settlement documents via background
processing
82
Shipment Cost Type and Item Category

LE-TRA basic Transportation Management

• Shipment Cost Type • Freight Settlement Document Type

‒ Number ranges ‒ Number ranges
‒ Status requirements of the shipment document ‒ Multiple FSDs can be created for one FO to
for creating a shipment cost document split the charges.

• Shipment cost items • Charge calculation level

‒ Refer to shipment header ‒ Calculation at header level
‒ Refer to shipment stage ‒ Calculation at stage level

Public 83
Shipment Cost Calculation

LE-TRA basic Transportation Management

• Pricing procedure determination • Freight Agreement determination

• Pricing procedure • Calculation Sheet (TCCS)

• Condition type • Charge Type

• Condition tables and condition records • Rate table

• Scale • Scale

• Calculation base • Calculation base & resolution base

• Multidimensional shipment rates (max. 3 scales) • Rate table with up to 3 scales

Public 84
Consistency Check for Freight Costs

LE-TRA basic Transportation Management

• Check certain settings in the price determination • Consistency check during charge master data
control for consistency. A warning message will maintenance.
be issued if an inconsistency found:
• Consistency check and veto for freight agreement
‒ Check for all condition types: Do the access
release.
sequences and calculation base match?
(Condition tables stored in the access
sequence must not contain any fields that are
not known for the calculation based used.)
‒ Check for all pricing procedures: Is at least one
condition type entered whose calculation base
is not ‘’? (Otherwise, no shipment costs
subitems can be created.)

Public 85
Additional Functions in Shipment Cost Calculation (1)

LE-TRA basic Transportation Management

• Shipment Comparisons • Line item selection of “Compare High/Low Value”

• Break Weight • Break-Weight calculation method

• Representing Geographical Aspects • Different calculation bases

‒ Distances ‒ Actual Distance, Aerial Distance
‒ Location and Zones (address data & tariff ‒ Source/Destination Location, City, Region,
zone) Country, Postal Code, Transportation Zone, etc.

• Pricing date & Settlement Dates • Calculation date & Settlement date

• Tax Countries • S/4 TM enables tax code determination and

calculation in S/4 ERP via condition types for tax

Public 86
Additional Functions in Shipment Cost Calculation (2)

LE-TRA basic Transportation Management

• Bulky Goods and Minimum Weights for shipping • Calculation rule with volume and minimum value,
units or with condition

• Bulkiness Factor • Dimensional weight profile and chargeable weight

• Freight Codes and Freight Classes • Product freight group; Commodity code

Public 87
Freight Cost Estimate

LE-TRA basic Transportation Management

• The transportation planner can execute a freight cost • Charges are calculated in the Freight Order and
estimate during shipment processing. displayed on the tab ‘Charges’

Public 88
Shipment Cost Document List: Calculation and Settlement

LE-TRA basic Transportation Management

• Calculation list: shipment cost documents which have • Freight Settlement worklist
not yet been completely calculated or if you still have
questions regarding calculation.
• Settlement list: shipment cost documents which have
note yet been completely transferred.
Public 89
Scales List

LE-TRA basic Transportation Management

• Gain an overview of which scales already exist for • Scales worklist

master data, in case these are needed.

Public 90
Shipment Cost Settlement with Service Agent (1)

LE-TRA basic Transportation Management

• Account Assignment • Freight settlement integration with standard SAP

‒ G/L account determination in Financial
Accounting
‒ Assignment for Cost Accounting
S/4HANA Financial Accounting via objects mapping:
‒ Assign freight settlement document information to
purchasing information in MM, in order to create
purchase order in purchasing
‒ Assign charge type information to a service master
record and an account assignment category used
for posting in Financial Accounting

• Mapping for Cost Distribution:

‒ Activate freight cost distribution to the order/delivery
item
‒ Assign charge types to condition types
‒ Posting to SAP S/4HANA ERP using Settlement
Management (earlier version Agency Business
Document)

Public 91
Shipment Cost Settlement with Service Agent (2)

LE-TRA basic Transportation Management

• Transfer to Financial Accounting • Posting freight settlement document to S/4 ERP,

‒ Purchase order determination freight settlement document is with status
‘Accruals Posted’ after S/4 ERP successfully
‒ Creation of the service entry sheet
created the PO and SES.
‒ Accrual establishment
• Standard invoice creation in S/4 ERP
‒ Self-billing (ERS procedure)
• Invoice creation
‒ Manual Invoice verification
‒ Credit memo procedure (ERS procedure)
‒ Manual Invoice verification

Public 92
Shipment Cost as delivery cost
LE-TRA
• Delivery costs can be considered for both
standard purchase orders and stock transfer
orders.
• The determined shipment costs are not directly
transferred to the accounting department, but are
included in the MM goods receipt document and
added to the respective material.
Public
basic Transportation Management
• Perform cost distribution at the level of ERP item in
the freight settlement document.
• In case of inbound transportation, use S/4 ERP
customizing settings to specify the type of posting
as material valuation for the distributed cost.
• The distributed freight cost will flow back to your
material level for the purpose of material valuation.
93
Transferring Shipment Costs to Accounting

LE-TRA basic Transportation Management

• Select the Transfer indicator and save the shipment • Posting to S/4 ERP from freight settlement document.
cost document. • Posting from freight settlement worklist.
• Transfer freight settlement documents via background
processing.

Public 94
Billing Shipment Costs to the Customer
LE-TRA
• To bill the customer for the actual shipment costs
based on effective shipment cost calculation. The
freight costs appear as additional entry in the
customer billing document.
• Shipment costs that are calculated from the
delivery items in the shipment cost document are
assigned directly to their corresponding billing
document items. Costs that are based on other
factors, for example, the shipment cost items,
are distributed among the billing document items
according to the proportional weight of the
delivery items.
Public
basic Transportation Management
• Create the Freight Settlement document out of the
Freight Order with active cost distribution to the
delivery items.
• If the SD billing process is enabled for the delivery
items, the system takes the distributed cost from
S/4 TM into account when it creates the billing
document for the deliveries in SD.
• Transportation costs are now part of the billing
document and can be invoiced to the customer.
95
Shipment Costs in the Sales Process

LE-TRA basic Transportation Management

• To have a rough idea of the shipment costs when

the sales order is created, in order to give
customers relevant information or to compare
different transportation options.

• As in normal situations no deliveries, shipments

or shipment cost documents exist at this point,
simulated version of them can be “created” in the
background to enable to calculate shipment
costs based on these documents.

Public 96
Interfaces
1. External Transportation Planning Systems
2. Transportation Planning in Cooperation with Forwarding Agents
3. Shipping Notification
4. Using Express Delivery Companies
5. Communication via Internet
External Transportation Planning Systems
LE-TRA
• Interface from LE-TRA to TPS
‒ Transmission of location master data (IDoc
TPSLOC01 or TPSDLS01)
‒ Transfer of deliveries (IDoc TPSDLS01)
‒ Transfer of status values for planned shipments
(IDoc TPSSHT01)
• Interface from TPS to LE-TRA
‒ Transfer of planned shipments (IDoc TPSSHT01)
‒ An exchange of error status (IDoc SYSTAT01)
Public
basic Transportation Management
• Architecture decision not to support IDoc any longer.
• S/4 TM Web Service for the Freight Units and
Freight Orders
‒ Exchange Transportation Demand (Freight Unit
Out)
‒ Receive Consolidated Load (Freight Order In)
‒ The entire communication is based on the
technical web service
TransportationOrderGenericRequest_Out/_In.
• For the master data transmission, Web Service
planned for Internal ID / External ID mapping, and
Standard ID registration.
98
Transportation Planning in Cooperation with Forwarding Agents

LE-TRA basic Transportation Management

• Forwarding agent can principally work like an external • Architecture decision not to support IDoc any longer.
TPS. The shipper transfer the deliveries to the
forwarding agent; the forwarding agent groups these
deliveries in his own system and then transfer the • S/4 TM Web Service for the Freight Units and
planned shipments to the shipper’s system. Freight Orders
‒ Exchange Transportation Demand (Freight Unit
• Shipper sends deliveries to the forwarding agent: Out)
‒ Plan/change/deallocate deliveries (IDoc TPSDLS01)
‒ Receive Consolidated Load (Freight Order In)
‒ Add/change location master data (IDoc TPSLOC01)
‒ The communication is based on the web service
‒ Set transportation planning status (IDoc TPSSHT01)
TransportationOrderGenericRequest_Out/_In.
‒ Status information about errors (IDoc SYSTAT01)
• For the master data transmission, Web Service
• Forwarding agent transmits the planned/rejected
shipments and changes back to the shipper: planned for Internal ID / External ID mapping, and
Standard ID registration.
‒ Create/change/delete shipment (IDoc TPSSHT01)
‒ Status information about errors (IDoc SYSTAT01)

Public 101
Shipping Notification

LE-TRA basic Transportation Management

• Notification by the vendor to the recipient regarding • Architecture decision not to support IDoc any longer.
the pending arrival of goods shipped or about to be
shipped. It contains the anticipated delivery date, • Advanced Shipping Notification interface
quantities, and details of the material (or service).
• The communication is based on the web service
• A shipping notification can be sent in the form of an TransportationOrderGenericRequest_Out/_In.
EDI message.

Public 102
Using Express Delivery Companies Overview
LE-TRA
• Modelling the special requirements of express
deliveries using express delivery companies,
includes:
‒ Information specific to the service agent
recorded in the delivery, refers to the entire
delivery or to the individual parcels.
‒ Printing out special labels with the required
information.
‒ Creating the manifest / delivery list (EDI using
standard IDocs and day-end closing)
‒ Parcel and status tracking (access information
directly from the express delivery company via
the Internet)
Public
basic Transportation Management
• Enable the carrier to transport parcels from a
shipping point to several consignees.
‒ Create parcel shipments in SAP TM based on
deliveries from an ERP system.
‒ Select a direct shipment option for
the parcel shipment. (The direct shipment
option involves selecting a carrier with the
relevant transportation services while taking
into account the applicable charges.)
‒ Creating the manifest for each shipping
location, carrier and service product with the
parcels (Freight Units) assigned.
‒ Plan, execute and track the transportation of
shipments to the consignees.
103
Process of outbound delivery using Express Delivery in LE-TRA

 If an express delivery company is specified in the

outbound delivery, the system automatically loads the
information from the data stored for that company,
includes the tracking number, routing information, and
the service code and product codes.

 The shipper informs the ship-to party of the tracking

number and any other information relevant to the
express delivery.

 The shipper also has the option of creating a shipment

document containing all the deliveries for a particular
express company (manifest).

 Both the shipper and ship-to party can monitor the

tracking status at any time using the tracking number
and Parcel Tracking.

 The data for the express delivery companies are

maintained in the Express Delivery (XSI) Cockpit.

Public 104
 Parcel Process in basic Transportation Management
 When the outbound delivery is saved with Handling Units
(one Handling Unit representing one parcel), the basic
TM system automatically creates one Freight Unit
mapping to one Handling Unit (parcel).

 Meanwhile, the system will rank the carriers using Direct

Shipment Options process (the detailed steps for DSO
are in the slide notes). The carrier can be selected
automatically or manually according to the configuration.

 A new manifest is then created for each shipping

location, carrier and service product with the parcels
(Freight Units) assigned. Technically, the manifest is a
freight order with a special type. In the real business
world, it‘s a document recording the parcel handover to
the express companies.

 The Tracking Numbers are assigned to each shipment

and parcels in the manifest.

 From TM 9.1, output templates are delivered for labels

and a Parcel Manifest.

 For Parcel Freight Orders, the Shipment is used for

calculating charges, if in the profile the calculation level is
defined as ‚item‘.
Public 105
Communication via Internet

LE-TRA basic Transportation Management

• Tendering shipments for service agents
• Tracking information monitor
‒ A simple tracking for monitoring the shipment status
between the shipper and the forwarding agent
The following features will be available in basic
Transportation Managementif they’re used via Logistics
Business Network (subscription license) :
• Shipment Tendering - Direct Tendering

• Transportation planning by the forwarding agents • Carrier Response to spot bids via LBN Integration
through the Internet
‒ Shipper offers deliveries to the forwarding agent • Carrier Invoice submission and Dispute Management
through a Web interface via Integration with LBN
‒ Forwarding agent receives a list of deliveries
‒ Forwarding agent sets up shipments and transmit
• Integration to Global Track & trace
the planned shipments to shipper
• TM Supported Invoice Verification Transactions
‒ Shipper decides whether to accept the planned
shipments or to offer the deliveries to another
forwarding agent

Public 106
Miscellaneous
Multi-level goods receipt (IS-A-GR)
LE-TRA
• Goods receipt is usually based on the inbound
delivery or inbound shipment in the automotive
industry, when the goods are not procured using
the JIT process.
• The first step in the multi-level goods receipt
goods receipt process is to compare the shipping
documents with the data received by EDI and
make any corrections or additions. The second
step involves the comparison of the packages
and quantities received with the delivery notes,
making any corrections, and then posting goods
receipt.
Public
basic Transportation Management
• In Advanced Shipping and Receiving (delivery
based FU only), you post goods movement at the
warehouse unloading stop level in freight order.
The system triggers goods receipt by the
warehouse. After the warehouse has successfully
processed the request, the system updates
the goods movement status in freight order
to Completely Processed. If the posting
of goods movement by the warehouse is not
successful, the system displays
the goods movement processing
status Posting/Cancellation Failed.
108
LE-TRA integration with EWM

LE-TRA basic Transportation Management

• LE-TRA can be integrated with SAP EWM: • Currently under investigation:

‒ IDoc communication between SAP ERP and It is planned to get an exception for EWM for the
EWM, sending and receiving SHPMNT05 and usage of SHPMNT05 for that specific IDOC
TPSSHT01 communication.
‒ Mapping between ERP shipment number and ECC System SAP S/4HANA EWM embedded

EWM external TU or vehicle number LE-TRA

Shipment
object
LE-TRA SHPMNT SHPMNT EWM-
Shipment IDOC IDOC Transportation
object Outbound Unit
Inbound
SHPMNT SHPMNT
IDOC EWM-
IDOC Transportation
Inbound Outbound Unit

NO LE-TRA Customizing
needed EWM has an own
customizing for this
integration

Public 109
System Modifications and Business Add-Ins

LE-TRA basic Transportation Management

• Business Add-Ins in Transportation: • There are around 219 BADIs in different areas of
‒ BADI for saving shipments S/4 TM version 1909:
‒ BADI for checks when creating a shipment cost ‒ Master Data
document ‒ Basic Functions
‒ BADI for creating a shipment cost document ‒ Freight Order Management
‒ BADI for shipment cost account assignment ‒ Planning
‒ BADI for checks during shipment cost ‒ Settlement
processing ‒ Integration
‒ BADI for transferring shipment cost items
‒ BADI for saving shipment cost documents
‒ BADI for the purchase order item determination

Public 110
Transition to SAP S/4HANA TM
Transition Assessment for SAP Transportation Management in S/4HANA

This transition assessment service determines the migration feasibility from SAP Logistics Execution Transportation (LE-TRA) to
Transportation Management in S/4HANA (S/4HOP1709 onwards).

Business needs Related Services

 Customers want to move to the next generation digital platform  SAP Model Company for Logistics Execution
 Customers want more transportation management capabilities (50137744)
 Customers want to move fast and against low cost

Delivery approach and scope

 The service will be delivered in line with the Activate methodology
 The service will include a code review of the current LE-TRA solution
 The service will draft the possible target architectures Internal Information
 The service will indicate the several migration options and migration recommendations  Service No.: 50144207
 The service will define the transition strategy  Contact: Pieter Rodenburg / Dré de Jong
 The service will give recommendation on transition
 Duration: Between 5 and 35 working days
depending on scope options
Value and benefits  Service Price: Market Unit adds if required
 Quick analysis on how to migration to next generation digital platform
 Migration building blocks defined as outcome to migrate faster to next generation digital platform
 Rough order of magnitude estimation and timelines for the real migration

Public 112
Transition Execution From LE-TRA TO S/4HANA TM
The transition execution service support migration from SAP Logistics Execution Transportation (LE-TRA) to S/4HANA TM – Basic Shipping

Business needs Related Services

 Customers need to migrate data to from LE-TRA to S/4HANA TM embedded  Transition Assessment For SAP Transportation
 Customers want fast and smooth transfer of data Management in S/4HANA (50144207) – Mandatory
 Customers want to have best practice content for a rapid set up of the new system pre-requisite to start Transition Execution service
 SAP Model Company for Logistics Execution
Delivery approach and scope (50137744)
 The service will transition SAP LE-TRA solution to SAP S/4HANA TM Basic Shipping solution  SCM Transportation Management Services (Generic)
 The service will apply the best practice content for the major scenarios in TM (50125498)
 The service will define relevant master data
 The service will provide guidance on master and transactional data compatibility in LE-TRA and Internal Information
S/4HANA TM  Service No.: 50146465
 This service will perform necessary customizing to setup SAP S/4HANA TM for customer specific  Contact: Pieter Rodenburg / Dré de Jong
requirements
 Duration: XXXX
 The service will execute the migration of data from LE-TRA to S/4HANA TM in Development, Quality
and Production System  Service Price: Market Unit adds if required
 The service will make main business processes run in S/4HANA TM

Value and Benefits Scope Options

 Lean and fast transition from existing LE-TRA solution to S/4HANA TM embedded solution  Scope option 01: Foundation (Mandatory)
 For more complex S/4HANA TM embedded implementations it may be used as a jumpstart for a  Scope option 02: Logistics Outbound (Optional)
project  Scope option 03: Logistics Inbound (Optional)
 Provides implementation of SAP best practices  Scope option 04: Charge Management, Invoicing, Cost
 Access to SAP experts who will provide guidance on functionality mapping and future direction Distribution (Optional)
 Scope option 05: TM Developments (WRICEF)
Public 113
Logistic Execution – Transportation Management

Master Data Shipping Point Route with defined

Stages

Transportation Deliveries
Multi Model
Requirment Transportation

Transportation Reports for

Leg and Stage Shipment
Transportation Shipment Creation External Planning
Planning Determination Stages
Planning

Shipment Reports Shipment Manual Status

Activity Profiles
Execution Completion Management

Information Transportation
Monitoring Systems Change
Shipments In Transportation Documents

Shipment Cost
Shipment Cost Shipment Cost Cost Settlement Billing Shipment Cost
Cost Distribution Simulation in Sales
Processing Document With Service Agent to Customer
Order

External Transportation Express Delivery

Communication via
Interfaces EDI Output Transportation Planning with Company
Internet
Planning Systems Forwarding Agents Requirements

Public 114
Basic Transportation Management
Master Data Location Default Route / Equipment Type /
Transportation Zone Transportation Lanes
Stages Group

Contract Freight Agreements

Basic Charge
Management Agreements

Triggering: Delivery
Freight Document Delivery Based Freight Orders / Determination of
Freight Units note, Goods Issue,
Management Freight Booking Stages
Customer Invoice

Freight planning Manual carrier

Manual Planning Basic Transportation Multi Modal Capacity Doc.
Active Vehicle selection / External Planning
and optimisation Cockpit Transportation Based on criterias
assignment

Transportation
Freight execution Basic Dangerous
Subcontracting Award Confirmation execution internal Status Management
and monitoring events / monitoring
goods management

Freight Settlement Freight settlement & Carrier Invoice Freight Cost

Freight settlement Document creation Charge calculation Verification Distribution

Communication via
Integration / Interface for External
defined TM web
Interfaces Planning
service

Reporting Via BI Reports

Public 115
Advanced Transportation Management
Master Data Schedules Allocations /
Trade Lanes Resources
Business Shares

Contract Strategic Freight Forwarding Service Product

Management Management Management Catalog

Combined Inbound /
Freight Document Order based Freight
Co2 Emissions
Units Outbound / Stock
Management Transfer

Interactive Planning
Freight planning Load Planning / Load Transportation
(Transportation VSR Optimizer Carrier Selection Driver Management
and optimisation Cockpit) Consolidation Proposal

Freight execution External Event Service Order

Advanced Tendering
and monitoring Management Management

Freight Settlement &

Automatic Change Forwarding
Freight settlement Advanced Charge
Management Settlement
Group Logistics Internal Settlement
Calculation

Enterprise Asset Extended Integration into

Integration / Descartes
Global Trade Service Management Event Management Warehouse Global Track & Trace Business Network for
Interfaces Integration
Integration Management Logistics

Embedded Analytics
Reporting (via CDS)
Public 116
Business value of S/4HANA TM compared to LE-TRA
S/4HANA Supply Chain for Transportation Management – Value
Reduced Freight spend and
improved service levels
E2E transportation visibility
and quicker data insights
Public
 Cut down manual processes in planning
(fully automated planning, carrier selection, tendering), freight capacity
procurement, freight status monitoring and freight invoice verification
 Optimized transportation planning ensuring cost and resource optimization
meeting service levels and all transportation constraints – including load plan,
freight consolidation and package building
 Optimized carrier selection ensures optimized carrier capacity utilization and
lower costs
 Optimal freight cost negotiation and freight contracts with simulation and what-
if analysis
 Reduction of expedites and overheads through real-time transportation status
monitoring
 Real-time shipment and order status visibility through integrated freight
execution tracking and event reporting, map-based tracking
 Freight cost and order visibility through extensive real-time analytics
118
S/4HANA Supply Chain for Transportation Management – Value

 Through real-time status visibility and alerting

Better respond to changes  Dynamic re-planning capabilities
 Realtime integration with warehouse enabling faster processing of orders

Improved Usability and Lower  Improved user experience, administration, and advanced planning tools
TCO (using map based planning, Gantt chart, load planning)

Public 119
Thank you.
Contact information:

© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material.