SAP AG SCM612 0-1

SAP AG 2008

SAP AG 2008

!"

"! #$%&

Software components used in the course 2008/Q1 Material number 50088756

SAP AG SCM612 0-2

SAP AG 2007

'!

Copyright 2007 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, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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. 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 AG SCM612 0-3

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 SCM612 0-4

SAP AG 2008

$ ($

Required Prerequisites SCM611 Transportation SAPSCM mySAP Supply Chain Management

Overview Recommended

Knowledge of Supply Chain Theory Knowledge of basic transportation planning

and execution processes SCM210 Core Interface APO SCM610 Delivery Processes

SAP AG SCM612 0-5

SAP AG 2008

$# "

Participants Project team members responsible for the

implementation of APO TP/VS SAP consultants and SAP partners

Duration: 5 days

User notes These training materials are not a teach-yourself program. They complement the explanations

provided by your course instructor. Space is provided on each page for you to note down additional information.

There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.

SAP AG SCM612 0-6

SAP AG SCM612 1-1

SAP AG 2005

Course Goals Course Objectives Course Content Main Business Scenario

Contents:

SAP AG SCM612 1-2

SAP AG 2005

This course will provide you with: An understanding of the Master Data requirements and

integration between APO TP/VS and an ERP system (or other external system)

Detailed knowledge of the Transportation Planning / Vehicle Scheduling (TP/VS) component of APO

SAP AG SCM612 1-3

SAP AG 2005

At the conclusion of this course, you will be able to: Use the TP/VS component of APO to plan both inbound

and outbound shipments Create the necessary integration models to

communicate data between an R/3 system and the APO TP/VS component

Make the necessary customizing settings required to perform transportation planning, vehicle scheduling and transportation service provider selection in the TP/VS environment

SAP AG SCM612 1-4

SAP AG 2008

Unit 1 Course Overview

Unit 2 Transportation Processes Overview

Unit 3 ERP Organizational Units,Shipments and Integration

Unit 4 TP/VS Master Data

Unit 5 Supply Chain Engineer

Unit 6 TP/VS Transaction Data

Unit 7 Vehicle Scheduling (VS) Basic Settings

Unit 8 Vehicle Scheduling (VS)

Unit 9 Transportation Service Provider Selection

Unit 10 Additional Topics

SAP AG SCM612 1-5

SAP AG 2005

As a member of the project team of a company that manufactures and sells computers and related components, you are responsible for the implementation of the APO TP/VS component that is to be interfaced with an SAP ERP System.

Your task is to integrate the APO TP/VS environment with your ERP system by making the necessary customizing settings, creating the Integration models to transfer the necessary master and transaction data and establishing the TP/VS models to perform the short to intermediate transportation planning for your company.

SAP AG SCM612 1-6

SAP AG SCM612 2-1

SAP AG 2008

Contents: The Transportation Management System (TMS) ERP Logistics processes Transportation planning and execution with ERP Transportation planning with TP/VS

SAP AG SCM612 2-2

SAP AG 2008

At the conclusion of this unit, you will be able to: Define processes related to transportation planning Identify the ERP documents that are related to

transportation planning Understand planning in ERP vs. planning in SCM

TP/VS

SAP AG SCM612 2-3

SAP AG 2008

It is important to understand the fundamental business processes that are related to transportation planning and execution

Example processes: A transportation planner is planning the logistic

activities to delivery goods to his customers Another transportation planner is creating planned

shipments for the pick-up of purchased items from his vendor.

A shipper is contacting a logistic service provider to check availability and price of a certain truck

SAP AG SCM612 2-4

SAP AG 2008

The target of the transportation planning process is to optimize the inbound, outbound and intercompany transportation.

The Transportation Management scenario comprises the following main processes: Document entry in ERP Dynamic route determination Vehicle Scheduling Carrier Selection Collaborative Transportation Planning Transfer Deliveries and Shipments to ERP Execute Shipment in ERP

The target of the transportation planning process is to optimize the inbound or outbound transportation demand between a plant/DC and different other locations such as suppliers and customers.

The optimization covers the own fleet as well as carrier vehicles. Carrier selection can be executed to select carriers based on least cost, business share and/or priority.

The Transportation Management scenario comprises the following main processes:

Document entry

Dynamic route determination

Vehicle Scheduling

Carrier Selection

Collaborative Transportation Planning

Tendering

Transfer Deliveries and Shipments to ERP

Execute Shipment in ERP by picking and packing deliveries, goods issue posting, set status shipment end and archive shipments.

SAP AG SCM612 2-5

SAP AG 2008

!" #

!$#!%

!%&'(%)

%*

+,

!!

#

The ERP (LES) system is used for execution, while the planning of the shipments is performed in the SCM (TP/VS) system. The BW system is used for reporting.

SAP AG SCM612 2-6

SAP AG 2008

Transport-relevant information as selection criteria

Grouping of deliveriesMeans of transport, Service

agents, Freight cost simulationMonitoring

Calculation of transportation costs

Split criteriaCopy of transport-relevant

information (Means of transport, shippingtype )

ShipmentFreight

CostDocumentOrder

OutboundDeliveryOutboundDeliveryDelivery

n : n n : 1 1 : 1

CustomerInvoice

,$-. .

/ + 0

&1

The transportation-relevant information is copied from the order item into the outbound delivery header. It can, therefore, be used as the split criteria for outbound deliveries. You cannot, for example, put two order items with different shipping types into one outbound delivery. (set data transfer and split criteria in copying control order delivery.)

Order relevant transportation data: Means of transport: Indicates the specific vehicle type with which the goods are to be transported,

such as 20t truck, ship or bulk container. Material master records with a Material Type of Packaging Material are maintained for means of transport.

Shipping type: You can use this to define the characteristics of the mode of transport, such as road, rail, or sea.

When creating shipment documents you can use transportation-relevant information as selection criteria. This means that you can, for example, group deliveries with means-of-transport type truck and means of transport small truck into one shipment.

Freight Cost Simulation / Shipment Monitoring When you are planning the shipments, the capacity of the means of transport e.g. truck is checked by

the system. If this capacity is exceeded, you will receive a warning. Shipment cost document -> copy into customer invoice

SAP AG SCM612 2-7

SAP AG 2008

ShipmentFreight

CostDocumentOrder

OutboundDeliveryOutboundDeliveryDelivery

n : n n : 1 1 : 1Customer

Invoice

Shipment

Shipper do transportation planning on their own

Carrier

InformationFax, EDI, Tendering Portal

Status

CarrierSettlement

/ + 0

*

&,1

Lets have a look at the document in a different scenario: Shipper with external Transportation Resources Carrier

In this scenario the shipper do the transportation planning on their own Order Delivery Shipment Creation

These shipments are transferred to the external carrier by Fax, EDI, Internet Tendering And carrier records status information back. In the system of the shipper the cost document is created information copied to customer invoice

and for carrier settlement

SAP AG SCM612 2-8

SAP AG 2008

ShipmentFreight

CostDocument

OutboundDeliveryOutboundDeliveryDelivery

n : 1 1 : 1

Shipper

LSP

ShipperSettlement

ShipmentStatus

mySAP ERPof LSP

LSP = Logistic Service Provider

OrderOutboundDeliveryOutboundDeliveryDelivery

n : n

CustomerInvoice

/ + 0

*

&( 1

Lets have a look at the document in the following scenario: Shipper with external Transportation Resources Logistics Service Provider

In this scenario the deliveries are transferred to the LSP, who does the transportation planning, shipment creation etc. and sends a customer invoice to the shipper.

SAP AG SCM612 2-9

SAP AG 2008

%* .

Shipment by truck from one plant to one customer

Shipment using several trucks from one plant to several customers

Shipment by rail from the vendor to the plant

Empty return shipment from the customer to the plant

Shipments using different modes of transportation from several plants to several customers

Direct Shipment = individual shipment Multi Pick and Multi Drop = Collective Shipment Multimodal Multiple legs, etc. transportation chain A company can use different Transportation Scenarios with different means of transport Different Shipment Types are:

individual shipment (one shipment from one single point of departure and one single destination and in most cases one mode of transport)

collective shipment (shipment with one or more points of departure and one or more destinations and in most cases, only one mode of transport is used)

transportation chain (one or more points of departure and one or more destinations, various modes of transport like road, rail, or sea can be used and various legs). Several shipment documents are created: preliminary legs, main leg, and subsequent legs)

Shipment types are defined in customizing with several parameters e.g. Leg Determination; Copy control etc.

SAP AG SCM612 2-10

SAP AG 2008

Shipment

Sales Orders create Demands

Deliveriescreate

Freight Units

create

update

update

- Carrier Selection

checks

checks

Mid

-an

d sh

ort

-te

rm o

ptim

iza

tion

Planned Shipments

Fixed Shipments&

Creation of deliveries

Fixed Shipments

create

Co

ntrol R

ules

update

update

Sales orders, outbound deliveries and shipments can be used to create transportation demand in TP/VS. The TP/VS planning process using sales order data will create the delivery and the shipment documents

in the ERP system. The TP/VS planning process does not make any changes to the sales documents that are in the ERP

system.

Generally, transportation-related changes made to an ERP document is updated in the corresponding TP/VS document.

SAP AG SCM612 2-11

SAP AG 2008

-

Shipment

Demands

Deliveries create

create

update

update

checks

checks

Mid

-an

d sh

ort

-te

rm o

ptim

iza

tion

Purchase Orders

checks

update

PurchaseRequisitons create

Freight Units

Planned Shipments

Fixed Shipments&

Creation of deliveries

Send Shipments

- Carrier SelectionC

ontrol

Rules

create

Purchase Orders, Stock Transport Orders, Inbound Deliveries and Shipment documents can be used to plan inbound transportation demand.

When Purchase Orders/Stock Transport Orders are provided to TP/VS for planning, TP/VS will create the Inbound Delivery and Inbound Shipment document data for the ERP System.

Transportation demands from Supply Network Planning (SNP) can also be used in TP/VS for planning. Transportation relevant changes made to an ERP document are updated in the corresponding TP/VS

document.

SAP AG SCM612 2-12

SAP AG 2008

,

Shipment

Orders update Demands

Deliveries

Shipments

Deliveriesupdate

updatemanualchanges

manualchanges

New

o

ptim

izat

ion

ru

n

update

update

Transportation planning relevant changes made to any ERP document that has a corresponding TP/VS document will be made to those documents.

A shipment in the SCM system changes its status if you change documents in the ERP system that are contained in a planned shipment in the SCM system.

Note: You can find a process list with the expected behaviour of the SCM system when changing the planning objects in the OLTP system in note 362445.

SAP AG SCM612 2-13

SAP AG 2008

$

You are now able to: Describe the processes related to transportation

planning in ERP and SCM TP/VS Identify the ERP documents that are related to

transportation planning

SAP AG SCM612 2-14

Exercises

Unit: Transportation Processes Overview

At the conclusion of this exercise, you will be able to:

Describe the Transportation Management System functions. List the documents that are used in the TMS components. Outline the functions provided by the APO TP/VS planning component.

The transportation function in a business can be divided into two fundamental steps: Planning and Execution. In an ECC (ERP) and APO environment the planning step is carried out in APO and the execution step is performed in the ECC (ERP) system. To perform these steps it is important to understand the functions provided in each system.

1-1 Select the process(es) that are not part of the Logistics Execution (LE) component of ECC: a Transportation process b Internal warehouse process c Material Requirements Planning (MRP) d Goods issue process e Goods receipt process f Production Planning process

1-2 _______________________ shipments are an integral part of the process chain in Procurement and are created from ______________________________________ documents.

1-3 _______________________ shipments are created from ____________________ delivery documents that are generated from sales orders.

1-4 True or False. Delivery documents must be created before shipment documents can be created.

1-5 True or False. Shipment costing is required for each shipment document.

SAP AG SCM612 2-15

1-6 ECC transportation and shipment cost processing includes: a _____________________________________________________

b _____________________________________________________ c _____________________________________________________

1-7 True or False. The goal of the transportation planning process is to optimize the inbound and outbound transportation demand between the plant/DC and other locations such as customers, suppliers and other plants/DCs.

1-8 Which of the following criteria does the TP/VS Optimizer take into account during transportation planning: a Shipment fixed costs b Cost minimization of distance c Order consolidation d Loading and unloading time e Goods issue date f Costs for non-delivery g Distance in the delivery route code

1-9 During Transportation Service Provider (TSP) Selection, TP/VS can select TSPs based on the following: a Vehicle capacities (weight, volume, number of pallets,..) b Availability and compatibility of products c Contract terms d Priority of TSP e Business share f TSP quality / service performance rating g Costs

1-10 True or False. Sales order and Purchase order demand must be used for APO TP/VS planning of outbound and inbound shipments, respectively.

1-11 The transfer of planned deliveries and shipments from TP/VS to the SAP ERP system can be triggered by the ________________ function.

SAP AG SCM612 2-16

Solutions

Unit: Transportation Processes Overview

1-1 Select the process (es) that are not part of the Logistics Execution (LE) component of ECC: Material Requirements Planning (MRP Production Planning process)

1-2 Inbound shipments are an integral part of the process chain in Procurement and are created from Inbound Delivery documents.

1-3 Outbo und shipments are created from Outbound delivery documents that are generated from sales orders.

1-4 True or False. Delivery documents must be created before shipment documents can be created.

1-5 False. Shipment costing is required for each shipment document.

1-6 ECC transportation and shipment cost processing includes: a Transportation processing b Shipment cost calculation c Shipment cost settlement

1-7 True. The goal of the transportation planning process is to optimize the inbound and outbound transportation demand between the plant/DC and other locations such as customers, suppliers and other plants/DCs.

SAP AG SCM612 2-17

1-8 Which of the following criteria does the TP/VS Optimizer take into account during transportation planning: Shipment fixed costs Cost minimization of distance Order consolidation Loading and unloading time Costs for non-delivery

1-9 During Transportation Service Provider (TSP) Selection, TP/VS can select TSPs based on the following: a Vehicle capacities (weight, volume, number of pallets, ...) b Availability and compatibility of products c Priority of TSP d Business share e Costs

1-10 False. Sales order and Purchase order demand must be used for APO TP/VS planning of outbound and inbound shipments, respectively.

1-11 The transfer of planned deliveries and shipments from TP/VS to the SAP ERP system can be triggered by the GOTO function.

SAP AG SCM612 3-1

SAP AG 2008

Contents: Organizational Units in Transportation

Shipment document structure and control

Basic ERP to TP/VS interface settings

SAP AG SCM612 3-2

SAP AG 2008

At the conclusion of this unit, you will be able to: Explain the organizational units related to ERP

transportation Describe the structure of the shipment document

and its functions Identify and locate important information in the

shipment document Make the basic customizing and master data

settings to interface an ERP System with an APO TP/VS system

SAP AG SCM612 3-3

SAP AG 2008

The computer manufacturer will utilize the APO TP/VS component to plan shipments for goods to be received from suppliers and to be shipped to its customers.

Although the planning function will be done using TP/VS, the execution of the shipments will be made using the ERP transportation application.

The primary document used in these processes is the shipment document - so project team members have to understand its structure, functions and the information it contains.

SAP AG SCM612 3-4

SAP AG 2008

Lesson 3: Basic ERP to TP/VS interface Settings

ERP Organizational Units, Shipments and Integration

Lesson 1: Organizational Units in Transportation

Lesson 2: Shipment Document Structure and Control

SAP AG SCM612 3-5

SAP AG 2008

At the conclusion of this topic, you will be able to: Name the organizational units that are used in ERP

transportation processing and execution

SAP AG SCM612 3-6

SAP AG 2008

!

Various organizational data play an important role in the transportation planning and execution processes. It is important that the implementation team understand the role that each organizational unit plays in the transportation processes.

SAP AG SCM612 3-7

SAP AG 2008

Dresden

Reflects the location or the group of people that is responsible for carrying out the shipping activities.

Each delivery is processed by a single shipping point.

A shipping point is assigned to one or more plants.

A shipping point can be further sub-divided into loading points.

Determination of shipping point is via Shipping Condition (customer), Loading group (MM) and plant.

The shipping point is the part of the company responsible for the type of shipping, the necessary shipping materials and the means of transport.

The most important organizational element for shipping is the shipping point. You can define a user-specific default value for the shipping point in the user parameter VST.

SAP AG SCM612 3-8

SAP AG 2008

Transportationplanning points

1010Hamburg

Internationalshipment by

sea

1011Hamburg

Railshipments

1200Dresden

TruckShipments

Planning and processingshipments

Company code

The transportation planning point is the central point within the company that plans, processes, and monitors shipments. It can be a location or a group of people responsible for processing.

Each shipment is created and processed by a single transportation planning point. You can freely define the transportation planning points to meet your corporate requirements, for

example, in terms of the location or the mode of transport. The transportation planning point is defined for a specific company code in Customizing. This

assignment of the planning point to the company code is important for shipment cost calculation and settlement.

SAP AG SCM612 3-9

SAP AG 2008

Strabourg

Frankfurt

Nuremberg

Munich

Praha

Cologne

Trade center

Vienna

Border

Strasbourg

Frankfurt

Nuremberg

Munich

Prague

Route

Stage

Route

Stage

Cologne

Trade center

Vienna

Border

"#

A route is the journey to be covered between a departure point and a destination and is represented by the route code.

A route can be defined in great detail and consist of one or more individual stages, but it can also be a general description or even simply a destination area.

Like a shipment stage, a stage can be a leg, a load transfer point, or a border crossing point. Example:

The above route consists of 5 stages - 3 legs, 1 load transfer point, and 1 border crossing point. The route code is determined for each line item in a sales order and is copied into the header of the

outbound delivery document(s) created from the sales order. Inbound delivery documents do not require a route code but one may be entered manually. The route code is not used by APO TP/VS because TP/VS determine the route stages based on the

planning criteria associated with transportation lanes. Routes in ERP are only required to identify the transportation documents as relevant for shipment.

Multimode APO transports or APO transports with transshipment points are created with several shipment stages in ERP. In ERP they are identified as 'generated manually'.

A transfer of the routes from ERP to APO does not occur. Currently a report or something similar is not available.

SAP AG SCM612 3-10

SAP AG 2008

Factorycalendar

Shipping type

Transportationplanninglead time

Travel duration

Transit time

Transportationrelevance

Distance

Description

Service agent

RouteRoute

#

You may define routes in Customizing or in LE master data maintenance. A route code can contain a number of fields of information that are important to the shipment, for

example, distance, transportation lead time, travel duration, shipping type, service agent. When TP/VS is used for transportation planning, it will determine the route itinerary; therefore, stages

are not necessary to be predefined for the route and should not be copied into the shipment document. You set transportation relevance for the route in Customizing for Transportation. The route must be

set for transportation relevance if it will be used in sales orders and deliveries to be planned in TP/VS.

SAP AG SCM612 3-11

SAP AG 2008

# $%

You set transportation relevance for the route in Customizing for Transportation.

The route must be set for transportation relevance if it will be used in sales orders and deliveries to be planned in TP/VS.

ERP IMG: Sales and Distribution Basic Functions Routes Define Routes Define Routes and Stages

The route code is not used by SCM TP/VS because TP/VS determines the route stages based on the planning criteria associated with transportation lanes. Routes in ERP are only required to identify the transportation documents as relevant for shipment. The Route code is copied to TP/VS and can be used as selection criteria for vehicle scheduling.

Multimode SCM transports or SCM transports with transshipment points are created with several shipment stages in ERP. In ERP they are identified as 'generated manually'.

A transfer of the routes from ERP to SCM does not occur. Currently a report or something similar is not available.

SAP AG SCM612 3-12

SAP AG 2008

&'

You should now be able to: Name the organizational units that are used in ERP

transportation processing and execution

SAP AG SCM612 3-13

SAP AG 2008

"(

Lesson 3: Basic ERP to TP/VS interface Settings

ERP Organizational Units, Shipments and Integration

Lesson 1: Organizational Units in Transportation

Lesson 2: Shipment Document Structure and Control

SAP AG SCM612 3-14

SAP AG 2008

At the conclusion of this topic, you will be able to: Define the structure of the shipment document Describe the role of the shipment type List the basic shipment types Identify key information fields in the shipment document Explain the ways a shipment document can be created

"

SAP AG SCM612 3-15

SAP AG 2008

"!

The shipment document is the central document in transportation planning and execution. It is important for the project team to understand its basic structure and data.

SAP AG SCM612 3-16

SAP AG 2008

")

Record planned and actual dates/status

information

Record shipmentcharacteristics

Determine shipment stages

Grouping of inbound or outbound deliveries in

shipments

Create output(EDI / documents)

04.06.12.06.

Shipment documentfunctions

Packing / loading

Service agentMod

e of tra

nspor

t

Plan Act.C

B

A

The shipment document is the central document that is used to model shipments in the ERP System. It contains all information necessary for organizing and carrying out a shipment.

The shipment document provides the following functions:

Combining inbound deliveries to form inbound shipments

Combining outbound deliveries to form outbound shipments

Assigning service agents, modes of transport, shipment types, and so on

Planning and monitoring deadlines

Specifying shipment stages

Cross-delivery packing and creation of shipping units

Creating output and shipping papers

Recording shipment-relevant texts

Recording partner information Using TP/VS, shipments are created by combining deliveries within APO. Also carriers and

transportation methods are assigned to the shipments. Then they are transferred to ERP. In ERP they contain the data which are maintained in APO.

SAP AG SCM612 3-17

SAP AG 2008

#"

00001234 Nordspeed 1000 18,586 0

0080004903 1200 8,386

0080004879 1000 3,200

0080004905 1000 7,000

TPPt: Wt/kgService agentShipments and deliveries ShPt

Shipment header:General data for the entire shipment

Items:Inbound or outbound deliveries in the shipment

The shipment document contains general data that applies to the whole document, such as shipment type, transportation planning point, route, deadlines, and status information. This information is displayed in the shipment header.

Since the shipment is a collection of inbound or outbound deliveries that are shipped together, the items of the shipment correspond exactly to the inbound deliveries in the case of inbound shipments, and to the outbound deliveries in the case of outbound shipments.

SAP AG SCM612 3-18

SAP AG 2008

Shipment type

Leg indicator

Planning Profile

Split profile

Copying rule

Number assignment

Shipping type

Completion type

Texts

Output

Leg determination / stage selection

Update change documents?

'

The shipment type controls elements in the shipment document and therefore represents a particular processing type for a shipment.

Shipment type settings include:

The leg determination type (automatic leg determination, for example) The completion type (loaded outbound shipment, inbound shipment, for example) The processing control (collective shipment using one mode of transport, for example) The service level (general cargo, grouped load, for example) The shipping type (truck, train, mail, for example) The leg indicator (preliminary leg, subsequent leg, direct leg, for example) Copying data from preceding documents (forwarding agent and route, if unique, for example) Output determination and text determination procedure

Default values for the shipment document (weight and volume unit, planning profile, for example) You can define your own shipment types to suit your own shipment requirements. Shipment types created for APO TP/VS use must not have leg determination enabled.

SAP AG SCM612 3-19

SAP AG 2008

Delivery type Delivery item category

Out. delivery LF X

Cash sale BV

Inb. delivery EL X

Standard item TAN X

Text item TATX

Inb. delivery ELN X

Route of the delivery

Route HH - F X

Route HH - M X

Northern route

Out. delivery LF

Transportation planning status = A

Route HH - F

The transportation relevance of the delivery type, the delivery item category, and the route in the delivery controls whether a shipment can be created or not.

So that a shipment can be created, the delivery type must be set as relevant for transportation. Similarly, at least one delivery item category in the delivery must be relevant for transportation. The outbound delivery must contain a route code that is relevant for transportation (does not apply to

inbound deliveries). A route is defined as the connection between a point of departure and a destination point with several possible points in between.

If all three (or two in the case of inbound deliveries) conditions are met, the delivery has transportation planning status A, which means that the delivery document is relevant for transportation.

You set transportation relevance in Customizing for Transportation.

SAP AG SCM612 3-20

SAP AG 2008

#(

Manually usingCreate

Shipment

Automatically in collective processingusing the worklist

Online B/ground

Using a transportation

planning system

Creating shipments

ERP

TP/VSWithout planning proposal

With planning proposal

The ERP System contains different ways of creating shipments: You can create shipments manually using the Create shipment function. You can select deliveries due

for shipping using different selection criteria and create the documents manually. You can also use a planning proposal. This is a pre-defined profile according to whose rules,

deliveries are automatically combined into shipments and completed with data. The system can also create shipments automatically. To do this, you use a collective processing run

that is executed online or in batch mode. The system creates one or more shipment documents according to different processing rules.

If the shipments are created and optimized by an external transportation planning system such as APO TP/VS, you can link to this system with an interface. In the ERP to APO environment this interface is called the Core Interface or CIF.

SAP AG SCM612 3-21

SAP AG 2008

Processing status of shipment

Status information in the shipment document header:

Overall status

PlannedCheck-inLoading startLoading endShipment completionShipment startShipment end

Check-in

CompletedCompleted

Not completed

Not completed

Not completed

Not completedNot completed

#

"

When the transportation activities such as planning, checking in, loading, and so on, are finished, you can set a status. As soon as the status is set, the activity is considered completed.

Thus you always know the current processing status of a shipment and can quickly provide information.

You can set the status by:

Choosing the corresponding pushbutton; the current date is adopted as the actual date.

Entering the actual date; the status is then set by the system. A traffic light symbol displays the overall status of the shipment.

Red: Planned status is set.

Yellow: Check-in / Loading Start / Loading End status is set

Green: Shipment completion / Shipment Start / Shipment End status is set Note: For shipment cost calculation, however, status Planned must be set as a minimum. Note: The planned status is automatically set if you transfer shipments from TP/VS to ERP.

SAP AG SCM612 3-22

SAP AG 2008

"&'

You should now be able to: Define the structure of the shipment document Describe the role of the shipment type List the basic shipment types Identify key information fields in the shipment document Explain the ways a shipment document can be created

SAP AG SCM612 3-23

SAP AG 2008

$%#

Lesson 3: Basic ERP to TP/VS interface Settings

ERP Organizational Units, Shipments and Integration

Lesson 1: Organizational Units in Transportation

Lesson 2: Shipment Document Structure and Control

SAP AG SCM612 3-24

SAP AG 2008

At the conclusion of this topic, you will be able to: Make the necessary customizing settings in the

ERP System to interface the ERP transportation application with the TP/VS component.

Create the necessary material master data in the ERP System for the TP/VS integration

$%#

SAP AG SCM612 3-25

SAP AG 2008

$%#!

To link the ERP system to the SCM TP/VS environment certain settings are required in the ERP system.

SAP AG SCM612 3-26

SAP AG 2008

(* "+

Customizing Activities

Transportation relevance of orders and deliveries Definition of Shipment Document Number Ranges Definition of Shipment Types Transportation Planning Point Determination Shipment Costing Settings related to TSP selection

Material Master Requirements

Check ATP-Category Create Packaging Materials needed in TP/VS Check Strategy Group

SAP AG SCM612 3-27

SAP AG 2008

Route

Delivery Type

Item Category

ERP: Transportation relevance of deliveries

ERP IMG: Logistics Execution Transportation Shipments Maintain Transportation Relevance

Only transport relevant deliveries can be assigned to shipments. For outbound deliveries route determination has to be maintained, because outbound deliveries without an assigned route are not transportation relevant. For Inbound deliveries, relevance is determined from the Item Category and Delivery Document Type.

SAP AG SCM612 3-28

SAP AG 2008

'

ERP IMG: Logistics Execution Transportation Basic Transportation Functions Routes Define Routes Define Shipping Types

The Shipping Type code can be assigned to Routes and they are assigned to Shipment Document Types.

They are used in the Transportation Planning Point Determination table to assign a Transportation Planning Point to a Shipment document that has been transferred from APO TP/VS to ERP.

The STPG (Shipping Type Procedure Group) code from this table is used to determine pricing procedures in shipment costing.

SAP AG SCM612 3-29

SAP AG 2008

",

ERP

SCM

External number range in ERP has to correspond withinternal number range in SCM.

ERP and SCM: Definition of Number Ranges must be consistent

ERP IMG: Logistics Execution Transportation Shipments Define Number Ranges for Shipments

SCM IMG: Advanced Planner and Optimizer (SCM) Transportation Planning/Vehicle Scheduling (TP/VS) Basic Settings Define Number Range for Temporary Shipments

SCM IMG: ... Define Number Range for Shipments

SAP AG SCM612 3-30

SAP AG 2008

'-

ERP: Definition of Shipment TypesExample for outbound shipments:

IMG: Logistics Execution Transportation Shipments Define Shipment Types Note: Maintain "Do not adopt stages" and "No legs to be determined"!

SAP AG SCM612 3-31

SAP AG 2008

# $%

Definition

Determination

ERP: Transportation Planning Point Determination:

ERP IMG: Enterprise Structure Definition Logistics Execution Maintain Transportation Planning Point

ERP IMG: Logistics Execution Transportation Interfaces Transportation Planning Point Determination

You must update the Transportation Planning Point determination table so that TP/VS can determine the Transportation Planning point to be assigned to the shipment documents that are created in TP/VS planning.

A default transportation planning point should also be maintained.

SAP AG SCM612 3-32

SAP AG 2008

.

/

Transportation Group An indicator that summarizes the characteristics of a material that are

relevant for transportation. Used for automatic route determination during sales order and delivery

creation. Each material is assigned to a transportation group. For example, a

transportation group can use characteristics such as "bulky goods" or "must be refrigerated."

Transportation Zone A Transportation Zone where the ship-to party is located and that is

used by the system as a factor for determining the route. Grouping of ship-from locations or ship-to locations from or to which

goods are delivered. In sales and distribution it represents the regional zone of the goods

recipient, in purchasing the regional zone of the supplier.

For example, transportation zones can be defined according to postal code areas. If a transportation zone is assigned to a customer e.g. the system automatically proposes a suitable

route by using the transportation zone of the goods recipient in combination with other information, such as the Countries of origin and destination, shipping conditions, transportation group.

SAP AG SCM612 3-33

SAP AG 2008

.# $%

ERP

SCM

Manual maintenance in both systems

The transportation Group is used to categorize materials according to their transportation requirements. Like materials in ERP, each APO Product is assigned to a Transportation Group code. A product attribute for grouping could be 'refrigerated transportation required' or 'dangerous goods'.

The Transportation Group codes in APO should match the R/3 Transportation Group codes. SCM IMG: Advanced Planning and Optimization Transportation Planning and Vehicle

Scheduling (TP/VS) Basic Settings Maintain Transportation Group ERP IMG: Logistics Execution Transportation Basic Transportation Functions

Routes Route Determination Define Transportation Groups The setup of the transportation groups in SCM is necessary for correct master data transfer.

SAP AG SCM612 3-34

SAP AG 2008

0 12

APO planned shipment can have a TOP HU automatically assigned, based on the Means of Transport used in APO

Usage of Handling Units is optional hence the following settings are optional. See the next slide for the necessary settings.

SAP AG SCM612 3-35

SAP AG 2008

3* ,# $%*

TP/VS

Create materials of material type "VERP" (naming should be the same as that used in the APO Transport Methods).

Note: In material master view "Sales: General/Plant Data" a packaging material type "means of transport" e.g. like Trucks" has to be maintained. See Packaging Material Types in ERP IMG: Logistics GeneralHandling Unit ManagementBasicsDefine Packaging Material Types

TP/VS: Mapping Table for Vehicles IMG: Advanced Planning and Optimization Transportation Planning and Vehicle Scheduling

(TP/VS) Interfaces Maintain Mapping Table for Vehicles Note: The APO Mapping Table for Vehicles is case sensitive. Maintain the column for external vehicle

description only by using upper cases.

SAP AG SCM612 3-36

SAP AG 2008

**")(3

SAP-Menu: Logistics Materials Management Material Master Material Change Immediately

ATP-Category in Material Master View: MRP 3: See Availability Check field Checking Group for Availability Check: 02 (Individual rqmt) This field must be set for individual requirements for sales requirement data to be transferred

to APO.

Strategy Group There are four ERP strategy groups that are not supported in APO:

11 Gross requirements

59 Phantom Assembly

52 Future Use

62 Future Use

In addition, some strategy groups are configured such that requirements are not transferred to APO. If requirements are not transferred to APO transportation planning will not occur for the material.

SAP AG SCM612 3-37

SAP AG 2008

(

1. Assign Shipment Types to Cost Types.2. Update Tariff Zone Determination to include new

Transportation Planning Points.3. Create Shipment Costing Pricing Procedure and update

Pricing Procedure Determination.4. Update Purchasing Data determination table in

Shipment Costing.5. Update Shipping Point Determination.6. Enter Freight Rates in ERP Transportation Master Data.

If External/Actual freight rates are going to be used in Transportation Service Provider selection, the following configuration and master data settings must be made:

If actual freight rates are going to be used to determine Transportation Service Providers in TP/VS, shipment costing related configuration settings must be made in the ERP system.

These settings must be made and the corresponding freight rates must be entered because TP/VS does not maintain any freight costing data or configuration. When TSPs are to be selected based on external/actual freight rates, TP/VS send a request to ERP to perform a simulated shipment costing calculation for the freight units. ERP will create a simulated shipment document and a corresponding shipment cost document that contains the values computed based on the freight rating and shipment costing pricing procedure settings.

SAP AG SCM612 3-38

SAP AG 2008

$%#&'

You should now be able to: Make the necessary customizing settings in the ERP

System to interface the ERP transportation application with the TP/VS component.

Create the necessary material master data in the ERP System for the TP/VS integration

SAP AG SCM612 3-39

SAP AG 2008

0'

You are now able to: Explain the organizational units related to ERP

transportation Describe the structure of the shipment document and

its functions Identify and locate important information in the

shipment document Make the necessary setting to interface an ERP System

with a TP/VS system

SAP AG SCM612 3-40

Exercises

Unit: ERP Organizational Units, Shipments and Integration Topic: Transportation Planning Point

At the conclusion of this exercise, you will be able to:

Understand the organizational units relevant for transportation processing in Customizing

Create a Transportation Planning Point to be used for shipment documents created by APO TP/VS planning.

As an employee in transportation planning and processing, you are also a member of the APO implementation team in the transportation area. Before you begin setting up the system and trying out its shipment processes, you familiarize yourself with ERP transportation processing in general. You examine the structure of the shipment documents and identify what information they contain and create two new shipment types to facilitate the creation of ERP shipment documents from planned shipments in TP/VS. Since you also need to familiarize yourself with the organizational structures, you learn how they are defined and assigned. You will create a new Transportation Planning Point to be used when creating ERP shipment documents from the APO TP/VS component.

1-1 True or false? 1-1-1 A company code is an independent, accounting unit. 1-1-2 Each plant has exactly one shipping point. 1-1-3 Shipments are processed at a transportation planning point. 1-1-4 Each transportation planning point must be assigned to a plant. 1-1-5 Each transportation planning point must be assigned to a warehouse number.

1-2 Which transportation planning points are defined for company code 1000? ____________________________________________________________

Go to the address screen for transportation planning point 1000. In which street is it located? ______________________________________________________

SAP AG SCM612 3-41

1-3 Create a new Transportation Planning Point to be used for shipments created from the APO TP/VS component. Identify the Transportation Planning Point as AP##. Assign it to Company Code 1000. Description: TP/VS Group ## In the Edit Address fields:

Name: APO TP/VS GR ## Search Term: AP## Country: DE Language: English

1-4 You must create and entry in the Assign Goods Receiving Points for Inbound Deliveries table in Customizing to enable the System to create Inbound Delivery documents from TP/VS planning of purchasing documents. APO TP/VS will be used to plan inbound shipments to your Hamburg plant, 10##. Update the customizing table with the following entry:

Plant St. Loc Shipping Point Sequence Number 10## 0001 Z0## 1

1-5 When shipment documents are created from the APO TP/VS system, the Transportation Planning Point must be determined for each shipment document. In this step you will update the interface table that is used to determine the Transportation Planning Point. Shipments will be planned for Shipping Point X0## Dresden and Z0## Hamburg. Create the following entries in the 'Determination of Transportation Planning Point table. Shipping Point Shipping Type TrspPlanPt X0## Blank AP## X0## 01 AP## Z0## Blank AP## Z0## 01 AP##

SAP AG SCM612 3-42

Exercises

Unit: ERP Organizational Units, Shipments and Integration Topic: Shipment Document Type

At the conclusion of this exercise, you will be able to:

Create Shipment document types used for APO planning

Shipment document types must exist for shipment documents created in APO TP/VS planning. You will create a shipment document type for inbound shipments created in TP/VS and a shipment document type for outbound shipment documents created in TP/VS planning. In addition, you will update the Transportation Planning point interface table for the ERP to APO TP/VS environment.

2-1 An outbound shipment for your group has been created in the system as an example. Display the outbound shipment. Search for the document using the F4 help. Use the External ID 1 field as a search term. External ID 1: GR##-2. (Note: This search is case-sensitive, enter the External Identification EXACTLY as shown.) 2-1-1 Which outbound deliveries does this shipment contain?

_____________________________________________________

2-1-2 Find the following information in the shipment document: Shipment type: ________________________________________ Ship-to address: _______________________________________ Shipping point: _________________________________________ Shipment weight: _____________________________________

2-1-3 Display the corresponding document flow. What order initiated this document flow? What is its status? ______________________________________________________

2-1-4 Check whether the shipment costs have already been calculated for this shipment. To do this, check the overall status of shipment cost calculation in the shipment header. Overall status of shipment cost calculation: ________________________________

SAP AG SCM612 3-43

Number of the shipment cost document: ________________________________

2-2 To facilitate creation of inbound shipment documents in the ECC system corresponding to planned inbound shipments in APO TP/VS, create a new shipment type, AI##, using existing Shipment Type 0010 as a template. In the new shipment type you need to make the following settings:

Field Name Data Shipment Type Description APO Inbound GR## No. Range Ext. 02 Adopt Route 2-Do Not Adopt stages Determine Legs blank (No legs to be determined) Pick Check* B No Check regarding full picking Weight Unit KG (Kilograms) Volume Unit M3 (Cubic Meters) Copy Routine 11 (Route/Deadlines)

* This setting is for the class only, it is not required to be set this way for TP/VS. Do not change any other settings.

2-3 To enable creation of outbound shipment documents in the ECC system corresponding to planned outbound shipments in APO TP/VS, create a new shipment type, AO##, using existing Shipment Type 0002 as a template. In the new shipment type you need to make the following settings:

Field Name Data Shipment Type Description APO Outbound GR## No. Range Ext. 02 Adopt Route 2-Do Not Adopt stages Determine Legs blank (No legs to be determined) Pick Check* B No check regarding picking SplProfBefPlng blank SplProfAfterPlg blanl Weight Unit KG (Kilograms) Volume Unit M3 (Cubic Meters) Planning prof. blank Copy Routine 11 (Route/Deadlines)

* This setting is for the class only; it is not required to be set this way for TP/VS. Do not change any other settings.

SAP AG SCM612 3-44

Exercises

Unit: ERP Organizational Units, Shipments and Integration Topic: Shipment Costing and TP/VS-related customizing

At the conclusion of this exercise, you will be able to:

Make the customizing settings necessary to assign your APO shipment types to a shipment cost type.

Make the relevant customizing settings necessary to perform shipment costing for shipments planned in APO TP/VS and provide the ability to perform Transportation Service Provider (TSP) selection in TP/VS using freight rates established in the ERP System.

Set up Pricing Procedure determination in Shipment Costing.

The ability to perform shipment costing for both inbound and outbound shipments and to provide the ability to influence TSP selection based on actual freight rates are significant benefits of using the ERP Transportation application combined with the APO TP/VS component. As a member of the TP/VS project team you will need make the required customizing settings in the ERP System to facilitate these functions.

3-1 Assign your two new Shipment Types AI## and AO## to Shipment Cost Type 0001 in ECC Customizing. 3-1-1 Set the Shipment Header, Leg, Load Transfer Point and Border Crossing Cost

Types as Relevant for shipment costs for each assignment.

3-2 Because you will be using tariff zone codes in your freight rates for shipment costing, you must update the tariff zone determination table to include your new Transportation Planning Point for each of your TSPs. You have three TSPs that have rate established for shipment costing and TSP determination in TP/VS: 1058, 1925 and 1930. These TSPs are also used for shipments created for Transportation Planning Point 1000, so you can "copy as" the existing entries to your Transportation Planning Point AP##. You should also copy all sub-items in the entry.

3-3 Update the shipment costing pricing procedure determination table to reflect your new Transportation Planning Point. Use Transportation Planning Point 1000 as a reference for the copy as process.

SAP AG SCM612 3-45

3-4 Make the required setting in the Purchasing Data determination table for your new Transportation Planning Point, AP##. Use the same purchasing organizational data as Transportation Planning Point 1000.

3-5 To satisfy a requirement for TP/VS Transportation Service Provider Selection when external costs are used as a criteria for selection, make sure an entry exists in the LES Shipping Point Determination table for your plants and their corresponding shipping points. Change the table entries corresponding to your group number (##) to appear as follows:

Shipping Condition Loading Group Plant Shipping Point(PrShP) 10## Z0## 12## X0##

SAP AG SCM612 3-46

Exercises

Unit: ERP Organizational Units, Shipments and Integration Topic: Stock Transport-related customizing

At the conclusion of this exercise, you will be able to:

Make the required, basic customizing settings required for stock transport processing.

When a new plant (s) is/are established in ERP, there are some fundamental settings required to facilitate the processing of stock transports both inter- and intra-company. These settings are independent of TP/VS. You must make these settings before stock transport orders are created in the ERP System.

4-1 To complete the required customizing settings, perform the following steps: 4-1-1 Copy the customer master record (1187) representing Plant 1000, to a new

customer master record, T-S090##. You must copy all views (General, Company and Sales Area) to your new customer master.

4-1-2 Copy the customer master record (22000) representing Plant 2200, to a new customer master record, T-S200##. You must copy all views (General, Company and Sales Area) to your new customer master.

4-1-3 Update the vendor master record for vendor T-S100## that represents plant 12## for intercompany stock transport orders. The Plant code for plant 12## must be entered in the Additional Purchasing Data view.

4-1-4 Update the Plant table in Stock Transport customizing with your new customer master for Plant 12##. Also, update the Plant table for Plant 22## with the customer account number you just created for the plant, T-S200##.

4-1-5 Check and make any required assignments in the Assign delivery type/checking table in Stock Transport customizing. The following assignments must exist: Type: NB SPlt: 12## DlvTy: NLCC C: B UB 10## NL RP

4-1-6 Check and make any required assignments in the Purchasing document type table in the Stock Transport customizing area. The table must include the following combinations of allowed stock transports and corresponding Purchase Order Document Types: 10## to 12## UB No one-step processing 12## to 22## NB No one-step processing

SAP AG SCM612 3-47

4-1-7 Verify and make any necessary changes to the Transportation Relevancy tables. In this step you will make sure that delivery document types NL and NLCC are set as relevant for transportation processing. In addition, you must verify that all relevant item categories for these document types are set as "relevant" for transportation processing. Unless these objects are set as "relevant" for transportation processing you will not get shipment documents created when TP/VS planned shipments are "published".

SAP AG SCM612 3-48

Exercises

Unit: ERP Organizational Units, Shipments and Integration Topic: Settings Necessary for Integration

At the conclusion of this exercise, you will be able to:

Create the Packaging Materials needed for APO TP/VS planning and integration with the ERP System.

When APO TP/VS creates shipment documents and they are subsequently transferred to the ERP System for execution, the Transportation Methods codes from TP/VS are translated into corresponding ERP packaging materials in the shipment document. These packaging materials must exist in the ERP Material Master.

5-1 You can have a handling unit representing the shipment created automatically in the shipments that are published to the ERP system by TP/VS. To facilitate this you must have the packaging materials representing the means of transport created in the ERP material master. You have decided to do this for your implementation of TP/VS. Create three packaging material master records, based on information in the following table:

Material Number Copy from material Description FTL-## TRUCK-04 FTL Group ## LTL-## TRUCK-05 LTL Group ## SHIP-## TM-110 SHIP Group ##

These materials should have Material Type of VERP and Industry Sector of Mechanical Engineering. The following views should be created: Basic Data 1, Sales: Sales Org. Data 1, Sales: Sales Org. Data 2, Sales: General/Plant Data and Accounting 1. In the Organizational Data enter only your Plant 12## but "copy from" Plant 1200 of the reference material. All other data fields should remain the same as the reference material.

SAP AG SCM612 3-49

Solutions

Unit: ERP Organizational Units, Shipments and Integration Topic: Transportation Planning Point

1-1 True or false? 1-1-1 True 1-1-2 False A plant can have more than one shipping point. 1-1-3 True 1-1-4 False A transportation planning point is only defined for a particular company

code and is not linked to other organizational units. 1-1-5 False A transportation planning point is only defined for a particular company

code and is not linked to other organizational units.

1-2 Which transportation planning points are defined for company code 1000? _ _________________________________________________________

Choose ERP IMG: Enterprise Structure Definition Logistics Execution Maintain Transportation Planning Point Note the transportation planning points that have a company code of 1000. 0001, 0007, 1000, 1010, 1011, 1200 Go to the address screen for transportation planning point 1000. In which street is it located? ______________________________________________________

Select Transportation Planning Point 1000.

Choose Goto Address Note the Street/House number: Altersdorferstr. 13

1-3 Create a new Transportation Planning Point to be used for shipments created from the APO TP/VS component. Identify the Transportation Planning Point as AP##. Assign it to Company Code 1000. Description: TP/VS Group ## Go to ERP IMG: Enterprise Structure Definition Logistics Execution Maintain Transportation Planning Point Select the New Entries button

SAP AG SCM612 3-50

Enter the data from the table below

Choose Enter . Enter the Address data:

Name TP/VS GR ## Search Term AP## Country DE Language Language of the Course

Choose Copy .

Choose Save .

Select Exit .

1-4 You must create and entry in the Assign Goods Receiving Points for Inbound Deliveries table in Customizing to enable the System to create Inbound Delivery documents from TP/VS planning of purchasing documents. APO TP/VS will be used to plan inbound shipments to your Hamburg plant, 10##. Update the customizing table with the following entry: Plant St. Loc. Shipping Point Sequence Number 10## 0001 Z0## 1 Go to ERP IMG: Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point Determination Assign Goods Receiving Points for Inbound Deliveries Select the New entries button. Enter the following data: Plant Stor. Loc. Shipping Point Sequence Number 10## 0001 Z0## 1

Choose Save .

Select Exit .

TPPt Description CoCd AP## TP/VS Group ## 1000

SAP AG SCM612 3-51

1-5 When shipment documents are created from the APO TP/VS system, the Transportation Planning Point must be determined for each shipment document. In this step you will update the interface table that is used to determine the Transportation Planning Point. Shipments will be planned for Shipping Point X0## Dresden and Z0## Hamburg. Create the following entries in the 'Determination of Transportation Planning Point table. Shipping Point Shipping Type TrspPlanPt X0## Blank AP## X0## 01 AP## Z0## Blank AP## Z0## 01 AP##

Go to ERP IMG: Logistics Execution Transportation Interfaces Transportation Planning Point Determination

Select the New entries button. Make the following entries:

Shipping Pt. Ship. type TrspPlanPt X0## AP## X0## 01 AP## Z0## AP## Z0## 01 AP##

Choose Save .

Select Exit .

SAP AG SCM612 3-52

Solutions

Unit: ERP Organizational Units, Shipments and Integration Topic: Shipment Document Type

2-1 An outbound shipment for your group has been created in the system as an example. Display the outbound shipment. Search for the document using the F4 help. Use the External ID 1 field as a search term. External ID 1: GR##-2. (Note: This search is case-sensitive, enter the External Identification EXACTLY as shown.) Go to ERP SAP Menu: Logistics Logistics Execution Transportation Transportation Planning Display Press F4 key. Enter GR##-2 in the External ID 1 field.

Choose Execute . Select the line with your shipment. 2-1-1 Which outbound deliveries does this shipment contain?

_____________________________________________________

Choose the Shipments and deliveries icon On the Shipments and deliveries overview screen: One outbound delivery is involved in this shipment. Record the delivery document number

2-1-2 Find the following information in the shipment document: Ship-to address: _____________________________________________ Shipping point: _____________________________________________ Shipment weight: _____________________________________________ Shipment type: _____________________________________________ From the Shipments and Deliveries screen note the Ship-to Address on the line with the delivery document number. From the Shipments and Deliveries screen note the Shipping point on the line with the delivery document number. From the Shipments and Deliveries screen note the Shipment weight from the line with the delivery document number.

Choose the Overview of current shipment icon . Note the Shipment type under the Processing tab.

SAP AG SCM612 3-53

2-1-3 Display the corresponding document flow. What order initiated this document flow? What is its status?______________________________________________________

Choose Environment Document flow Note the StandardOrder number: Document numbers will vary Note the the Status of the order is completed.

Choose Back 2-1-4 Check whether the shipment costs have already been calculated for this

shipment. To do this, check the overall status of shipment cost calculation in the shipment header. Overall status of shipment cost calculation: ________________________________

Number of the shipment cost document: ________________________________

Select the Shipment cst cal tab Note the Overall status of shipment cost calculation: Completely processed Choose the Shpmnt cost doc button. Note the Shipmt Cost No.

2-2 To facilitate creation of inbound shipment documents in the ECC system corresponding to planned inbound shipments in APO TP/VS, create a new shipment type, AI##, using existing Shipment Type 0010 as a template. In the new shipment type you need to make the following settings:

Field Name Data Shipment Type Description APO Inbound GR## No. Range Ext. 02 Adopt Route 2-Do Not Adopt stages Determine Legs blank (No legs to be determined) Pick Check* B No Check regarding full picking Weight Unit KG (Kilograms) Volume Unit M3 (Cubic Meters) Copy Routine 11 (Route/Deadlines)

* This setting is for the class only, it is not required to be set this way for TP/VS. Do not change any other settings.

SAP AG SCM612 3-54

Go to ERP IMG: Logistics Execution Transportation Shipments Define Shipment Types Select Shipment Type 0010

Choose Copy As . Overtype the Shipment Type with AI##. Enter the remainder of the settings from the table above.

Choose Enter .

Choose Save .

2-3 To enable creation of outbound shipment documents in the ECC system corresponding to planned outbound shipments in APO TP/VS, create a new shipment type, AO##, using existing Shipment Type 0002 as a template. In the new shipment type you need to make the following settings: Field Name Data Shipment Type Description APO Outbound GR## No. Range Ext. 02 Adopt Route 2-Do Not Adopt stages Determine Legs blank (No legs to be determined) Pick Check* B No check regarding picking SplProfBefPlng blank SplProfAfterPlg blank Weight Unit KG (Kilograms) Volume Unit M3 (Cubic Meters) Planning prof. blank Copy Routine 11 (Route/Deadlines)

* This setting is for the class only, it is not required to be set this way for TP/VS. Do not change any other settings. Go to ERP IMG: Logistics Execution Transportation Shipments Define Shipment Types Select Shipment Type 0002.

Choose Copy As . Overtype the Shipment Type with AO## and the remainder of the settings from the table above.

Choose Enter .

Choose Save .

SAP AG SCM612 3-55

Solutions

Unit: ERP Organizational Units, Shipments and Integration Topic: Shipment Costing and TP/VS-Related Customizing

3-1 Assign your two new Shipment Types AI## and AO## to Shipment Cost Type 0001 in ECC Customizing. 3-1-1 Set the Shipment Header, Leg, Load Transfer Point and Border Crossing Cost

Types as Relevant for shipment costs for each assignment.

Go to ERP IMG: Logistics ExecutionTransportationShipment CostsShipment Cost Document Shipment Cost Relevance and Default for Shipment Cost Type Find your shipment types, AI## and AO## and enter 0001 in the SCTy column.

Choose Save . Under Dialog Structure, select: Define shipment cost relevance fo shipment type. For your shipment types, select the Header, Leg, Load Transfer Point, and Border Crossing boxes.

Choose Save.

Choose Exit

3-2 Because you will be using tariff zone codes in your freight rates for shipment costing, you must update the tariff zone determination table to include your new Transportation Planning Point for each of your TSPs. You have three TSPs that have rates established for shipment costing and TSP determination in TP/VS: 1058, 1925 and 1930. These TSPs are also used for shipments created for Transportation Planning Point 1000, so you can "copy as" the existing entries to your Transportation Planning Point AP##. You should also copy all sub-items in the entry. Go to ERP IMG: Logistics Execution Transportation Shipment Costs Basic Functions Define and Assign Tariff Zones Under the Dialog Structure select the line: Define organizational key for tariff zone assigs Select the records in TPPt 1000 for Service Agents: 1058, 1925 and 1930.

Select Copy as .

SAP AG SCM612 3-56

Type your Transportation Planning Point, AP##, over the TPPt 1000 and select Enter. When the Specify object to be copied dialogs appear, select Copy all, and continue for the information boxes. Note: You will get the message three times.

Choose Save .

Choose Exit .

3-3 Update the shipment costing pricing procedure determination table to reflect your new Transportation Planning Point. Use Transportation Planning Point 1000 as a reference for the copy as process.

Go to ERP IMG: Logistics Execution Transportation Shipment Costs Pricing Pricing Control Define And Assign Pricing Procedures Define pricing procedure determination for shipment costs You will create the pricing procedure determination data for your Transportation Planning Point by copying the records from Transportation Planning Point 1000 to the clipboard, then paste-ing the records in your Transportation Planning Point, Select Transportation Planning Point 1000.

Select the Determine pricing procedure path under the Dialog Structure. After the table is displayed, press Cntl + Y (Mark). The cursor should turn into the cross-hair symbol. Place the cross-hair in the upper left-hand corner of the first record, drag the cursor across the first record and then at the end of the first record, at the vertical scroll bar, drag the cursor down the screen to the line below the last determination record (the line with It.Det.Grp of 0006). Release the left mouse button and press Cntl + C to copy the block to the clipboard. Select Transportation Planning Point under the Dialog Structure to return to the list of Transportation Planning Points. Select your Transporation Planning Point from this table.

Select the Determine pricing procedure path under the Dialog Structure. Select New Entries. Place the cursor in the It.Det.Grp. field on the first line of the table. Press Cntl + V to copy the clipboard to the records in your Transportation Planning Point.

Select Save .

Choose Exit

Choose Cancel

SAP AG SCM612 3-57

3-4 Make the required setting in the Purchasing Data determination table for your new Transportation Planning Point, AP##. Use the same purchasing organizational data as Transportation Planning Point 1000. Navigate to ERP IMG: Logistics Execution Transportation Shipment Costs Settlement Assign Purchasing Data Select the line with TPPt 1000 and SCTy 0001

Choose Copy As . Enter your TPPt. AP##.

Select Enter .

Select Save .

Choose Exit .

3-5 To satisfy a requirement for TP/VS Transportation Service Provider Selection when external costs are used as a criteria for selection, make sure an entry exists in the LES Shipping Point Determination table for your plants and their corresponding shipping points. Change the table entries corresponding to your group number (##) to appear as follows:

Shipping Condition Loading Group Plant Shipping Point(PrShP) 10## Z0## 12## X0##

Navigate to ERP IMG: Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point Determination Assign Shipping Points Find your plants in the Shipping Point Determination table that match the entries in the exercise. Change the default shipping point to match your shipping points in the exercise.

Choose Enter

Choose Save .

Choose Exit .

SAP AG SCM612 3-58

Solutions

Unit: ERP Organizational Units, Shipments and Integration Topic: Stock Transport-related customizing

4-1 Perform the following steps to customize the Stock Transport environment: 4-1-1 Copy the customer master record (1187) representing Plant 1000, to a new customer

master record, T-S090##. You must copy all views (General, Company and Sales Area) to your new customer master. Navigate to ERP SAP Menu: Logistics Logistics Execution Master Data Partner Customer Create Total Enter the data from the following table in the Customer Create Initial Screen:

Customer Account Group 0001 Sold to Party Customer T-S090## Company Code 1000 Sales Organization 1000 Distribution Channel 12 Division 00 Reference Customer 1187 Refernce Company 1000 Reference Sales Organization 1000 Reference Distribution Channel 12 Reference Division 00

Choose Enter . Enter the General Data from the table below: Name Plant 10## Search term Plant 10## Postal code 01069 City Hamburg Transportation zone D000000000 Language Select the language of the course

SAP AG SCM612 3-59

Select the Control data tab, and enter the data from the table below:

Trading partner 1000 VAT Registration DE123456789

Choose Enter . Select Company code data button. Select Sales area data button. Select the Shipping tab. Enter the data from the table below:

Shipping Condition Enter the sum of 50 plus your group number ## Select the Billing tab. Enter the data from the following table:

Tax classification 0 non taxable for country DE

Choose Save .

Choose Cancel . 4-1-2 Copy the customer master record (22000) representing Plant 2200, to a new customer

master record, T-S200##. You must copy all views (General, Company and Sales Area) to your new customer master. Navigate to ERP SAP Menu: Logistics Logistics Execution Master Data Partner Customer Create Total Enter the data from the following table in the Customer Create Initial Screen.:

Customer Account Group 0001 Sold to Party Customer T-S200## Company Code 1000 Sales Organization 1000 Distribution Channel 12 Division 00 Reference Customer 22000 Refernce Company 1000 Reference Sales Organization 1000 Reference Distribution Channel

12

Reference Division 00

SAP AG SCM612 3-60

Choose Enter . Enter the General Data from the table below:

Name Plant 22## Search term Plant 22## Postal code 75015 City Paris Region 75 Transportation zone

F000010000

Language Select the language of the course Select the Control data tab, and enter the data from the table below:

Trading partner 2200 VAT Registration FR93341612695

Choose Enter . Select Company code data button. Select Sales area data button. Select the Shipping tab. Enter the data from the table below:

Shipping Condition Enter the sum of 50 plus your group number ## Select the Billing tab. Enter the data from the following table:

Tax classification 0 non taxable for country DE

Choose Save .

Choose Cancel .

4-1-3 Update the vendor master record for vendor T-S100## that represents plant 12## for intercompany stock transport orders. The Plant code for plant 12## must be entered in the Additional Purchasing Data view. Navigate to ERP SAP Menu: Logistics Logistics Execution Master Data Partner Vendor Change Enter the following data field from the table below: Vendor T-S100## Company Code 2200 Purchasing Organization 2200

SAP AG SCM612 3-61

Select: Purchasing Data

Choose Enter . Choose Extras Add. purchasing data Enter 12## in the Plant field Choose Save .

4-1-4 Update the Plant table in Stock Transport customizing with your new customer master for Plant 10##. Also, update the Plant table for Plant 22## with the customer account number you just created for the plant, T-S200##. ERP IMG: Materials Management Purchasing Purchase Order Set up Stock Transport Order Define Shipping Data for Plants Select Plant 10##.

Select Details . Enter your customer: T-S090## in the Customer no. plant field. Choose Save .

Choose Back . Select Plant 22##.

Select Details . Enter your customer: T-S200## in the Customer no. plant field. Choose Save .

Choose Exit back to the Stock Transport Order customizing list.

4-1-5 Check and make any required assignments in the Assign delivery type/checking table in Stock Transport customizing. The following assignments must exist:

Ty. SPl DlTy. CRI NB 12## NLCC B UB 10## NL RP

Navigate to ERP IMG: Materials Management Purchasing Purchase Order Set up Stock Transport Order Assign Delivery Type and Checking Rule Update the table, if necessary, with the information in the table above.

Choose Save .

Choose Back .

SAP AG SCM612 3-62

4-1-6 Check and make any required assignments in the Purchasing document type table in the Stock Transport customizing area. The table must include the following combinations of allowed stock transports and corresponding Purchase Order Document Types:

SPl Plnt Type One step 10## 12## UB Not checked 12## 22## NB Not checked

Navigate to ERP IMG: Materials Management Purchasing Purchase Order Set up Stock Transport Order Assign Document Type, One-Step procedure, Underdelivery Tolerance Make sure that there are two entries in the table that match the data in the table above.

Choose Enter .

Choose Save , if necessary.

Choose Back 4-1-7 Verify and make any necessary changes to the Transportation Relevancy tables. In

this step you will make sure that delivery document types NL and NLCC are set as relevant for transportation processing. In addition, you must verify that all relevant item categories for these document types are set as "relevant" for transportation processing. Unless these objects are set as "relevant" for transportation processing you will not get shipment documents created when TP/VS planned shipments are "published". Navigate to ERP IMG: Logistics Execution Transportation Shipments Maintain Transportation Relevance Select Maintain transportation relevance for delivery types. Verify that delivery types: NL and NLCC are "checked" for transportation relevance.

Select Back to the Activity box. Select Maintain transportation relevance for delivery item types, Verify that Item Categories: ELN, NLC and NLN are "checked" for transportation relevance.

Choose Back to the Activity box. Select Maintain transportation relevance for routes. Select the Position button. Enter FR0007.

SAP AG SCM612 3-63

Verify that this route is relevant for transportation. If the Rel. for transport check box is blank, select the box and then choose Save.

Choose Exit .

Choose Cancel

SAP AG SCM612 3-64

Solutions

Unit: ERP Organizational Units, Shipments and Integration Topic: Settings Necessary for Integration

5-1 You can have a handling unit representing the shipment created automatically in the shipments that are published to the ERP system by TP/VS. To facilitate this you must have the packaging materials representing the means of transport created in the ERP material master. You have decided to do this for your implementation of TP/VS. Create three packaging material master records, based on information in the following table:

Material Number Copy from material Description FTL-## TRUCK-04 FTL Group ## LTL-## TRUCK-05 LTL Group ## SHIP-## TM-110 SHIP Group ##

These materials should have Material Type of VERP and Industry Sector of Mechanical Engineering. The following views should be created: Basic Data 1, Sales: Sales Org. Data 1, Sales: Sales Org. Data 2, Sales: General/Plant Data and Accounting 1. In the Organizational Data enter only your Plant 12## but "copy from" Plant 1200 of the reference material. All other data fields should remain the same as the reference material.

Navigate to SAP Menu: Logistics Materials Management Material Master Material Create (Special) Packagin Enter the following on the Create Packaging (Initial Screen): Material Number From the table above Industry Sector M - Mechanical Enginering Copy From Material From the table above

Select Select Views button. Select the following views:

Basic Data 1 Sales: Sales Org. Data 1 Sales: Sales Org. Data 2 Sales: General/Plant Data Accounting 1

SAP AG SCM612 3-65

Choose Continue Enter the following in the Organizational Levels dialog:

Choose Continue . On the Basic data 1 screen, enter the Description as indicated in the table.

Choose Enter on all remaining screens. NOTE: When creating the SHIP-## packaging material: if necessary, in the Sales: General/Plant view, enter KP (no ATP Check and Loading group 0001. In the Accounting 1 view enter a Moving price of 1.00

Choose Save on the Accounting 1 screen. Enter the remaining materials using steps b. thru i.

Choose Exit

Organizational levels Copy from Plant 12## Plant 1200 Sales Organization Distribution Channel

SAP AG SCM612 4-1

SAP AG 2008

Contents: SCM TP/VS-related ERP Master Data TP/VS Means of Transport TP/VS Resources Transportation Lanes Hierarchies

SAP AG SCM612 4-2

SAP AG 2008

Lesson 3: TP/VS Resources

Lesson 4: Transportation Lanes

SCM TP/VS Master Data

Lesson 1: SCM TP/VS-related ERP Master Data

Lesson 2: TP/VS Means of Transport

Lesson 5: Hierarchies

SAP AG SCM612 4-3

SAP AG 2008

At the conclusion of this unit, you will be able to:

Describe the result of the transfer of ERP TP/VS relevant Master Data into SCM

Explain the function of the individual Master Data Types in SCM

Specify where in the APO System it may be necessary to add to the Master Data transferred from ERP

Define TP/VS Means of Transport Define TP/VS Resources Create Transportation Lanes Create Transportation Zone and TSP Hierarchies

SAP AG SCM612 4-4

SAP AG 2008

In preparation for transportation planning using the APO TP/VS component, master data must be transferred to the APO system using the CIF.

The PC electronics manufacturer must set up one or more integration models to transfer TP/VS relevant master data to APO.

SAP AG SCM612 4-5

SAP AG 2008

Lesson 3: TP/VS Resources

Lesson 4: Transportation Lanes

SCM TP/VS Master Data

Lesson 1: SCM TP/VS-related ERP Master Data

Lesson 2: TP/VS Means of Transport

Lesson 5: Hierarchies

SAP AG SCM612 4-6

SAP AG 2008

!"#

After completing this lesson, you will be able to: Describe the ERP master data that is required for TP/VS

planning. Create an APO Core Interface model to transfer the

required data from the ERP system to the SCM APO system.

SAP AG SCM612 4-7

SAP AG 2008

!"!$%

To start the TP/VS planning process the required master data must be present in the SCM APO system. This include product and location master data among others. The implementation team must establish CIF models in the ERP system to transfer this data to the TP/VS environment.

SAP AG SCM612 4-8

SAP AG 2008

&'()* +

ERP Transaction Data

ERP Master Data

PlantShipping PointCustomerVendorTrp.zone

Material Master

Location

Product

Planned Sales OrdersPlanned Purchase OrdersPlanned Production OrdersPlanned DeliveriesPlanned Shipments

Sales OrdersPurchase OrdersProduction OrdersDeliveries

Shipments

SCM Transaction Data

SCM Master Data

ERP SCM

CIF (real time or batch)

CIF (real time)

Batch transfer of master data: The transfer of master data changes can be scheduled periodically as a job.

A variant has to be defined (containing the target system and the selection of master data objects) for the RCPTRAN4 report (hidden behind transaction CFP1)

SAP AG SCM612 4-9

SAP AG 2008

CIF

#,

Plant

Distribution Center

Storage Location MRP Area

Transportation zone

Customer

Vendor

Production Plant