Transportation in

EWM
Supply Chain Execution
SCM 5.0

© SAP AG 2005

© SAP AG 1
 Transportation in EWM - Definitions

Shipping and Receiving

Shipment: Document containing all the goods that are consolidated by a

ship-from party and are then transported together from an issuing
location (a plant, for example) to a destination location (a customer, for
example). The shipment forms the basis for planning, executing, and
monitoring the transportation of goods.

Freight Document: Document that reflects the result of planning and

consolidating shipments and is used in collective goods traffic, for
example. The freight document determines the load on a vehicle.

© SAP AG 2005

„ You can create shipments both manually and automatically. In conjunction with the processes in the
Extended Warehouse Management (EWM) component, the following classification is relevant:
Planned shipment: Can still change with regard to type and size, for example, due to a subsequent delivery
split in the Extended Warehouse Management (EWM) component.
Final shipment: Is fixed with regard to type and size, in other words, it is confirmed. Most of these
shipments are already packed or loaded.
„ The freight document is relevant to transferring planning results and to printing, and maps trips as well as
multiple pickups and stops.
„ You can create freight documents both manually and automatically.
„ You define the freight document type in Customizing for Transportation Management (TM). It contains all
the important control parameters for the freight document.
„ You can manually set statuses in the freight document, for example, Transportation Completed. In this case,
this status is set automatically for all the bills of lading contained in the freight document. These are then
printed automatically. You can also print master bills of lading and freight lists from the freight document.
For more information about printing, see Post Processing Framework.
„ By integrating Transportation Management (TM) with the Extended Warehouse Management (EWM)
component, you enable bills of lading to be printed automatically when vehicles are being loaded.

© SAP AG 2
 Shipment

Instance Settings Use

Transportation request In Customizing for TM under Define Shipment Type, you You can assign transportation requests to
have not set the UI Changeable indicator for the shipment bills of lading or to freight documents.
types Planned Transportation Request and Final
Transportation Request.
In Customizing for TM under Maintain Settings for
Determining Shipment Types, you have defined the
shipment types Planned Transportation Request and Final
Transportation Request as predecessor shipment types.

Bill of lading In Customizing for TM under Define Shipment Type, you You can assign transportation requests with
have set the UI Changeable indicator for the shipment type common properties to a bill of lading, for
Bill of Lading. example:
In Customizing for TM under Maintain Settings for Transportation service provider
Determining Shipment Types, you have defined the Ship-from party and ship-to party
shipment type Bill of Lading as a successor shipment type. Delivery date
You can manually set statuses in the bill of
lading, for example, Transportation
Completed. In this case, the relevant paper
document (international bill of lading (CMR)
or bill of lading according to VICS standard)
is printed automatically. For more information
about printing, see Post Processing
Framework.

© SAP AG 2005

„ A shipment can have different characteristics that are determined by the shipment type as well as its
relationship to other shipments. You define the shipment type in Customizing for Transportation
Management (TM). It contains all the important control parameters for the shipment document.

© SAP AG 3
 Why Routing Guide ?

1. Deliveries must be as close to promised dates as

possible.

2. Hence ATP check must consider Transportation

Activity more accurately

3. ERP Routes have no significance in ATP and

Planning

4. Routing Guide provides a simple, effective and

highly flexible alternative wherein you can
• Define Routes, Schedules and TSP Profiles
• Setup Trip Determination Strategies

5. Routing Guide can be called directly or can be

integrated into APO ATP check through CPS

© SAP AG 2005

„ The aim of route determination is to find the most cost-effective route from a large number of
routes.
„ Route determination is executed in the routing guide. It runs automatically in the background, for
example, when a Global Available-to-Promise (Global ATP) check is performed in SAP Customer
Relationship Management (SAP CRM) during the creation of a sales order.
„ A report is available for simulating route determination in Extended Warehouse
Management (EWM).

© SAP AG 4
 Route Definition

Route: Sequence of legs

connected by transshipment
locations.

© SAP AG 2005

„ The route represents a framework or corridor that comprises a multitude of trips, in other words,
possible concrete itineraries. The system uses routes to determine trips in route determination.
„ The following figure shows a route with three legs that are connected by the transshipment
locations P and M. It also shows a trip for each of the two sequence strategies for the middle leg.
„ You can form cross-docking routes from routes.

