Travel Distance Calculation
Travel Distance Calculation
Public
Warning
This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.
This is custom documentation. For more information, please visit SAP Help Portal. 1
4/3/25, 7:44 PM
Stock Migration
Use
The result of the travel distance calculation is used for:
Planning the workers, if you have activated Labor Management (LM). For more information, see Operational Planning.
Calculating engineered labor standards (ELS), if you have activated LM. For more information, see Determination of Normal
Time Using Engineered Labor Standards.
In addition to calculating the travel distance, the system determines the travel time required by a worker to execute the warehouse
order. The system calculates the time required based on the speed of the resource used, among other factors. For more
information, see Travel Time Calculation.
Prerequisites
You have activated the travel distance calculation for your warehouse number in Customizing for Extended Warehouse
Management under Master Data Define Warehouse Number Control .
When calculating the distance during warehouse order creation, the system uses the following values:
This is custom documentation. For more information, please visit SAP Help Portal. 2
4/3/25, 7:44 PM
For the speed, the system uses the speed of the slowest resource (pessimistic approach). This is relevant for the travel time
calculation.
For the distance to be covered in order to reach the first item of a storage type, the system uses the default distance which
you have specified in Customizing for Extended Warehouse Management. This is because the system does not know which
resource will execute the warehouse order, and therefore its position is also unknown.
If a travel network is available, the system uses all defined routes in the network without resource-type restrictions.
The system can only access more detailed information when the warehouse order is confirmed, as only then is the executing
resource known. The following information is then available:
The system saves the result of the travel distance calculation in the planned workload. If you have activated Labor Management,
the system also saves the result of the travel distance calculation in the executed workload. For more information, see Labor
Management (LM).
Types of Distance
Direct distance
The system can calculate the travel distance using the direct distance, based either on the Euclidean or Manhattan metric.
The figure below shows the direct distance between two storage bins of a storage type. The solid line represents the
Euclidean metric; the dotted line represents the Manhattan metric.
The system can calculate the travel distance based on an existing valid network. For more information about networks, see
Networks.
This is custom documentation. For more information, please visit SAP Help Portal. 3
4/3/25, 7:44 PM
The figure below shows the distance between two storage bins of a storage type. The resource moves across the valid
routes.
Networks
Networks define the valid routes (streets) in the warehouse, on which the resources move.
Types of Network
A network consists of edges and nodes. Edges are connected to each other by way of nodes. Edges represent the valid routes in the
warehouse, and nodes represent crossings.
The figure below shows a warehouse consisting of different storage types. Each storage type is displayed in a different color.
Storage-type-specific networks are defined (with green, blue and gold edges), which are connected to each other by a global
network (red edges).
This is custom documentation. For more information, please visit SAP Help Portal. 4
4/3/25, 7:44 PM
Please note that image maps are not interactive in PDF outputs.
These networks consist of edges corresponding to the aisles of a storage type, and edges that connect these aisles to each
other. In the example above, these are the green, blue and gold edges.
An edge, if they are located in an aisle, and an edge exists for the aisle.
A node that matches your X and Y coordinates, or lies close to them in terms of the chosen metric (Euclidean or
Manhattan metric), if you have not assigned an edge.
Global network
The global network connects the defined, storage-type-specific networks to each other. If no storage-type-specific
networks are defined, it connects the storage bins to each other directly. In the example above, these are the red edges.
An edge is usually passable in both directions, however it can also be defined as a one-way street. The direction is defined
through the start and end nodes.
For each edge, you can define which resource types are allowed to pass.
An edge has a length that is used by the system to calculate the travel distance, if a resource passes along the edge.
This is custom documentation. For more information, please visit SAP Help Portal. 5
4/3/25, 7:44 PM
A network is valid if every node can be reached from every other node. The system calculates the validity for each resource type.
The global network is valid if every node of a valid storage-type-specific network can be reached from every other node of a valid
storage-type-specific network. The travel distance calculation only uses valid networks. The system ignores edges in invalid
networks.
You can create both global and storage-type-specific networks in the settings for the travel distance calculation. For more
information, see Settings for the Travel Distance Calculation.
You can generate storage-type-specific networks using the Generate Edges - Travel Distance Calculation app. For more
information, see Generate Storage-Type-Specific Networks.
You can upload CSV files containing your network data. For more information, see Upload Travel Distance Network.
On the launchpad, choose Extended Warehouse Management Settings Travel Distance Calculation Evaluate Travel
Distance Network .
3. If you want travel time information to be included in the message log, you can additionally specify the executing resource
and whether or not it is unloaded.
Features
On the launchpad, choose Extended Warehouse Management Settings Travel Distance Calculation Configure TDC -
Travel Distance Calculation.
This is custom documentation. For more information, please visit SAP Help Portal. 6
4/3/25, 7:44 PM
Define edge direction (unidirectional, bidirectional)
Context
You can define networks:
Edges are only created for aisles that have more than one storage bin.
The length of the edges corresponds to the Euclidean distance between the start and end nodes.
If storage bins are located on both sides of the aisle, the edges are located in the center of the aisle.
If there are only storage bins on one side of the aisle, the edges lie half a bin depth away from the aisle.
The edges start and end outside the aisle (half a bin depth).
The system generates connecting edges between neighboring aisles by connecting both the start and end nodes of two
neighboring aisles with an edge.
Procedure
This is custom documentation. For more information, please visit SAP Help Portal. 7
4/3/25, 7:44 PM
1. On the launchpad, choose Extended Warehouse Management Settings Travel Distance Calculation Generate
Edges - Travel Distance Calculation.
Warehouse number
Storage type
Indicate whether you want to generate edges for aisles only, or for an entire network
Aisle attribute for grouping storage bins and allocating edges. The system generates an edge for each aisle.
The X and Y coordinates of the storage bins (these define the bottom left corner of a storage bin) are there to
position the start and end nodes of the edges.
The system uses the breadth and depth of the storage bin type to define the center of the aisle and the distance
between the edge and the aisle.
Procedure
1. On the launchpad, choose Extended Warehouse Management Settings Travel Distance Calculation Upload Travel
Distance Network .
2. Select the warehouse number for which you want to maintain the travel distance network. Specify whether you want to
change the storage type-specific networks and/or the global network.
3. In the section Upload Object, select whether you want to upload edges or excluded resource types.
4. Choose your upload settings, for example, whether you want to replace the existing data for the networks selected in step 1
with the uploaded data or only add new edges.
Your CSV file for edges should have the following format:
For global edges, leave the storage type field empty. You specify the edge ID yourself and it has to be unique on warehouse
level.
Your CSV file for excluded resource types per edge should have the following format:
This is custom documentation. For more information, please visit SAP Help Portal. 8
4/3/25, 7:44 PM
7. Start the data transfer.
The resource visits each storage bin in the sequence defined by the list.
The resource executes the horizontal movement first, meaning the resource first moves to the storage bin in a horizontal
direction.
The resource then executes the vertical movement, namely the movement from the floor to the bin and back.
The resource then moves to the next storage bin in a horizontal direction.
The total travel distance in a vertical direction therefore corresponds to twice the Z distance of the storage bins to the floor (point
of origin Z = 0).
For the horizontal movements, three types of distance influence the calculation: the direct distance, the distance between a bin
and a node, and movements within a network.
For movements between storage bins within a storage type, if no valid storage-type-specific network exists.
For movements between storage bins from different storage types, if no global valid network exists.
For movements within an aisle. Here, the system uses the direct distance between storage bins to calculate the travel
distance.
This figure shows examples for travel distances between multiple storage bins within an aisle. The green line represents the
Euclidean metric; the dotted blue line represents the Manhattan metric.
This is custom documentation. For more information, please visit SAP Help Portal. 9
4/3/25, 7:44 PM
Storage bins are connected to the network using either of the following:
Using the nearest node, if no edge has been assigned to the storage bin. The node comes from the storage-type-specific
network, or if this does not exist, the global network.
Calculating the travel distance using the nearest node, if no edge is assigned to the storage bins
Using the nodes of an edge, if the storage bin is in an aisle, and an edge exists for the aisle.
This is custom documentation. For more information, please visit SAP Help Portal. 10
4/3/25, 7:44 PM
Calculating the travel distance using the nodes of an edge, if one storage bin is in an aisle and an edge exists for the aisle, and then
moving to the nearest node, if no edge has been assigned to the second storage bin
Fundamentally, there are four options. However, for a one-way route, only one option is allowed: entering the edge at the
start node and leaving it at the end node.
This figure displays how a bin sequence within an aisle can be connected with the node or nodes of the respective edge. As
stated in the section above, the edge itself is not used for the calculation within an aisle, because the direct distance is used
between storage bins.
This is custom documentation. For more information, please visit SAP Help Portal. 11
4/3/25, 7:44 PM
Lie in the same storage type but not in the same aisle, and a valid storage-type-specific network exists.
When calculating movements within the valid global network and any valid storage-type-specific networks, the system:
1. Connects the storage bins with the nodes of the respective edge or with the nearest node.
2. Adds the travel distance between the assigned nodes. If a bin is assigned to the nodes of an edge, there are several possible
options for calculating the network distance.
Example: Both bins are assigned to different edges, which are not one-way routes. There are four options:
From the start node of the first edge to the start node of the second edge
From the start node of the first edge to the end node of the second edge
From the end node of the first edge to the start node of the second edge
From the end node of the first edge to the end node of the second edge
This figure shows the different connections between edges (black lines), edge and node (black dots), and possible connections
between the assigned nodes (green lines). The system uses the option with the shortest travel distance.
The warehouse manager wants to calculate the travel distance from storage bin 1 to storage bin 3 within a storage type with a valid
network (green edges). 1, 2, and 3 are storage bins at which warehouse worker X withdraws goods.
This is custom documentation. For more information, please visit SAP Help Portal. 12
4/3/25, 7:44 PM
The travel distance comprises the following:
Direct distances A (within an aisle), B and D (connection between storage bin and network)
Of the four possible calculations, the system uses the first option, as that represents the shortest travel distance.
This is custom documentation. For more information, please visit SAP Help Portal. 13
4/3/25, 7:44 PM
Option three for calculating travel distance from 1 - 3
Example 2: Travel Distance Calculation Between Two Storage Types with Valid
Networks
This example shows a travel distance calculation between two storage types that each have a valid, storage-type-specific network
(green and blue edges) and a valid, global network (red edges).
This is custom documentation. For more information, please visit SAP Help Portal. 14
4/3/25, 7:44 PM
The travel distance comprises the direct distances A and C (connection between storage bin and network) and distance B within
the entire network (local and global).
Example 3: Travel Distance Calculation Between Two Storage Types with a Global
Valid Network
This example shows the travel distance calculation between two storage types with a valid global network (red edges). Only one
storage type (green) has a valid network (green edges).
This is custom documentation. For more information, please visit SAP Help Portal. 15
4/3/25, 7:44 PM
The travel distance comprises the direct distances A and C (connection between storage bin and network) and distance within
network B.
Two heuristics for the travel distance calculation within a network exist. The system calls both by default. You can control the
heuristics using the Business Add-Ins (BAdIs) for the travel distance calculation.
Depth-first search
The system attempts to find a route between the specified nodes of a network in the shortest time possible. Here, the
search runs in the direction of start node to end node. The search finishes when the first complete route is found.
Breadth-first search
The system looks for all possible routes in the network, and selects the one that has the shortest distance. This heuristic is
more performance intensive at runtime, and is only appropriate for small networks.
Stopping criterion
The stopping criterion quickens the breadth-first search. This may have a negative impact on the solution quality, and the
system may fail to find the shortest route. The parameter restricts the number of nodes that can be visited by a route, in
relation to the route found by the depth-first search.
By default, the total travel time is calculated as follows. You can find the result in the message log in Evaluate Travel Distance
Network and in the planned workload. If you have activated Labor Management, you can also find it in the executed workload.
The horizontal travel time and vertical travel time are calculated as follows:
Horizontal travel time = Total horizontal travel distance / Horizontal resource type speed
Vertical travel time = Total vertical travel distance / Vertical resource type speed
If you want to use a more complex travel time calculation, you can maintain your own set of calculation rules in BRFplus. For more
information, see Configuring the Travel Distance Calculation and Travel Time Using BRFplus.
EWM provides a standard BRFplus application /SCWM/TDC_SYS and function /SCWM/TDC_CALC_TIME to which you can assign
your own rulesets. The interface of the standard function includes the following:
This is custom documentation. For more information, please visit SAP Help Portal. 16
4/3/25, 7:44 PM
Consolidated section information of horizontal movements
When you define your own rules, you can use any or all of the above information as input.
In contrast to the total travel distance, consolidated section information lets you consider each section of the calculated travel
path separately. For example, you might want to consider turns and stops in the travel path, because they limit the maximum
speed of a resource. The shorter a straight segment is, the less likely it is for the resource to travel at its maximum speed.
Technically, a travel path is defined as a list of points. These points can either be nodes (N) of edges or bins (B). A pair of
consecutive points defines a section of the travel path. Two consecutive sections define a turn angle for the resource. Sometimes,
the turn angle is zero, which indicates that both involved sections can be consolidated into one straight section. However, if the
shared point of both sections is a bin - where the resource needs to stop - the sections cannot be consolidated, even if the turn
angle is zero.
The above figure demonstrates how sections are consolidated. Sections S1 and S2 cannot be consolidated as there is a turn in
between. Sections S2 and S3 cannot be consolidated as there is a bin in between. However, the two sections following S4 can be
consolidated into S5.
Example 1
This is custom documentation. For more information, please visit SAP Help Portal. 17
4/3/25, 7:44 PM
We use the following information from the function interface:
Horizontal travel time = Total horizontal travel distance / Horizontal resource type speed
Vertical travel time = Total vertical travel distance / Vertical resource type speed
The horizontal travel distance is 5 metres. The horizontal resource type speed is 5m/s. The vertical travel distance is 1 metre. The
vertical resource type speed is 0.5m/s. The total travel time is therefore 3 seconds:
5/5 + 1/0.5 = 3
Example 2
We use the following information from the function interface:
S1 2m ...
S2 4m ...
S3 6m ...
S1 1m ...
S2 1m ...
S3 0.5m ...
S4 0.5m ...
We can then define a loop expression in BRFplus over the consolidated horizontal sections and define the following formula to be
used in every iteration:
This is custom documentation. For more information, please visit SAP Help Portal. 18
4/3/25, 7:44 PM
Total horizontal travel time = Total horizontal travel time + (Current section in iteration / Horizontal resource type speed) + 2s
In this simplified model, we add 2 seconds to the time needed for each section, to account for turns.
For the total vertical travel time, we can define a loop expression over the consolidated vertical sections and use a similar formula
in every iteration:
Total vertical travel time = Total vertical travel time + (Current section in iteration / Vertical resource type speed) + 1s
Assuming a horizontal resource type speed of 2m/s and a vertical resource type speed of 0.5m/s, we arrive at a total travel time of
22 seconds.
Available BAdIs
BAdI: Change Storage Bin List for Travel Distance Calculation /SCWM/EX_TDC_BIN_LIST
Influence the default distance to the first storage bin in the storage bin list.
The system calls this BAdI to calculate the travel distance of a warehouse order. If you implement this BAdI, you can define
your own logic for calculating the travel distance along the sorted storage bin list transmitted to the BAdI.
You can implement this BAdI to define your own logic for the travel time calculation or to determine how travel time is
calculated. For more information, see Configuring the Travel Distance Calculation and Travel Time Using BRFplus.
For more information about these BadIs, see Customizing for Extended Warehouse Management, under Business-Add-Ins
(BAdIs) for Extended Warehouse Management Cross-Process Settings Travel Distance Calculation .
This is custom documentation. For more information, please visit SAP Help Portal. 19