SAP TM Master Data Parts and 2

1
SAP TM Master Data – Part 1
Locations, Products, Resources, and
Means of Transport
SAP TM Master Data – Part 2
Transportation Lanes & Transportation Zones
2
SAP TM Master Data – Part 1
Locations, Products, Resources, and
Means of Transport
3
©SAP 2009 / Page 3
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role & Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
4
©SAP 2009 / Page 4
SAP TM Mast er Dat a –
Over vi ew
Existing master data elements from the SAP SCM system are re-
used in SAP TM
SAP TM wraps master data into business objects in order to allow
distinct and well-defined access to these elements
Geography is based on the following main elements:
Locations
Transshipment locations
Incoterm locations
Transportation lanes
Transportation zones
Other master data:
Products
Capacities, such as resources, schedules (e.g. sailing schedules),
drivers
Organizations and business partners (separate chapter)
Master data is needed to prepare the system for the
operational aspects of conducting business. In most
cases, master data will not be created by the end user.
During operations, power users might add new master
data like products and locations according to a pre-
defined process.
5
©SAP 2009 / Page 5
SAP TM Mast er Dat a –
Over vi ew – ‘Lean’ Mast er Dat a
ERP customers have the option of
automatically creating a variety of master
data elements via the Core Interface (CIF);
examples include locations, business
partners, or products (material masters)
Logistics service providers in particular may
not have an ERP system or might not use
SAP ERP for logistics purposes. In this case,
SAP TM provides the option of either
creating certain master data elements in
SAP TM itself, or working with basic
standard code lists.
Lean master data elements
Products – freight classification codes
Locations – standardized identification
schemes for locations
Lean master data concept
6
©SAP 2009 / Page 6
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role Codes and Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
7
©SAP 2009 / Page 7
SAP TM Mast er Dat a –
Loc at i ons
Different Customizing entries and master data elements from SAP ERP are reflected in SAP
TM as locations with different types
SAP ERP master data can be transferred to SAP TM via the Core Interface (CIF)
ERP Master Data
Plant
Customer
Vendor
Shipping point
TM Master Data
Location
Location
Location
Location
Transportation zone
If a plant, customer or vendor is transferred and a transportation zone in maintained for
this object then during the transfer to the SCM system:
The plant, customer or supplier location is created
The plant, customer or supplier location is assigned to the transportation zone in the
SAP TM relevant hierarchy.
For details please check the CIF integration training.
8
©SAP 2009 / Page 8
SAP TM Mast er Dat a –
Loc at i ons – One-Ti me Loc at i on
One-time locations can be
created in two ways:
Manually by the user on the
shipment/freight request UI
Automatically by the system based
on address data of an incoming
request to SAP TM
A temporary location is
created in SAP TM, which can
be deleted later in batch (see
notes)
An existing business partner
(e.g. shipper, consignee) is
needed in order to make the
association of the new
address
Transaction data
Shipment request
Freight request
TM
One-time location
One-time location
If the shipment
request refers to
an existing
location then this
location is used
The deletion of one-time ship-to locations is included in the re-organization job for
locations. This batch job checks for the existence of orders for this location. Only if no
orders, e.g. sales orders, deliveries, shipments, exists anymore this location is deleted.
Report to delete locations /SAPAPO/DELETE_LOCATIONS.
OSTA: Override ship to address (sometimes also called One time Ship to Address.
Address validation will not be performed, e.g. Berliner Street and Breliner Street are
different streets
9
©SAP 2009 / Page 9
SAP TM Mast er Dat a –
Loc at i ons – Geoc odi ng 1/2
A geocoder determines the geographical coordinates (longitude and latitude) from a gi ven address.
In SAP TM, three level s of geocoding are possi ble:
Standard (SAP0) (included in SAP TM software license)
Zip code (Internet Graphics Server) comes from PTV (included in SAP TM software license)
Full addresses (Internet Graphics Server) (add. license)
Mileage software (PC Miler, ALK) can be integrated on a custom basi s via exi sting Web servi ces.
These coordinates are used to determine distances between locations.
The geocoding program supplied by SAP determines the longitude and latitude based on the country and region codes.
PTV (Karlsruhe, Germany)
Prerequisites for level 2 and 3:
Install the geocoding program on a WINDOWS Server
Establish an RFC-Connection to the geocoder
See note 433785 for explanation about installing a third party geocoder
10
©SAP 2009 / Page 10
SAP TM Mast er Dat a –
Loc at i ons – Geoc odi ng 2/2
Prerequisites for all levels:
Registering geocoding
program in the system
Assigning geocoding
program to countries
Assigning relevant address
fields for geocoding
To test the geocoder, run report GEOCODING_FIRST.
It is possible to use more than one geo-coding program.
It is possible to set up the system for using specific geo-coding programs for specific
countries.
After geocoding you find the coordinates in the location master data on the tab general
Geocoding Settings are done in configuration:
Menu Path via SPRO:
SAP Netweaver -> General Settings -> Set GeoCoding Preferences
11
©SAP 2009 / Page 11
SAP TM Mast er Dat a –
Loc at i ons – Al t er nat i ve I dent i f i er s 1/2
Alternative Identifiers
Definition of alternative identifiers
for locations like customers,
terminals, sea ports, airports, e.g.
based on an official agency code list
like IATA-code list, UN code list…
Users can search for locations by
alternative identifiers in any SAP TM
transaction.
Agency Code Lists
If an agency is defined via a 3-digit
agency code (United Nations EDIFACT
data element 3055 DE 3055), these
codes can be used for external
communication or to visualize it on
certain UI screens
Project-Based Code Lists
Can be used for input help search on
locations
In the logistics world, one particular location (e.g. port, airport, terminals) might
be identified by different location codes. Oftentimes agencies define standard
location code lists or a company might work with its own particular identifiers.
SAP TM needs to allow users to work with different location codes.
New in SAP TM 7.0
Excerpt from IMG:
Define location scheme agencies
This configuration is optional. The agencies that you define must represent organizations
that maintain standardized identification schemes for locations. For more information,
see the 'Requirements' section.
Define alternative location identifier types (ALI types)
ALI types distinguish between several identification schemes that can be used to identify
locations and can therefore be used to assign alternative location identifiers to locations.
Define code lists for specific ALI types
For each ALI type, you can create a code list. Code lists are useful for project-specific
identification schemes or if you intend to restrict the identifiers to a subset of a
standardized identification scheme.
If you define a code list, you have to select the identifiers that refer to the ALI type from
the code list. If you do not define a code list, you can freely choose the identifiers.
12
©SAP 2009 / Page 12
SAP TM Mast er Dat a –
Loc at i ons – Al t er nat i ve I dent i f i er s 2/2
Alternative Identifiers in the Location Master
New in SAP TM 7.0
Search Locations via Alternative
Identifiers
13
©SAP 2009 / Page 13
SAP TM Mast er Dat a –
Loc at i ons – Tr ansshi pment Loc at i on
Transshipment Location
Used for unloading goods from one vehi cl e resource and loading it onto another vehicl e resource during the transportation process
Necessary when different MTr or different transportation servi ce providers (carriers) have to execute a transportation process, such as the following:
Truck – ocean – truck
Truck – rail – truck
May also be used when consolidating or deconsolidating goods for transportation
Transportation
Zone
Plant
Transshipment
Location
Plant
Assignment of locations / transportation zones to transshipment location is done in TA
/SCMTMS/LOC_TRANS
SAP TM planning supports parallel hubs and the selection of these
Requires special parameter to activate this behavior, as parallel hubs have a huge
performance impact this functionality is not general available
14
©SAP 2009 / Page 14
SAP TM Mast er Dat a –
Loc at i ons – I nc ot er m Loc at i on
Incoterm Location
Used in combination with an incoterm (e.g. FOB – Free on Board)
Transportation charge management considers this location when distributing charges to
different business partners vi a a Business Add-In (BAdI)
15
©SAP 2009 / Page 15
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role Codes and Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
16
©SAP 2009 / Page 16
SAP TM Mast er Dat a –
Pr oduc t s
Products
Products are optional master data
They can be created in the following ways:
Manually in the NetWeaver Business Client or SAP GUI
Via the Core Interface (CIF) by transferring material master data from SAP ERP
As an alternative, the system can
work with cargo classification codes
Reduction of master data
maintenance
Cargo codes can be entered to
identify the shippable items in a
shipment request
17
©SAP 2009 / Page 17
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role Codes and Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
18
©SAP 2009 / Page 18
SAP TM Mast er Dat a –
Means of Tr anspor t Ver sus Vehi c l e Resour c es
Mode of
Transport
Means of Transport (MTr)
Vehicle Resources
Mode of Transport
Type of transport, e.g.
road or sea
MTr
Method of transport
Examples: rail, car, truck,
refrigerated truck, LTL,
FTL, barge, vessel
Vehicle Resources
Examples: maintenance
of capacities, depot
locations, and other
settings for individual
vehicles
In addition a means of transport can be assigned to a transportation mode (see
maintenance of MTr)
Transportation Mode
The Transportation Mode is a code defined to indicate the actual ‘mode’ of
transportation. This code is assigned to the Transport Method. The Transportation
Mode in SAP TM should correspond to the Transportation Mode used in the ERP
System (ERP IMG: Logistics Execution Transportation Basic Transportation
Functions Routes Define Routes Define Modes of Transport).
Means of Transport
The Means of Transport is used to represent a ‘method’ of transportation such as a 48’
truck with full truck load capacity or refrigerated truck. The Means of Transport are
assigned to Vehicle Resources in SAP TM master data. In addition, the Means of
Transport will be assigned to Transportation Lanes.
Vehicle Resources
Vehicle Resources are used to represent a unit of transportation and its capacity and
planning parameters.
A Vehicle Resource is independent of a particular carrier.
19
©SAP 2009 / Page 19
SAP TM Mast er Dat a –
Means of Tr anspor t (MTr ) - Over vi ew
Means of Transport
Represents a ‘class’ of vehicles
The MTr is used to define cost
structures and geographical availability
(via the concept of transportation
lanes)
Used to determine whether a resource
is part of your own fleet or that of an
external provider
In case of an external provider, an MTr
can be defined as a multiresource, e.g.
10 trucks exist for this MTr (see
separate slide)
Defines whether a resource is traveling
based on a fixed schedule, e.g. sailing
or rail schedule (see separate slide)
Defines if GIS is used or an average
speed
An MTr can be passive, e.g. a trailer
that needs to be pulled by a tractor
An MTr can have zero capacity, e.g. for
a tractor that is used to pull a trailer
GIS: Geographical Information system, can determine the speed based on detailed map
information, if GIS is used then the speed for slow, average and high speed needs to be
determined
Example for MTr: ship, aircraft, truck15to, truck25to
A MTr represents refrigerated trucks with a specific cost structure and geographic
availabilty.
Within this group several vehicle resources exists:
3 trucks with capacity of 3500 KG
2 trucks with capacity of 3600 KG
All trucks do have the same geographical availibilty and the same cost structure.
20
©SAP 2009 / Page 20
SAP TM Mast er Dat a –
Means of Tr anspor t & Geogr aphy
Where the MTr is available (from
where to where)
What the costs are for the MTr in
this region/connection
Which carriers are available for
the MTr in this region/connection
How the TSP/carrier selection is
to be performed for this MTr in
this region/connection
A means of transport is used in connection with a
transportation lane to define the following business rules:
For more details see the slides about transportation lanes following later in this chapter
'Own means of transport’
Vehicles belonging to a MTr which has the flag 'Own means of transport’ can have a
depot location. Depending on customizing setting the optimizer will make sure the
Resource starts and ends at this depot location within one optimization run.
To use the Own-means-of-transport functionality you have to set the flag in the means-
of-transport and assign a location to the resource master data
For planning:
A planned shipment always starts at the depot location (independent of the flag of the MTr)
On completion of the shipment planned by the optimizer, the vehicle must always return to the depot
location (if the flag on the MTr is set)
21
©SAP 2009 / Page 21
SAP TM Mast er Dat a –
Means of Tr anspor t – Hi er ar c hi es
Means of Transport Hierarchy
Available in Customizing to simplify the
maintenance of transportation lanes
Hierarchies are taken into consideration
in the following functions:
Transportation service provider selection
Transportation network (for example,
transportation lanes)
Incompatibilities
Profiles and settings
Lane determination, distance
determination, and duration
determination
Temperature-
controlled truck
Cooled Chilled Standard
Truck
To define a means of transport hierarchy go to IMG ->Transportation Management ->
Master data ->Transportation Network ->Maintain Means of Transport
Create a main MTr and then assign this to the sub-MTr in the field „Sup. MTr“Field
For more information, see the Implementation Guide (IMG) for SAP TM under Master
Data ->Transportation Network ->Define Hierarchy Priorities for Lane Determination.
22
©SAP 2009 / Page 22
SAP TM Mast er Dat a – Geogr aphi c al Hi er ar c hy
and Means-of -Tr anspor t Hi er ar c hy
Treating ‘ability-to-reach’ as properties of the geographical hierarchy and the
means-of-transport hierarchy
This way, the given intra-zone lane for Zone 0 and " Truck" implies:
Any two locations within Zone 0 are reachable not only with resources defined as MTr " Truck" ,
but also with MTr " Truck-16t" and " Truck-40t"
Any two locations within Zone 2 are reachable not only with resources defined as MTr " Truck" ,
but also with MTr " Truck-16t" and " Truck-40t"
Truck
Truck-16t Truck-40t
Zone 1 Zone 2
Zone 0
The concept of transportation zones will be explained later
23
©SAP 2009 / Page 23
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role Codes and Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
24
©SAP 2009 / Page 24
Calendar resource for
opening times
Handling resources (could also be
a multiresource)
SAP TM Mast er Dat a –
Resour c es – Over vi ew
Vehicle resource Transportation unit resource
Resources are objects that transport or handle the goods.
Driver
Path: SAP menu Transportation Management->Master Data Resource
A vehicle resource always represents a specific vehicle, for example:
Double-axis truck with maximal number of pallets 20, 12 tons weight capacity, 37 m3.
Unloading forklift with a capacity of 100 tons per hours.
Calendar resources are used to model when a plant is available for loading/unloading. They are
assigned to a location.
Resources specify the available capacity and the hours on which they can be operated
Resources can have different capacity dimensions and can be linked to a schedule. They can
contain shifts and are always assigned to a MTr
Resources must be created in SAP TM, can not be transferred from ERP via CIF
Single- or Multiresources are used to model loading and unloading resources
(inbound/outbound).
A single resource allows one parallel loading / unloading activities while a multi resource
models several loading / unloading activities. A single resource can only have two different
situations: Either it is loaded with an activity or it is not loaded at all.
Multi resources are used to map resources on which several activities can be carried out at a
time. The maximum number of activities that can be scheduled at the same time depends on the
organizational or technical conditions for the resource.
A Handling Resource (Resource Type H) is a single- or multi-resource
Capacities in the form of available working hours including downtimes are specified for the
handling resource
25
©SAP 2009 / Page 25
SAP TM Mast er Dat a –
Vehi c l e Resour c e
Vehicle Resources
Model the vehicles that are physically available to
transport and move goods
Depend on the MTr
Can move by itself (‘active’) or rely on another resource to
be pulled (‘passive’)
Can be modeled with or without capacity
Acti ve resource with no capacity
Passive resource with capacity
MTr combinations can be used to model a truck-and-
trailer combination
Multiresources can be used to model an external fleet in
one step
Acti ve resource with capacity
An instance of a particular means of transport, or a group of identical instances of
means of transport that can provide transportation services.
You use this business object to map the capacity and availability of vehicles that you
want to use for transportation.
You can choose up to eight dimensions and units of measurement to describe the
capacity (Mass and Volume are predefined by default). Planning can only take the
vehicle capacity into account if these correspond to the dimensions and units of
measurement that you have defined in a freight unit building rule.
26
©SAP 2009 / Page 26
SAP TM Mast er Dat a –
Mul t i r esour c es (ex t er nal Resour c es)
2008 Wipro Ltd
Business Requirement:
Case 1: A company has a lot of resources of the same type and does not need to plan on
individual resources as the resource master maintenance causes quite a lot of effort.
Case 2: A non-asset-based logistics service provider that subcontracts all its transports to a
third-party carrier may not need to maintain data for resources of a third party.
Definition of resources of the
same type in one step, e.g. 10
trucks
The concept of multiresources
enables the customer to maintain
only one resource master and to
specify how many resources of
that type (MTr) are actually (i.e.
physically) available, or
alternatively there is no
restriction at all on the number of
resources available
Creation of multiple tours for the
same multiresource (resource
counter)
New in SAP TM 7.0
27
©SAP 2009 / Page 27
SAP TM Mast er Dat a –
Vehi c l e Resour c e – Means-of -Tr anspor t Combi nat i ons
A truck-and-trailer combination, for
example
Number of objects of each MTr within
the combination, e.g. 1 truck and 2
trailers
Capacities (several UoM): Maximum
capacities of the combination
Additional (freely definable) attributes:
Can be used for
incompatibilities/compatibilities;
based on a customizable attribute
definition (code + text)
Coupling/uncoupling durations are
defined per passive MTr
Max. capacity for the
MTr combination
Which and how many
of these MTr belong to
the MTr combination
Additional attributes
for compatibilities
Means-of-Transport Combination (MTr Combination)
Can be Used to Model the Following:
An instance of a particular means of transport, or a group of identical instances of
means of transport that can provide transportation services.
You use this business object to map the capacity and availability of vehicles that you
want to use for transportation.
You can choose up to eight dimensions and units of measurement to describe the
capacity (Mass and Volume are predefined by default). Planning can only take the
vehicle capacity into account if these correspond to the dimensions and units of
measurement that you have defined in a freight unit building rule.
28
©SAP 2009 / Page 28
SAP TM Mast er Dat a –
Tr anspor t at i on Uni t s & Dr i ver s
Transportation Units
Used to model freight units that have to
be moved by a vehicle resource
Examples include containers, flatbed or
chassis
Transportation units can only be
configured / loaded manually
Transportation units can be tracked
separately from vehicle resources via
SAP Event Management (SAP EM)
Drivers
Person who operates vehicle resources
Offers skills, such as licenses
Examples: truck driver, captain
No automatic support in planning, only
used for manual planning
Labor resources are defined in the same transaction as resources themselves, press the
Driver button to create a driver.
Future TM release will allow for integration to SAP HCM module and consideration of
Hours-of-Service (HOS) concepts that need to comply to government regulations (e.g.
maximum operating times)
29
©SAP 2009 / Page 29
SAP TM Mast er Dat a –
Compar t ment s and Tr ai l er s
Compartments
Compartments divide the truck and
also the trailer into smaller units
Flexible and fixed compartments
Incompatibilities can be used to
restrict certain freight units to be
transported together
Allows the assignment of dangerous
goods to certain areas of the truck
Improves transport planning for oil and
gas, chemicals, retail and consumer
products
Capacity constraints for compartments,
trucks, trailers, and vehicle
combinations are considered
simultaneously
30
©SAP 2009 / Page 30
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role Codes and Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
31
©SAP 2009 / Page 31
SAP TM Mast er Dat a –
Sc hedul e
Start
(mandatory)
(mandatory)
(mandatory)
(mandatory) optional
Truck: TSP1
Schedule definition
Shipment 1
Shipment 2
Schedule
Used to define a train schedule or a sailing schedule, for example
A schedule defines a stop sequence that consists of a start stop, an arbitrary
number of intermediate stops, and a destination stop. Each stop can be a location or
a transportation zone.
Has a means of transport assigned
The user can define an arbitrary number of transportation service providers for a
schedule
A departure calendar or time table defines the departure dates and the duration of
the trip
Schedules are using internal transportation zones for representation
In SAP TM only schedules with mandatory stops are supported, eWMsupport optional
stops
Stops may be defined a mandatory or optional (zones are always optional). Automatic
planning will only support the schedules with mandatory stops only
BAPI are available to upload schedules.
/SCTM/BAPI_LEG_READ_MULTI BAPI-FuBa for reading schedules
/SCTM/BAPI_LEG_SAVE_MULTI BAPI-FuBa for create, change, read, delete
schedules
An interface will allow for uploading of schedules (I.e Airline flight schedules).
Stops in transportaton zones are not planning relevant
32
©SAP 2009 / Page 32
SAP TM Mast er Dat a –
Sc hedul e - Enhanc ement s
Schedule Without Resources
Creation of schedules without individual resources
Planning without individual resources
Enhancements of Schedule Master Data
Containing additional information such as vessel ID, flight number, voyage number
As of SAP TM 7.0
33
©SAP 2009 / Page 33
SAP TM Master Data – Business Purpose
Locations and Geocoding
Products
Means of Transport (MTr), Mode of Transport
Resources
Schedules
Special Topic
Role Codes and Type Codes
SAP TM Mast er Dat a - Par t 1
Contents:
34
©SAP 2009 / Page 34
SAP TM Mast er Dat a –
Rol e Codes and Type Codes
Role Codes and Type Codes
Some role codes are firm and
cannot be changed by the customer,
such as source or destination in the
location role code table.
Customers can add specific entries
to any role code or type code table.
A prominent use of role codes and
type codes is to leverage these
entries during input help search. A
lot of input help searches offer role
code functionality.
Role codes and type codes can also
be used when creating conditions.
SAP TM offers a variety of role codes or type codes that can be configured in
Customizing. These codes can be used to search for, add, and use customer-
specific information throughout the system.
35
©SAP 2009 / Page 35
Explain the function of the master data
elements in SAP TM
Explain the settings for geocoding
Understand the concept of products
Maintain and explain the settings for means of
transport
Maintain and explain the usage of resources
and schedules
Put the concept of type codes and role codes
into context
You are now able to:
SAP TM Mast er Dat a –
Uni t Summar y
36
SAP TM Master Data – Part 2
Transportation Lanes and Transportation Zones
37
©SAP 2009 / Page 37
Transportation Lanes
Means of Transport (MTr) Settings Relevant for
Transportation Lanes
Distance Calculation
Transportation Zones
Transportation Zone Hierarchy
Transportation Service Provider Profile (TSP Profile)
SAP TM Mast er Dat a – Par t 2
Contents:
38
©SAP 2009 / Page 38
SAP TM Mast er Dat a –
Tr anspor t at i on Lane 1/3
Represent a direct route between two locations in order to transport freight
from one location to another
Are typically maintained at transportation zone level
Are defined by:
Source and target locations
Direction
Available MTr
TSP (e.g. carrier) per MTr
Maintenance:
Individual
Mass maintenance
A transportation lane may connect:
A location (customer, vendor, plant, distribution center, carrier) with another
location
A location with a transportation zone (geographic region comprising various
locations), or vice versa
A transportation zone with a transportation zone
Using transportation zones as a start or destination will considerably reduce
the amount of transportation lanes to be maintained.
A transportation lane is needed in SAP TM to plan transports from one location to
another with a specific means of transport and a specific transportation service
provider (TSP).
Lanes have a validity period.
39
©SAP 2009 / Page 39
SAP TM Mast er Dat a –
Tr anspor t at i on Lane 2/3
Distribution
Center
Customer
Transportation Lanes
Supplier
Transportation
Zone
A transportation lane can be maintained between:
Two locations
A location and a transportation zone
Two transportation zones
A transportation zone itself
Location
A transportation lane points only in one direction, to model the reverse direction a
separate transportation lane needs to be created.
40
©SAP 2009 / Page 40
Information Assigned to a Lane
Start location and destination
location
Means of Transport
Validity
Distance and duration
Costs
Transportation service provider
(TSP) or carrier selection
settings
TSP
TSP business partner, e.g.
carrier or logistics service
provider
Transportation costs
Share of business
Priority
Continuous move
SAP TM Mast er Dat a –
Tr anspor t at i on Lanes 3/3
The system proposes time and distance of transportation based on the coordinates of
the locations.
You can maintain real data and set the flag for 'Fixed Transport Duration' and 'Fixed
Transport Distance'.
A carrier will be assigned in a lane under the transport type button 'Allocate carrier'.
Beforehand, the carrier has to be defined as a location (location type 1020). To do this,
an additional tab 'Carrier' is available.
41
©SAP 2009 / Page 41
Transportation Lanes
Means of Transport (MTr) Settings Relevant for
Transportation Lanes
Distance Calculation
Transportation Zones
Transportation Zone Hierarchy
Transportation Service Provider Profile (TSP Profile)
SAP TM Mast er Dat a – Par t 2
Contents:
42
©SAP 2009 / Page 42
Runtime Lane Geo Distance 80
Maintained Master Lane Distance 130
Master Lane Geo Distance 100
Runtime Lane Distance 104
SAP TM Mast er Dat a –
Cal c ul at i on of Di st anc e and Dur at i on
Runtime Geo Distance 80 X
=
Actual Runtime Distance 104
Maint. Master Lane 130
Master Geo Distance 100
Distance / Average Speed Per Unit = Duration
With GIS
By connecting the GIS to the Internet Graphics Server (IGS), distance and duration time
can be calculated for each means of transport within a transportation lane using exact
road details
Without GIS (Geographical Information System)
SAP TM will compute the runtime lanes during optimization. Corresponding
transportation lanes will be generated between all locations assigned to the
transportation zones. In the process, the cost information is taken from the
transportation lanes maintained. The distance/duration is calculated according to the
settings or taken from the transportation lane maintained.
The maintained distance in the Master Lane includes a factor for road/street map
variability. The Factor is obtained from the Means of Transport. This factor establishes
the proportion between the linear distance between two locations and the actual
distance covered by the vehicle transporting goods between them.
Included in the Means of Transport is the Average Speed of the transport method. The
Runtime distance is divided by the average speed to calculate the estimated Duration.
NOTE: If an external Geographical Information System is used to calculate the
distances, these distances are stored in a separate Table (/SAPAPO/TRDIDUPS) and is
NOT calculated at runtime.
In the means-of-transport you flag if this MOT is calculated by a GIS system. If the flag
is not set the aerial distance is used
If the GIS flag is set then the low, medium, high average speed is used. GIS systems
typically categorize streets by “slow”, “medium”, or “fast”.
43
©SAP 2009 / Page 43
SAP TM Mast er Dat a – Si ngl e Gener at i on of
GI S Di st anc es and Dur at i ons
Determines distance and duration
according to the GIS mode as
specified in the means of transport.
Duration is determined according to
the velocities maintained for the
means of transport.
Displays the GIS quality of the
calculated proposals.
0 =Aerial distance
1000 =Manually maintained
Any other entries represent specific
GIS providers.
100 =e.g. PTV
110 =e.g. ESRI
44
©SAP 2009 / Page 44
SAP TM Mast er Dat a –
Mass Gener at i on of GI S Di st anc es and Dur at i ons
Distances and durations
are calculated in a job
using the GIS server.
They are stored in table
/SAPAPO/TRDIDUPS.
If a location is added or
modified, this transaction
needs to be executed again
to update the GIS
information.
For more information, see
notes page on transaction
/SAPAPO/TR_IGS_BPSEL.
Transaction /SAPAPO/TR_IGS_BPSEL
This transaction obtains distance and duration information for the specified scope (lanes
and means of transport) from the connected GIS server and stores the results in table
SAPAPO/TRDIDUPS. When runtime lanes are created later on during an optimization
run, the distance and duration are obtained from this table.
Note: The job cannot be terminated without losing the data. Once the job is started all
old records are deleted, if the job is started with this setting.
45
©SAP 2009 / Page 45
Transportation Lanes
Means of Transport (MTr) Settings Relevant for
Transportation Lanes
Distance Calculation
Transportation Zones
Transportation Zone Hierarchy
Transportation Service Provider Profile (TSP Profile)
SAP TM Mast er Dat a – Par t 2
Contents:
46
©SAP 2009 / Page 46
SAP TM Mast er Dat a –
Tr anspor t at i on Zones
Can group locations as well as other zones.
Include one-time locations
Include zones with their locations and
subzones
Example:
All locations that are supplied by the same
warehouse are grouped into a transportation zone.
The following zone types are possible:
Direct Zone – locations are assigned directly to a
zone
Postal Code Zone – specified by a postal code or
postal code range
Region Zone – specified by a country or region,
e.g. state of Florida in the US
Mixed Zone – a combination of the three other
zone types
Transportation zones can dramatically reduce the effort needed to model your
geographic network; by grouping locations into zones, you can effectively reduce
master data volume in the SAP TM system.
If SAP ERP integration is used then the transportation zones are automatically created
from the address of the location and the location is automatically assigned to the
transportation zone
47
©SAP 2009 / Page 47
SAP TM Mast er Dat a –
Tr anspor t at i on Zones – Hi er ar c hy
Zones can include locations and other zones.
The assignment of zones to other zones can be maintained in transaction
/SAPAPO/RELHSHOW.
You cannot assign a zone to itself.
Z4 Z1
L1 H1 L2 L3
Z5 Z2 Z3
L4
By organizing transportation zones into hierarchies, you can inherit properties of
the superordinate transportation zone to the locations on lower levels of the
hierarchy.
The SAP TM relevant hierarchy can be defined in customizing Transportation
Management -> Transportation Network ->Define Transportation Zone Hierarchy
48
©SAP 2009 / Page 48
SAP TM Mast er Dat a –
Tr anspor t at i on Zones
Groups locations and zones
Can include locations based on
Identity
Region
Postal code
Includes one-time locations
Includes zones with their locations and sub-zones
Hubs can be loading or unloading points
49
©SAP 2009 / Page 49
Transportation Lanes
Means of Transport (MTr) Settings Relevant for
Transportation Lanes
Distance Calculation
Transportation Zones
Transportation Zone Hierarchy
Transportation Service Provider Profile (TSP Profile)
SAP TM Mast er Dat a – Par t 2
Contents:
50
©SAP 2009 / Page 50
SAP TM Mast er Dat a –
TSP Pr of i l e (‘Car r i er Pr of i l e‘)
The TSP profile allows you to see the assigned lanes from the TSP perspective.
You can also remove existing assignments and add new assignments.
You have different views of the lane-TSP assignment.
You can store the following objects in a TSP profile:
Freight code sets
Transportation lane and
TSP-specific parameters
Product freight groups
Transportation groups
Equipment groups and
equipment types
Fixed transportation costs
Dimension costs
TSP’s are business partners that you have assigned the business partner role ‘Carrier’
to
51
©SAP 2009 / Page 51
Describe the usage and setup for transportation
lanes
Describe the settings of the means of transport
relevant for transportation lanes
Describe the options of distance calculation
Describe the usage of transportation zones and
transportation zone hierarchies
Describe the usage of TSP profiles
You are now able to:
SAP TM Mast er Dat a – Par t 2
Uni t Summar y
52
©SAP 2009 / Page 52
Copyr i ght 2009 SAP AG
Al l Ri ght s Reser ved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein
may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,
eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
J ava is a registered trademark of Sun Microsystems, Inc.
J avaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.
Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothingherein shouldbe construed
as constituting an additional warrant.