© SAP AG 5
 Route Network

© SAP AG 2005

„ This figure shows a route network consisting of two Cross Docking routes.
„ You use cross-docking routes (CD routes) to link routes to route networks. The system takes into
account CD routes when you use route determination as part of cross-docking. Here you can define
per route pair (inbound route and outbound route) whether goods at the cross-docking location (CD
location) are to remain on the same vehicle or whether they are be loaded onto a different vehicle.

© SAP AG 6
 Process Overview
CRM EHS SCM

User enters
APO does gATP incl. sourcing
Sales Order

Scheduling: Starts back- or forward scheduling

+ calls RG if required

RG finds Routes
between source and
destination incl. TSP’s
+ MTr’s, builds Trips

EHS determines
dangerous goods RG schedules and
data calculates costs

RG calls EHS filter,

eliminates trips
EHS does DG checks

RG calls BADI filter

RG evaluates all trips

based on costs

Scheduling: uses the dates calculated by RG

and continues with the process

CRM updates order Scheduling: Assigns dates to order

© SAP AG 2005

© SAP AG 7
 Basic Data and Terminology

„ Locations
‹ All ERP Plants, CRM Business Partners are replicated in SCM system as valid Locations
z CRM Business Partners can be customers, vendors or Transportation Service Providers
‹ Locations can also be created in the SCM system directly
„ Zones
‹ Zones group locations by
z direct assignment
z postal codes or
z regions
„ Transportation Service Provider Profile
‹ Every TSP must have a profile, defining
z how the TSP services a particular geography
z what products they can service etc.
„ Transportation costs
‹ Transportation costs based on distance/time/quantity can be assigned to every TSP
„ Calendars
‹ Can be created for defining departure times, transportation times and working times
„ Routes
‹ Routes define valid transportation paths between two locations.
‹ They consist of
z Legs – Uni-modal paths of the route with two or more stops. Stops can be locations/zones.
z Shipment conditions defining when the route can be used
z lead times for the route
„ Trips
‹ Instances of Routes with TSP’s + MTr’s + Schedules.

© SAP AG 2005

© SAP AG 8
 Example Route

AMS

WDF

Zone NY

LA

Leg America (Truck)

Leg Atlantic (Ship)
Leg Europe (Truck)

© SAP AG 2005

© SAP AG 9
 Main Transactions

„ /SAPAPO/LOC3 – Maintain Locations

„ /SCMB/SCHED_CAL– Maintain Calendars

„ /SCTM/ZONE – Maintain Zones

„ /SCTM/ROUTE – Maintain Routes

„ /SCTM/TSPP – Maintain Profile for TSP

„ /SCTM/TCPRF – Maintain Cost Profile for TSP

„ /SCTM/RGINT – Run Interactive Test Report for RG

© SAP AG 2005

© SAP AG 10
 Maintain Route - UI

© SAP AG 2005

© SAP AG 11
 Advanced search – multiple options

• Routes can be
searched between
locations
• Routes can also be
searched for a given
stop (dealer)

© SAP AG 2005

© SAP AG 12
 Route Header details

Weight, Volume and Dimension restrictions on Route header

© SAP AG 2005

© SAP AG 13
 Stops – Weight & Volume per stop

Weight, Volume and Dimension restrictions can be specified per stop

(dealer)

© SAP AG 2005

© SAP AG 14
 Request types (Delivery types, Sales Order types…)

• Allowed Request types for the complete Route

• Allowed Request types for Stops (dealers)

© SAP AG 2005

© SAP AG 15
 Departures

Different departure calendars can be specified depending on the request

type

© SAP AG 2005

© SAP AG 16
 Cross-dock routes

• A Cross-dock route
defines a network of
routes at a given
location
• Such a location is
called a cross-dock
location
• Transportation of
goods from any
incoming route can
continue on any of
the outgoing route
specified in the
network

© SAP AG 2005

© SAP AG 17
 Copyright 2005 SAP AG. All Rights Reserved
„ 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
„ IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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.
„ Java is a registered trademark of Sun Microsystems, Inc.
„ JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
„ MaxDB is a trademark of MySQL AB, Sweden.
„ SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.

„ The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
„ This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
„ SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document 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.
„ SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
„ The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

© SAP AG 2005

© SAP AG 18