TM110 - ERP Integration for Order Management (Shipper Specific).pdf

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]

ERP Integration for Order Management (Shipper Specific)


P A R T IC IP A N T H A N D B O O K INSTRUCTOR-LED TRAINING Course Version: 16 Course Duration: 2 Day(s) Material Number: 50131925

0



SAP Copyrights and Trademarks

© 2015 SAP SE. All rights reserved. No part of this publication may be reproduced or transm itted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. •

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

•

IBM, DB2, DB2 Universal Database, System i, System i5, System p. System p5, System x, System z, System zlO, System z9, zlO, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S /39 0 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, P0WER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

•

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

•

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

•

Oracle is a registered trademark of Oracle Corporation

•

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

•

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

•

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

•

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.

•

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries.

•

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

•

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.



These materials are subject to change without notice. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.





0



Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used.

This information is displayed in the instructor’s presentation

Demonstration

Procedure

Warning or Caution

A

Hint O

Related or Additional Information

Facilitated Discussion

0

User interface control

Example text

Window title

Example text




0



Contents xi

Course Overview

1

Unit 1:

2 11

Lesson: Describing Transportation Requirements Unit 2:

12 19 26 35 45

SAP ERP Integration for Order Management

Master Data Integration

Lesson: Integrating SAP ERP Master Data with SAP TM Exercise 1: Generate and Activate an Integration Model Lesson: Evaluating Master Data in SAP TM Exercise 2: Evaluate Master Data in SAP TM Unit 3:

Integration of Transportation Requirements

47

Lesson: Preparing SAP TM for Integration of Transportation

53 59

Requirements Exercise 3: Define Transportation Requirement Types Lesson: Preparing SAP ERP for Integration of Transportation Requirements Lesson: Integrating Sales Orders and Deliveries into SAP TM Exercise 4: Configure Appropriate Outputs from a Sales Document Exercise 5: Activate Order Integration in SAP ERP Lesson: Generating Transportation Requirements in SAP TM Exercise 6: Create Transportation Requirements with SAP ERP Integration Lesson: Integrating Purchase Orders into SAP TM

65 69 73 78 83 93 97 102 113 125

126 132 139 144

Exercise 7: Create a Purchase Order Lesson: Integrating Scheduling Agreements into SAP TM Exercise 8: Create a Scheduling Agreement Unit 4:

Transportation Requirement Processing

Lesson: Integrating Routing Information from SAP ERP Lesson: Retaining Consistency Across Systems Exercise 9: Manage Cross-System Changes Lesson: Scheduling Sales Orders with SAP TM



153

154

Lesson: Triggering Delivery Creation from SAP TM

163 169 175 180

Exercise 10: Create a Delivery Lesson: Updating and Splitting Deliveries Lesson: Managing Blocks Lesson: Integrating Handling Units

189

Unit 6:

Lesson: Building Freight Units

190 197

Exercise 11: Define Freight Unit Types Exercise 12: Apply Freight Unit Building Rules Exercise 13: Create Freight Units Lesson: Building Packages

205 209 217 225 239

Transportation Demands for Planning

Exercise 14: Create Freight Units with Packages Unit 7:

Transportation Planning

240

Lesson: Defining the Transportation Planning Process

246 249 257

Lesson: Evaluating Freight Units Exercise 15: Examine a Freight Unit Lesson: Creating Freight Orders for Shipping Exercise 16: Create a Freight Order

263 271

Unit 8:

SAP Transportation Management Transportation Network

273 281 290 299 305 313 319

Lesson: Integrating SAP ERP Master Data with SAP TM

329 333 335 347

Exercise 20: Create a Means of Transport Lesson: Defining Transportation Lanes Exercise 21: Create Transportation Lanes

350 357 360 365

Exercise 17: Generate and Activate an Integration Model Lesson: Evaluating Location Masters Exercise 18: Examine Location Masters Lesson: Creating Transportation Zones Exercise 19: Define Transportation Zones Lesson: Defining Methods of Transportation

Exercise 22: Calculate Durations and Distances using Transportation Lanes Lesson: Creating Carrier Profiles Exercise 23: Create Carrier Profiles Lesson: Examining Resources in SAP TM Exercise 24: Define Capacity Limits with Vehicle Resources



Lesson: Defining Conditions in SAP TM Lesson: Identifying Incompatibilities

380 383 387 397

Exercise 25: Create Incompatibility for Transportation Groups Unit 10:

Transportation Planning Preparation

399 403 411

Lesson: Examining Optimizer Planning

417 424

Exercise 27: Create Selection Profiles and Sub Profiles Lesson: Creating Planning Profiles

429 436 437

Exercise 28: Create a Planning Profile Lesson: Creating Capacity Selection Settings

445

Exercise 26: Create Freight Order Types Lesson: Defining Selection Profiles

Exercise 29: Create a Capacity Selection Profile Unit 11:

Interactive Planning with the Transportation Cockpit

446

Lesson: Customizing the Transportation Cockpit Layout

453 458 459 465 469 477

Exercise 30: Create a Profile and Layout Set Lesson: Customizing the Transportation Cockpit Exercise 31: Customize the Transportation Cockpit Lesson: Performing Interactive Planning Exercise 32: Create Freight Orders Interactively Lesson: Examining Freight Order Scheduling

481 493

494 503 509 515

Exercise 33: Schedule a Freight Order Unit 12:

Carrier Selection

Lesson: Performing Carrier Selection Exercise 34: Execute Carrier Selection Lesson: Tendering Freight Orders Exercise 35: Tender a Freight Order







Course TARGET AUDIENCE This course is intended for the following audiences:

•

Application Consultant

•

Business Process Architect


© Copyright. All rights reserved.

xi




0



UNIT 1 SAP ERP Integration for Order Management

Lesson 1 Describing Transportation Requirements

2

UNIT OBJECTIVES

•

0

Describe outbound and inbound transportation requirements



Unit 1 Lesson 1 Describing Transportation Requirements

LESSON OVERVIEW This lesson introduces outbound and inbound transportation requirements in the context of SAP TM. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Transportation Requirements in SAP TM

Order Manage ment

Figure 1: Document Flow

The initial event that triggers the transportation management process is a transportation requirement. This document may be created on the back of a sales order, a purchase order, or a



stock transport order (STO). The corresponding returns can also be the trigger for a transportation requirement. Additionally, the trigger could also be an outbound or inbound delivery, or a Scheduling Agreement.. All of these transportation requirements request the movement of a material. In a shipper scenario, this movement is caused by a facility within the same company. SAP TM integration with SAP ERP is accomplished using Web Services, for example, SAP NetWeaver Process Integration (SAP PI). Transportation Management Triggers in the Shipper Scenario

•

Sales order

•

Sales order return

•

Purchase order

•

Purchase order return

•

Stock transport order

•

Stock transport return

•

Outbound delivery

•

Inbound delivery

•

Scheduling Agreements (SD, MM)

The shipper/supplier focus is fully integrated with SAP ERP (inbound and outbound). This includes sales orders (SOs), purchase orders (POs), and stock transfer orders (STOs). SO, PO, and STO returns are also included. Transportation Requirements

•

Sales Order Selected SAP ERP sales orders create outbound messages in SAP ERP which are sent to SAP TM, where an order-based transportation requirement (OTR) is created. The necessary data for the transportation of goods, such as the customer at the end of a sales order, a shipping point, a material and quantities, delivery date, and several other requirements for the transport, are incorporated into the OTR.

•

Purchase Order / Stock Transport Order Selected purchase orders, using standard purchase order workflow configuration, initiate the process of sending the purchase order data to SAP TM. In SAP TM, an OTR is created as well. SAP TM does not differentiate between inbound and outbound transportation. Therefore, an OTR is used for both sales orders and purchase orders.

•

Scheduling Agreement Selected MM scheduling agreements and sales scheduling agreements can be integrated to create OTRs in TM also. The integration is based on delivery schedules. The relevant data, including dates and quantities are incorporated into the OTR.

•

Delivery



Deliveries can also initiate the transportation process in SAP TM. Deliveries can be transferred to SAP TM in addition to the predecessor orders, or as a first source for integration with SAP TM. In the latter case, instead of integrating the created sales order or purchase order, only the outbound or inbound delivery is sent to SAP TM. For deliveries, a delivery-based transportation requirement (DTR) is created. SAP ERP Logistics Integration

SAP TM

1

r

L.

^ Delivery-Based Transportation Requirement

Order-Based Transportation Requirement

A

k

A

Figure 2: ERP Logistics Integration

SAP TM — SAP ERP integration is available as of SAP ERP 6.05 and additional integration functionality has been added with subsequent enhancement packs for SAP ERP. For this reason, it may be that not all the functionality described in this or other trainings is available with every installation of SAP ERP 6.05. As already mentioned, the transportation process in SAP TM is started with a transportation requirement document. This transportation requirement can be order-based or delivery-based. When integrating an ERP sales order with SAP TM, the process flow in ERP remains the same as for a system not integrated with SAP TM. The sales order is created in the usual way and saved. Upon saving, the ERP system creates an XML message in the background that is sent to SAP TM. The document in SAP TM that corresponds to the ERP sales order is the order-based transportation requirement (OTR). The OTR is created by the system upon receipt of an XML message from ERP. The OTR document contains all the transportation-relevant information about the sales order. In the context of creating sales orders, it is usual to talk about outbound transportation. However, as already mentioned, SAP TM does not differentiate between outbound and inbound transportation. Therefore, the OTR does not state any information about outbound or inbound



scenarios. The ship-to party is incorporated in the OTR document as the destination location. The shipping point determined in ERP is used as the source location of the OTR. Therefore, it is mandatory to transfer all master data from SAP ERP to SAP TM using the Core Interface (CIF) framework before integration transactional data. In cases of sales order integration, the source location on the header level of the OTR is empty. This is because the shipping point in ERP is determined per item line or even per schedule line. Therefore, it can occur that one ERP order contains several item lines or schedule lines that contain different shipping points and therefore different source locations. The source location is filled on the item level of the OTR. However, because the ship-to party is maintained for the entire ERP sales order, the destination location can be defined at header level of the OTR. Similarly with SAP ERP sales orders, purchase orders can also be integrated into SAP TM. The integration technology behind the integration of purchase orders is different to that behind the integration of sales orders. Instead of output management, workflow is used to create the XML message. However, once the XML message is created in SAP ERP, it is sent to SAP TM and the same process is triggered as for the sales order. The message received in SAP TM is again used to create an order-based transportation requirement. Since SAP TM does not differentiate between inbound and outbound transports, OTRs are created for both. For purchase orders, the source location, being the vendor, is defined on the header level of the OTR, while the destination location is only defined on the item level. This is because the receiving plant can differ from item line to item line while the vendor needs to be maintained at header level of the purchase order. Stock transport orders (STOs), being a special type of purchase order, can also be transferred to SAP TM. As with sales orders and purchase orders, stock transport orders transferred to SAP TM create an OTR document. Because an STO is a special type of purchase order, the workflow functionality in SAP ERP is again used to create the XML message that is transferred to SAP TM. A scheduling agreement is an outline agreement containing delivery quantities and dates within a specified time period. These are entered as schedule lines in a delivery schedule. You can integrate MM scheduling agreements and Sales scheduling agreements from SAP ERP with SAP TM. The integration is based on delivery schedules. You can control the communication between the two systems by using specific time horizons and by specifying which delivery schedule types (Forecast or JIT) should be transferred. Communication is based on eSOA services, supporting both process integration (PI) based communication and web services reliable messaging (WS-RM). The integration can be triggered by the creation or a change of delivery schedules. You can use a batch process to manage the future transfer of delivery schedules.



Order-Based Transportation Requirements

Figure 3: Order-Based Transportation Requirement

The OTR is the first document created in the SAP TM system when starting the transportation process. It is created when a triggering XML message is received from a connected SAP ERP system. The OTR document lists all necessary information for the transport of the corresponding ERP order, such as products, schedule lines, delivery dates, locations and quantities. The OTR is read only, which means the data contained in the document may not be changed manually. The reason for this is that in a scenario that includes integration between the two systems, the lead system is SAP ERP and every change to the transportation process is therefore supposed to be triggered from the ERP order. In order to be able to perform follow up activities such as planning or subcontracting, a successor document, the freight unit, is created out of the OTR document (freight units and freight unit creation are discussed later in the course).



Delivery-Based Transportation Requirements

Delivery-Based Transportation Requirement

Figure 4: Delivery-Based Transportation Requirement

Instead of starting the transportation process with an ERP order, the process can also be started based on a delivery. Regardless of whether an inbound delivery or an outbound delivery has been received by SAP TM, a delivery-based transportation requirement (DTR) is created. Other than in SAP LE-TRA, inbound and outbound deliveries can be consolidated into one transport. This is because once they have been transferred to SAP TM they are only referred to as DTRs, with no differentiation between inbound and outbound. Depending on the configuration of the SAP ERP system, the ERP order may not create a message for SAP TM to trigger the process, it being triggered instead by a delivery. The decision whether to start the process in SAP TM with the ERP order or the ERP delivery depends on individual customer requirements and guidelines concerning transportation planning and execution. If shipping activities other than transportation planning are involved prior to the transportation process, it is more likely to start the process based on the ERP delivery. If the goods are already sold considering all shipping activities, the ERP order will be the basis for transportation planning. On studying a DTR document, you can see that OTR and DTR documents are not very different from each other. Like the OTR, the DTR cannot be edited, and can only create freight units to continue the transportation process. Therefore, from the point of view of the continuation of the transportation process, there is no difference between transportation requirements based on an ERP orders and those which are based on ERP deliveries — both documents are capable of triggering the entire process.



LESSON SUMMARY You should now be able to:

•




Learning Assessment

1. Which SAP ERP documents create an order-based transportation requirement in SAP TM? Choose the correct answers. | A Sales order B Inbound delivery | C Returns purchase order D Stock transport order E Outbound shipment 2. Freight units can be based on delivery-based transportation requirements. Determine whether this statement is true or false. | True False

0



Learning Assessment - Answers

1. Which SAP ERP documents create an order-based transportation requirement in SAP TM? Choose the correct answers.

|~xj A Sales order B Inbound delivery

|~xj

C Returns purchase order

|~xj

D Stock transport order E Outbound shipment

2. Freight units can be based on delivery-based transportation requirements. Determine whether this statement is true or false. [x ] True False



Lesson 1 Integrating SAP ERP Master Data with SAP TM Exercise 1: Generate and Activate an Integration Model

12 19

Lesson 2 Evaluating Master Data in SAP TM Exercise 2: Evaluate Master Data in SAP TM

26 35

UNIT OBJECTIVES

0

•

Describe how the CIF transfers master data to TM

•

Examine master data in SAP TM



Integrating SAP ERP Master Data with SAP TM

LESSON OVERVIEW This lesson examines the integration process between SAP ERP and SAP TM. You learn about the SAP ERP master data that is relevant for integration with SAP TM. and consider how the Core Interface (CIF) supports the process of integration. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


The Integration Process When implementing TM, consider if your business is integrating to SAP ERP, or implementing TM as a stand-alone product. Depending on which scenario applies to your business, the integration options differ. In the case of a shipper using a back end SAP ERP system, the business requires automated integration when implementing TM. When using SAP ERP, integration is delivered in two formats. The first is used to support the integration of master data. This is referred to as the Core Interface (CIF). This uses a queued remote call function (qRFC) process to create and synchronize the data as frequently as required. The second integration format is for transactional data and is discussed in a later unit. Transferring the ERP master data is a two-step process: Step 1: Select the Relevant ERP data models using transaction CFM1

Step 2: Transfer the ERP data from SAP ERP to SAP TM using transaction CFM2 Figure 5: CIF Master Data Models



Integration Between SAP ERP and SAP TM

The integration between SAP ERP and TM is a two-step process. The first step is to determine what data from your ERP system needs to be replicated in TM. This is activated by a scheduled batch job using a program variant. For example, as you create new customer master records you may need to transfer these to TM on a daily basis; these can be considered in the nightly TM planning run. Once the data is selected, the transfer process is prompted from ERP. Using RFC calls, the data is created in TM. Similar to the selection process, this is prompted by a scheduled job using program variants. This two-step process is managed by a business analyst or a member of the IT group. Integration Model The CIF uses an object called an integration model to manage the data transfer and synchronization process between SAP ERP and the SAP New Dimension products. TM is used to support only the transportation aspect of logistics; not all items in the integration model will integrate. Generate integration model. Name ^

^

Determine name and SAP TM target system. Select master data.

Target system Application

Plant Material master

Activate integration model. Integration model is active.

* (&

S t a r t

Master data will be transferred.

Figure 6: Generate Integration Model/Activate Integration Model

The Integration Model The transfer of master data and transaction data is controlled in the CIF by an integration model. You create, generate, and activate this integration model in the ERP system. Integration models do not exist in TM. In the integration model, select the dataset (master or transaction data) you want to transfer. Specify the following in the integration model: •

The SAP TM target system for the data transfer

•

The data objects you want to transfer

Define the integration model that controls the transfer of master and transaction data in the ERP system. You can find the menu option Core Interface Advanced Planner and Optimizer (the CIF menu) under Logistics —► Central Functions —> Supply Chain Planning Interface.



The integration model distinguishes between master data and transaction data. When integrating with TM, you transfer master data via the integration models. Transactional data is not transferred using the CIF. We recommend that you select different types of data in separate integration models and then transfer them separately, for example, shipping points, customers, or vendors.

Note: Your ERP system may use integration models to communicate with an APO instance and an instance of EWM. All use integration models and transfer similar data, but the target systems are different. You can deactivate and then delete the integration models that you no longer need. Generate the Integration Model Name + application = unique definition of integration model Name

Vnt

Target sys.

.]

pc TM_MD_01

Application I

1 Material master

1

I Customers

LZI Plants n

SAP TM system

TM CLNT800

1

1

I Vendors

□

W ork centers

Selection of master data types

Sales orders Relevant materials

rs >

Material Plant

1000

Selection criteria for the relevant data

MRP type Q*

Execute

+

|Q

Save

Figure 7: Generate Integration Model

The master data transferred from the ERP system to the SAP TM system in the initial transfer is defined in an integration model. The ERP system generates this integration model (transaction CFM1). Elements in an Integration Model In the ERP system, a unique integration model consists of five elements:

•

Model Name

•

Logical System

•

APO Application

•

Date

•

Time



SAP recommends that you have one integration model per object. To integrate a master data object, identify the model name, logical system, and APO application. Select the object that you want to transfer to TM. Assuming you do not want to transfer every material in the ERP database, restrict the metadata you want to transfer. Transfer only the active materials.

Note: Although the field is labeled APO application, the field is still applicable to TM. You may want to use the model name field to represent the business division and the application (TM/APO/EWM) that the integration model is going to be used to support. The APO application can be used to identify objects in the integration model, such as materials, customers, or vendors. It is useful to create several integration models with the same name, but as different applications. Ensure that your integration model data pools are not too large. This enables you to handle errors more easily. Integration Model Generation The target or logical system that you specify in the integration model determines the new dimension (TM) system to which the master data is transferred. The target system is a logical (TM) system that must have an RFC connection. This is defined by the basis team. Specify the model, logical system, APO application, object, and metadata. Save this as a program variant. This schedules the generating integration models program on a nightly basis. It calls out the program variants you created. Once the program variant is created, generate an integration model by executing the model. The ERP system then reviews your database and identifies what items are transferred and created in TM. You may do this interactively the first time you generate an integration model. Subsequently, the program is scheduled as a background job.



Integration Model Activation

In te g ra tio n m o d e l

Name Target system Application "Activate" PUMPS

PUMPS I APQCLNT800 MATERIALS

#

I

Active/lnactive

APOCLNT800

MATERIALS

10:00 AM

Start

Figure 8: Activating an Integration Model for Initial Data Transfer

To transfer data to SAP TM, you must activate the integration model generated. You activate an integration model with transaction cfm2. ERP —> Logistics —*■ Central Functions —> Supply Chain Planning Interface —*■ Core Interface Advanced Planner and Optimizer —> Integration Model —> Activate Choose the Start function to trigger the data transfer to TM. The master data, or the equivalent of the ERP master data, then exists in the TM system. The initial data transfer runs in a particular order: the objects are selected successively, transferred to TM and processed there in this sequence. For improved system performance, it is also possible to execute a parallel initial data transfer. Several integration models can be activated at the same time. During parallel processing, you can set whether to run the selection in RPC, the processing in TM, or both at the same time. Parallel processing takes place within an object type. The different object types are still transferred in sequence.



Regenerate an Integration Model

ER

31.

N ew

Name Target system Appl.

PUMPS

1

APOCLNT800 MATERIALS

E x is tin g in teg ratio n m o d el

Execute B 0

Save

ly/f Material master "Activate" MRP type

xo

PUMPS

APOCLNT800

MATERIALS

11:00 AM

PUMPS

APOCLNT800

MATERIALS

10:00 AM

Start

s? Active/lnactivel

D iffe ren c e is tra n s fe rre d

New master data in SAP TM Figure 9: Repeat Generation and Activation

You can regenerate and activate an existing active integration model with the same or changed selection criteria, under the same name at any time. The existing model is regenerated (and the new master data is selected). There are then two models with the same name. The only difference between them is the date and time. This option is suitable for transferring new or changed TM-relevant master data. If you activate a regenerated model, only the difference in the objects not contained in the runtime version is transferred, including any change pointers that may exist. The system compares the existing, active integration models with the new model for each object and determines which new master data needs to be created in TM (delta transfer). Data Transfer After the data is transferred, the old integration model is deactivated and the new integration model is activated. For example, you activate model 1 with the material masters A and B, and activate model 2 in the second step with the material masters B and C. Thus, when you activate model 2, only material C will be transferred. When you deactivate model 1, the integration for materials B and C remains.



Periodic Regeneration of an Existing Integration Model

Report RIMODGEN Name

G e n e ra te in teg ra tio n m o d el

w

PUMPS

Target system APOCLNT800 Application

MATERIALS

Report RIMODAC2

Variant PUMP MAT

JOB 1 Execute ____+ ____ O Save

cD O Step 1

A ctiv a te in teg ra tio n m o d el

Name

PUMPS

Target system

APOCLNT800

Application

MATERIALS

JOB_2 Â ctive /lna ctive

+

Step 1

Start

Figure 10: Periodic Generation and Activation

To ensure that the system transfers all the TM-relevant master data, it is possible to regenerate periodically and activate the existing integration models. Because any existing change pointers are also processed in this procedure, a separate transfer of data changes is no longer necessary. Integration models can be regenerated and activated at regular intervals. You can do this automatically through the definition of jobs. Report RIMODGEN generates an integration model. You schedule this report by entering a variant that you define as a job. Report RIMODAC2 activates an integration model. You need a variant for this report to enable you to schedule it in a job. You can retransfer all the data objects with report RIMODINI. You need a variant for this report to schedule it in a job. The entire data record is transferred. If, for example, you change just one field in a material master, the entire material master is retransferred with the data change transfer.



Unit 2 Exercise 1 Generate and Activate an Integration Model

Business Example

ABC Corporation wants to implement SAP TM to support truck-load (TL) and less-than-truckload (LTL) planning scenarios. The SAP consultant needs to create appropriate CIF models to transfer master data from SAP ERP to SAP TM. Set Up Data Transfer from SAP ERP to SAP TM Your business wants to integrate your plants, shipping points, and materials from SAP ERP to TM. Create the necessary integration models to support this activity and ensure that you can generate new integration models if necessary. Note that in this exercise, you transfer customers and carriers for use during the course. These customers and carriers are participant-specific. Shipping points and materials have already been transferred and are common to all groups and participants.Insert the

1. In SAP ERP, create a CIF model to transfer customers from SAP ERP to TM. Save your data, and name and describe the variant. Use the following data: Field

Value

Model Name

TM_GR##

Logical System

ZMTCLNT800

APO Application

Customers

Customer (from and to)

CUST##-01to CUST##-30

Create Loc./BP

Create both

Variant Name

GR## Cust

Description

GR## Customer Integration

2. Generate an integration model. 3. In SAP ERP, create a CIF model to transfer carrier master data. Save your data, and name and describe the variant. Use the following data:

0

Field

Value

Model Name

TM_GR##

Logical System

ZMTCLNT800

APO Application

Carriers

Material Independent Objects screen area

Vendor



Field

Value

Vendors from

CAR##-01

Vendors to

CAR##-04

Create Loc./BP

Only create business partners

Variant Name

GR## Carrier

Description

Group ## Carriers/FWD Agents

4. Generate an integration model. Transfer Data from SAP ERP to SAP TM You have now selected the master data to transfer and integrate with TM. You now need to initiate the transfer process. Trigger the activation of your new integration models.

1. In SAP ERP, configure the parameters for transfer of master data to SAP TM. Select the Parallelize Selection in ERP System checkbox. Use the following data: Field

Value

Model

TM_GR##

Logical System

ZMTCLNT800

Absolute Max No. of Processes

20

APO Application

This field should be empty

2. In SAP ERP, transfer customer master data to TM. Drill down on your logical system ZMTCLNT800, then your model TM_GR## to transfer the customer data. 3. In SAP ERP, transfer carrier master data to TM. Drill down on your logical system ZMTCLNT800, then your model TM_GR## to transfer the carrier data. 4. (Optional) In Customizing for SAP ERP, ensure the client level settings for change integration via the CIF appear. 5. (Optional) How are master data changes transferred to SAP TM?



Unit 2 Solution 1 Generate and Activate an Integration Model

Business Example

ABC Corporation wants to implement SAP TM to support truck-load (TL) and less-than-truckload (LTL) planning scenarios. The SAP consultant needs to create appropriate CIF models to transfer master data from SAP ERP to SAP TM. Set Up Data Transfer from SAP ERP to SAP TM Your business wants to integrate your plants, shipping points, and materials from SAP ERP to TM. Create the necessary integration models to support this activity and ensure that you can generate new integration models if necessary. Note that in this exercise, you transfer customers and carriers for use during the course. These customers and carriers are participant-specific. Shipping points and materials have already been transferred and are common to all groups and participants.Insert the

1. In SAP ERP, create a CIF model to transfer customers from SAP ERP to TM. Save your data, and name and describe the variant. Use the following data: Field

Value

Model Name

TM_GR##

Logical System

ZMTCLNT800

APO Application

Customers

Customer (from and to)

CUST##-01to CUST##-30

Create Loc./BP

Create both

Variant Name

GR## Cust

Description


a) In SAP ERP, from the SAP Easy Access screen, choose the menu path: Logistics —*■ Central Functions —► Supply Chain Planning Interface —> Core Interface Advanced Planner and Optimizer —> Integration Model —► Create (transaction code: C

F

M

l ) .

b) At the top of the Create Integration Model screen, fill the Model, Logical System, and APO Application fields as specified in the table. c) Under Material Independent Objects, select the Customers checkbox and then choose the £> (Special Restrictions') button. d) Under Customers, fill the Customer (from and to), and CreateLoc./BP fields as specified in the table.

0



e) Save your data. f) On the Variant Attributes screen, fill the Variant Name and Description fields as specified in the table. g) Save your data. 2. Generate an integration model. a) On the Create Integration Model screen, choose b) Choose the c) Choose

Execute to process the selection.

Generate IM button to generate the integration model. Continue on the information message.

d) Exit the Create Integration Model screen and return to the SAP Easy Access screen. 3. In SAP ERP, create a CIF model to transfer carrier master data. Save your data, and name and describe the variant. Use the following data: Field

Value

Model Name

TM_GR##

Logical System

ZMTCLNT800

APO Application

Carriers


Vendor

Vendors from

CAR##-01

Vendors to

CAR##-04

Create Loc./BP

Only create business partners

Variant Name

GR## Carrier

Description


a) In SAP ERP, from the SAP Easy Access screen, choose the menu path: Logistics —*■ Central Functions —> Supply Chain Planning Interface —> Core Interface Advanced Planner and Optimizer —> Integration Model —> Create (transaction code: C

F

M

l ) .

b) On the Create Integration Model screen, fill the Model, Logical System and APO Application fields as specified in the table. c) Under Material Independent Objects, select the Vendors checkbox and then choose the £> (Special Restrictions) button. d) Under Vendors, fill the Vendor (from and to) and Create Loc./BP fields as specified in the table. e) In the menu bar, choose Go to —> Variant —► Save as Variant. f) Name and describe the variant as specified in the table.



g) Save your data. 4. Generate an integration model. a) On the Create Integration Model screen, choose b) Choose the c) Choose


Generate IM button to generate the integration model. Continue on the information message.

d) Choose the Exit icon several times to return to the SAP Easy Access screen. Transfer Data from SAP ERP to SAP TM You have now selected the master data to transfer and integrate with TM. You now need to initiate the transfer process. Trigger the activation of your new integration models.


Value

Model

TM_GR##

Logical System

ZMTCLNT800


20

APO Application

This field should be empty

a) In SAP ERP, from the SAP Easy Access screen, choose Logistics —> Central Functions —*■ Supply Chain Planning Interface —> Core Interface Advanced Planning and Optimizer —> Integration Model Activate (transaction code: —

►

c

f

m

2

) .

b) Enter the data from the table. Ensure that the APO Application field is empty, and the Parallelize Selection in ERP System checkbox is selected. c) Choose (Execute) and stay on the Activate or Deactivate Integration Model screen to carry out the next steps. 2. In SAP ERP, transfer customer master data to TM. Drill down on your logical system ZMTCLNT800, then your model TM_GR## to transfer the customer data. a) Select Customers to show model details. b) Select the top line and choose the

Active/lnactive button.

c) Select the line again and choose (fy(Start) to initiate the transfer. d) Answer NO to branching to application logs and choose ^ message.

Continue on the information

e) Stay in the transaction. 3. In SAP ERP, transfer carrier master data to TM. Drill down on your logical system ZMTCLNT800, then your model TM_GR## to transfer the carrier data.



a) Select Carriers to show model details. b) Select the top line and choose the

Active/lnactive icon.

c) Select the line again and choose (fy(Start) to initiate the transfer. d) Answer NO to branching to application logs and choose ^ message.


4. (Optional) In Customizing for SAP ERP, ensure the client level settings for change integration via the CIF appear. a) On the SAP Easy Access screen, start transaction

spro.

b) Choose SAP Reference IMG, and then choose Integration with Other SAP Components —> Advanced Planning and Optimization —*• Basic Settings for the Data Transfer —> Change Transfer —> Change Transfer for Master Data —> Configure Change Transfer for Master D ata. c) Do not make any changes in the Customizing activity. Choose Exit several times to return to the SAP Easy Access screen. 5. (Optional) How are master data changes transferred to SAP TM? The changes are processed to SAP TM in real time.




•

0




Unit 2 Lesson 2 Evaluating Master Data in SAP TM

LESSON OVERVIEW In this lesson, you learn about SAP ERP and SAP TM location types, and consider the roles of the customer, vendor, and business partner in transportation planning. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Locations in SAP TM

As a result of CIF integration, master data is created in SAP TM. Figure ERP Master Data Integration gives an overview of master data objects which can be transferred from SAP ERP to SAP TM using the CIF. Locations can be created based on plants, shipping points, customers, and vendors. Business partners can be created based on customers and vendors. Products can be created based on material master data.



A location is a logical or physical place in which resources are managed on a quantity basis. A freight unit is used as the basis for the transportation processes in which you name a source location, a destination location, and any transshipment locations necessary to complete it. Define a Location Type

Location type Description 1001

Production plant

1002

Distribution center

1003

Shipping point

1010

Customer

1011

Vendor

1030

Terminal

1100

Port

1110

Airport

1120

Railway station

1130

Container Freight Station

1140

Hub

1150

Gateway

1160

Container Yard

1170

Warehouse

1180

Carrier Warehouse

Figure 13: Location Types

In SAP TM, you define different location types, representing different kinds of locations. Specific location types are available for ERP master data that triggers the creation of locations in SAP TM.



ERP and TM Location Types ERP

SAP TM

Figure 14: ERP and TM Location Types

Different customizing entries and master data elements from ERP are displayed in SAP TM as locations with different location types. ERP plants, customers, vendors, and shipping points are integrated with SAP TM and become the following types of location: Plants-1001 (production plant) or 1002 (distribution center), Customers-1010 (customer), Vendors-1011 (vendor), and Shipping Points-1003 (shipping point). The location type is automatically determined based on the object being transferred from ERP when location data is created via the CIF. Shipping Points in SAP TM In the SAP ERP system, each inventory-relevant location can be assigned one or more shipping points. A shipping point is an independent organizational unit at a fixed location that processes and monitors inbound and outbound deliveries.



Plant

l l _. W^mrnm Bb I .

m

g* '

Truck Warehouse

Rail Loading Station

Plant (1001)

Shipping Point (1003)


Figure 15: Shipping Point Integration

In ERP, the shipping point can have the following information assigned to it: •

Address

•

Transportation Zone

•

Factory Calendar

•

Working Times

•

Loading Time

•

Pick/Pack Time

Shipping Point Integration

As a result of CIF integration, a shipping point in SAP ERP creates a location master with a location type 1003 (shipping point). The location has the address information from SAP ERP because of integration. No other data assigned to the shipping point ERP transfers to SAP TM because the parameters are maintained differently to support more robust planning functionality. If the shipping point has the same name as the plant, a Business Add-In (BAdl) is applied to SAP ERP before the shipping point can be transferred. The BAdl adds an extension to the shipping point name so that it is different from the plant.



Business Partners in SAP TM Different business partners with various relationships to one another exist in the marketplace. Examples of business partners are: •

Customer

•

Vendor

•

Employee

•

Contact person

•

Driver

Examples of business relationships are: •

Vendor-customer: The vendor acts as the forwarding agent for the customer.

•

Contact person - customer: The contact person is employed at the customer's company.

•

Contact person - customer: The contact person is the customer's consultant but does not work in the same company.

•

Customer-customer: Sold-to party and ship-to party are not the same.

•

Employee - contact person: Contact person is looked after individually.

•

Employee - customer: Customer manager

Partner Types

The business partners that exist in the marketplace are represented in the SAP system by a partner type. Table 1: Partner Types Partner types AP, KU, LI, and PE are defined in partner processing for the sales and distribution application module. These are defined as follows: Acronym

Definition

AP

Contact Person

KU

Customer

LI

Vendor

PE

Personnel



Partner Functions

Figure 16: Partner Functions

Partner types allow us to distinguish between different business partners. Partner functions represent the roles they play within the business transaction. For example, different customer partners can assume certain roles in a business transaction. The customer who places the order is not necessarily the same customer who receives the goods or is responsible for paying the invoice. Assigning Partner Functions Assigning partner functions in the SAP system determines the functions of particular partners in the sales process. One partner may have several functions. For example, when all the partner functions within the customer partner type are assigned to one business partner, the same customer is the sold-to party, ship-to party, payer, and bill-to party. You can enter contact persons for a customer directly in the customer master so that they are automatically assigned to that customer. The contact person can also be assigned to another customer, in a consultant role, for example. The forwarding agent is an example of a vendor. Employees in your company are managed in the employee master records. They can assume partner functions of partner type Personnel, such as the partner function ER: Employee Responsible.



Integrating Business Partners

Customer

CIF

C>a

Customer - 1 0 1 0

SP Sold-to party SH Ship-to party

BP Bill-to party

CIF

Business partner Roles

PY Payer

>

VE Vendor Vendor - 1011

Supplier

CIF

-> ®

Figure 17: Integrating Business Partners

In business transaction documents such as an order-based transportation requirement (OTR), the BP master data object appears as a participating party in transportation processes. The party assumes roles, such as consignee, shipper, or ordering party. The CIF models involved in customers and vendors require more than plant and material data. This is to ensure that when the customers and vendors are transferred, the business partner and locations are created. When the CIF model is constructed, you input a setting for customers and vendors. Business Partners and Locations

In the Create Loc./BP there are three settings: •

Blank-Only create a location

•

1-Only create a business partner

•

2- Create business partner and location

2- Create business partner and location is relevant for customers and vendors in SAP TM. Shipping point location type 1003 does not have this setting, but must have a defined business partner in certain scenarios. The business partner for the shipping point is created manually in SAP TM and assigned to the shipping point location. A BAdl is available to automate this process. During the transfer of a customer, it is created with the corresponding type and if selected in the CIF, the business partner is created automatically in SAP TM and assigned to the location. Customers in SAP TM SAP ERP defines the customer as a business partner with whom a business relationship involving the issue of goods or services exists. SAP TM considers how these customers relate to planning.



The customer is relevant to planning during transportation planning in TM. Sales orders are generated in SAP ERP and transferred to SAP TM as requirements for planning in the context of shipping.

Data transfer from the customer (ERP) ERP

M a s te r d a ta : C u s to m e r

Customer;|J0063-----

Location

0000001000

Name

Loc. type

1010

<(^~B ecker~

Street <££alvinstr. 36 City

<0 3 4 6 7 Berlin

Becker

Customer

/ G eneral\/A ddress\ S lrset — -Calvinstr. 36 ----- 4 *)4C7 D /trlin

Countr

Germany

Re9ion <013>eerlift 11

Language
TM

Master data: Location

German

(CCET^

Control data x transportation zone

Berlin

Master data: Transportation Zone Tr.Zone

D10000

Berlin region

D10000 11 Berlin region Figure 18: Customer Location Type

Transferring Customers from ERP SAP TM plans shipments to one or more customers. TM works with the SAP ERP delivery processing. This functionality requires information about customers and their geographic locations to calculate distances and durations during an optimization planning run. Customers are transferred from ERP as locations with type 1010. TM customers represent a destination location in the case of a sales order, or a source location in the case of a returns order. Because these are objects created by the CIF, the system also copies basic settings for the customer such as description, address data, and time zone. TM locations contain additional planning parameters that have no equivalents in SAP ERP. You must maintain these parameters in TM. The system cannot transfer them from ERP without further activities. Vendors In SAP TM SAP ERP defines the vendor as a business partner from whom materials or services are procured. The vendor master is master data, whether it is created for a one-time purchase or as a partner with whom your organization engages continuously.



Vendor Master Records

When vendor master records are transferred to SAP TM they prompt the creation of location master records of location type 1020. If you are modeling an inbound scenario, transfer the materials supplier as a location. This is the source location. When transferring vendors from ERP, create both the location master and the business partner. Both customer and vendor master data exist in the SAP SCM location master data. If customer and vendor masters in the SAP ERP system have the same number ranges, any vendor master having the same account number as a customer master must be renamed. A user-exit exists for this purpose; during the transfer of SAP ERP master data any vendor account number that is a duplicate of a customer master can be renamed automatically. Carrier locations are normally not needed in TM. Carriers that provide services that we order and pay for are created as business partners only.



Unit 2 Exercise 2 Evaluate Master Data in SAP TM

Business Example

You need to check the location and business partner master data that was created in SAP TM based on the customer and carrier master data that was transferred from SAP ERP. Review some of the details of the integration process. 1. In NWBC, view location master data for CUST##-16. 2. What is the address?

3. What business partner was assigned to the location? Hint: Go back to the 'General' tab.

4. On the Resources tab, what are the loading and unloading hours?

5. Review business partner Cust##-16 that was created in SAP TM as a result of CIF integration. 6. What is the address?

7. What business partner roles are created?

8. Review business partner CAR##-01 that was created in SAP TM as a result of CIF integration.

0



9. What business partner roles are created?



Unit 2 Solution 2 Evaluate Master Data in SAP TM

Business Example

You need to check the location and business partner master data that was created in SAP TM based on the customer and carrier master data that was transferred from SAP ERP. Review some of the details of the integration process. 1. In NWBC, view location master data for CUST##-16. a) In NWBC, choose Master Data —> Transportation Network —► Location —► Define Location.

b) Enter cust##-16 in the Location field and choose Display. 2. What is the address? 800 Independence Avenue, Evansville, IN 47713, USA_________________________________ 3. What business partner was assigned to the location? Hint: Go back to the 'General' tab. Business partner CUST##-16 is created and assigned to your customer location.__________ 4. On the Resources tab, what are the loading and unloading hours? By choosing the Resources tab, you can assign resources to your locations to support loading and unloading details. Because this is TM data and this item was just transferred from ERP, it may not have been maintained.___________________________________________________ 5. Review business partner Cust##-16 that was created in SAP TM as a result of CIF integration. a) In NWBC, choose Master Data —> General —► Define Business Partner. b) Enter business partner cust ##-16. 6. What is the address? The address is the same as that for the location._____________________________________ 7. What business partner roles are created? Four roles are created for this partner: Business Partner (Gen.), Financial Services BP, Ship-to Party, and Sold-to Party. You can see these in the dropdown for the Display in BP role field. 8. Review business partner CAR##-01 that was created in SAP TM as a result of CIF integration.

0



a) In NWBC, choose Master data —> General —► Define Business Partner. b) In the toolbar, choose theQ$(Open BP) icon (Shift + F5). c) Enter business partner car##-01. 9. What business partner roles are created? Three roles are created for this partner: Business Partner (Gen.), Carrier, and Financial Services BP.




•

0






Unit 2

Learning Assessment

1. Which SAP ERP master data elements can be transferred to SAP TM? Choose the correct answers. | A Supply Area B Customer | C Material D Shipping Point 2. The Core Interface (CIF) is used to transfer both master data and transactional data to SAP TM. Determine whether this statement is true or false. | True False 3. Which location types are used when a location is created based on master data from SAP ERP? Choose the correct answers. | A Production Plant B Customer | C Airport D Vendor E Container Freight Station

0



4. By transferring customer master data from SAP ERP, both a location and a business partner can be created in SAP TM. Determine whether this statement is true or false. | True False



Unit 2


1. Which SAP ERP master data elements can be transferred to SAP TM? Choose the correct answers. | A Supply Area [x ] B Customer

|~x]

C Material

[x ] D Shipping Point

2. The Core Interface (CIF) is used to transfer both master data and transactional data to SAP TM. Determine whether this statement is true or false. | True \x \ False

3. Which location types are used when a location is created based on master data from SAP ERP? Choose the correct answers. [x ] A Production Plant [x~| B Customer | C Airport [x ] D Vendor E Container Freight Station

0



4. By transferring customer master data from SAP ERP, both a location and a business partner can be created in SAP TM. Determine whether this statement is true or false. 0

True False



UNIT 3

Integration of Transportation Requirements

Lesson 1 Preparing SAP TM for Integration of Transportation Requirements

47

Exercise 3: Define Transportation Requirement Types

53

Lesson 2 Preparing SAP ERP for Integration of Transportation Requirements

59

Lesson 3 Integrating Sales Orders and Deliveries into SAP TM Exercise 4: Configure Appropriate Outputs from a Sales Document Exercise 5: Activate Order Integration in SAP ERP

65 69 73

Lesson 4 Generating Transportation Requirements in SAP TM Exercise 6: Create Transportation Requirements with SAP ERP Integration

78 83

Lesson 5 Integrating Purchase Orders into SAP TM Exercise 7: Create a Purchase Order

93 97

Lesson 6 Integrating Scheduling Agreements into SAP TM Exercise 8: Create a Scheduling Agreement

102 113

UNIT OBJECTIVES

0

•

Define transportation requirement types

•

Activate SAP ERP order and delivery integration

•

Configure output types for integration into SAP TM



•

Explain the process of generating transportation requirements in SAP TM from sales orders in SAPERP

•

Describe the impact of changes to the shipping condition

•

Create a purchase order in SAP ERP and identify requirements for integration into SAP TM

•

Explain the generation of transportation requirements in SAP TM from scheduling agreements in SAP ERP



Unit 3 Lesson 1 Preparing SAP TM for Integration of Transportation Requirements

LESSON OVERVIEW In this lesson, you examine the necessary settings in SAP TM to integrate transportation requirements from SAP ERP, and you also learn how to integrate text types. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Order-Based and Delivery-Based Transportation Requirements ! SAP ERP

Order Management

Figure 20: Document Flow (Transportation Requirements Focus)

0



The integrated orders and deliveries created in SAP ERP are represented by transportation requirements in SAP TM. The integration allows you to react continuously to changes to orders and deliveries that occur in the SAP ERP system. T ra n s p o rta tio n R eq u ests Depending on the business need, there are several ways in which transportation requests can be received and created:

From internal SAP ERP system:

From external ordering party / customer:

• • • • • •

• •

Sales O rde r P urchase O rder S tock T ransport O rder O utbound D elivery Inbound D elivery S cheduling A g reem ents

Via X M L m essage E ntered m anually

SAP ERP logistics integration is accomplished with either SAP PI or Web Services Reliable Messaging (WS-RM). WS-RM is a point-to-point connection option using Web Services. Documents Integrated from SAP ERP The documents integrated as standard from SAP ERP are: •

Sales orders

•

Purchase orders

•

Stock transfers

•

Sales order returns

•

Purchase order returns

•

Stock transfer returns

•

Outbound deliveries

•

Inbound deliveries



•

Scheduling Agreements (SD, MM)

Order-Based and Delivery-Based Transportation Requirements

SAP ERP logistics integration introduces the concept of order-based (OTR) and delivery-based (DTR) transportation requirements. The customer downstream TM processing options are as follows: •

From OTRs only

•

Consuming OTRs with DTRs

•

From DTRs only

DTRs can be created from outbound deliveries (SOs) and from inbound deliveries (POs). Creation of DTRs from SAP ERP deliveries without order reference are also supported. Customizing the OTR and DTR In Customizing for SAP TM, you can specify different types of order-based and delivery-based transportation requirements (OTRs/DTRs). These allow your organization to define certain parameters for the OTR that influence how the system processes this business document. For example, if you receive an order from a customer who buys products in truck load quantities, there is no reason to plan this requirement with others. The system can immediately plan the order in a short-cut process.



Defining Features Within the Transportation Requirement Type Change View "Order-Based Transportation Requirement Types": Details *1? New Entries

Q

(8 13 £3 0T99

OTR Type

TMlll GR99 Order-Based Transp Rqrrmt

i

Default Type Number Range Settings 01

Number Range Interval

Process Control / Busness Object Mode “’BW Relevance

(v Automate Freight Unit Buidng

r Enable Approval Workflow 1 Track Changes

i Automatic Block P Actual Quantity Event Manager

Integration Active

EMWeb Interface Transaction [ Dynamic Determnation of Outpu Dangerous Goods Profile Text Schema Propagate Changes Incoterm Loc. Stage Bldng

Output Profile Add. Output Profite Retention Period

1 1 n ERP_DFLT ni99 Text Type Synchronous Propagation of Changes, Fatoack to Asynchronous

1

-

n

Stage Profile

Stage Profile Cond.

I-----------

1

Default Values Default Weight UoM Plan on Req/Cnf Qty Piarmg Profile Freight Unit Buldng Riie FU Buldng Rule Condtion

[lb- ] DefaJt vcAjme UoM Plan on Confirmed Quantities

U

FBR99

U

I»1 13

3F

Figure 22: Transportation Requirement Type Customizing

Within the transportation requirement type, you can define the following: •

BW relevance: You can indicate if the system can extract data from documents of this type to the SAP BW environment.

•

Automatic freight building: You can decide if you prefer the system to generate freight units automatically or if you want planners do this manually.

•

Freight unit building rules: If freight units are to be built, you can identify rules or conditions that assist in planning transportation requirements.

•

Activate work flow

•

Track document changes

•

EM Integration: You can trigger whether integration to the delivered EM system is active. You define the events in customizing if you require more than is delivered by SAP.

•

Output profile: This determines what possible documents and EDI messages may be generated.•

•

Dangerous goods profiles: If you are shipping materials classified as hazardous, you use this profile to assist in determining which materials cannot be shipped together.



•

Planning quantities (OTR only): Depending on your scenario, you may want to plan on either the requested quantities or the confirmed quantities that were determined by ATP.

Business Scenarios in SAP TM There may be several different planning scenarios modeled in SAP TM. To make sure that your SAP ERP document type maps to your TM document type, you must create conditions that map the two systems together.

Input Values Define input values for each condition by defining business object fields including user-specific fields and and/or values determined in external determination classes. Conditions are used as control parameters throughout SAP TM. Different condition types are available for different needs. Table 2: Determination of the Transportation Requirement Type The following table shows the condition type used for the determination of the transportation requirement type: Object

Condition Type

Order-based transportation requirement

/SCMTMS/OTR_TYPE

Delivery-based transportation requirement

/SCMTMS/DTR_TYPE

Integration of Text Types Texts are stored in various objects in the SAP system, such as documents. You can define different text types for each of these areas. A sales note, a marketing note, and a shipping specification are examples of sales-specific text types. Documents contain texts at header and item level. You can enter texts in several different languages. You can store texts in the master data and then copy them into sales and distribution documents. You can also copy texts from a reference document to another sales and distribution document, for example, from a quotation to an order, or from an order to a delivery document. Texts can be copied in a specific language. Text control is used to determine texts automatically when you create a text object. Texts on ERP documents can be integrated to SAP TM. In SAP TM, you need to define text types and map ERP text types to TM text types. A set of text types is defined as a text schema. A text schema can be



assigned to a transportation requirement type, defining which text types can be used for this document type in SAP TM. The transferred texts will be visible in the transportation requirement. Change Trade Fair30-0tdet 13270: Header Data

©& Trade Far 30CrOWr

Sales

13270

Caches# order no

CUST00-18

Grw.it DMde / 10 US 42 W / Carrolton KT

Ghppng

Mrg Document

Payment cards

-*■>

ffi

T*t ty. •

Form Header

Accounting

. BSli

• •

Heiader note 1 \~2Header note 2 • Q* Header note 3 ■ Header note4

• S3 Formsucptomwnt U • 3 Terms of delvery

D is p la y B ills O rd e r 1 1 0 0 0 0 0 1 7 8 (S a le s O rd e r 1 3 2 7 0 )

• Shppng instructor* • GJ Terms of payment

doc*

• GJ Warranties • •

3 3

Penalty for breach c Contract riders (dau

General Data

• S3Selection • S3 Other contractual st • Q

jsMu

.

Business Partner

Locations and Dates/Twnes

r je r t f j Text Type

,

• 3 license[Platej*). B|

License P e te Ms

a n fM jn Encash

Mo □

CM m sradey

O w ig e d O n

XITMUSCR

1110312011 15 5 8 4 1 CfT

L>C

/\

Figure 24: Text Type Mapping



Define Transportation Requirement Types

Business Example

Your company wants to start planning in SAP TM. To do so, you need a document to support integration in SAP ERP and planning in SAP TM. Create an order-based transportation requirement type to support this business requirement. 1. In Customizing for SAP TM, review the number ranges used in forwarding order management. 2. Remain in Customizing for SAP TM. Create a new order-based transportation requirement type to support your freight unit planning and integration. Use the following data: Field

Value

OTR Type

OT##

Description

GR## Order Type


01

Automatic Freight Unit Building

Selected

Text Schema

ERP_DFLT

Propagate Changes

Synchronous Propagation of Changes, Fall back to Asynchronous

Default Weight UoM

LB

Default Volume UoM

M1 *3

Plan on Req/Cnf Qty

Plan on Confirmed Quantities

Freight Unit Building Rule

FUBRJTMlll

Transportation Requirement Type Determination Most of your configuration for SAP ERP and SAP TM integration is complete. You now need to create a condition record that instructs TM to create the correct OTR type and FU based on your integration scenario.

1. In Customizing for SAP TM, review the document type code for SAP ERP documents in TM. Choose SAP Transportation Management —> Transportation Management —>General Settings for Order Management —*• Define Business Transaction Document Type Codes.

0



2. What is document type code 001?



5. In NWBC, review the condition ZOTR_TYPE. Make sure that an OTR type determination condition record exists in TM that will map a document type code and sales order type to your new OTR type. This should correspond with the data in the following table: Field

Value

Condition Name

ZOTR_TYPE

TR Original Order C

Sales Order

TR ERP Order Type

ZA##

TR Destination Location

No value

Buyer Origin Document

No value

OTR Type

OT##



Define Transportation Requirement Types

Business Example

Your company wants to start planning in SAP TM. To do so, you need a document to support integration in SAP ERP and planning in SAP TM. Create an order-based transportation requirement type to support this business requirement. 1. In Customizing for SAP TM, review the number ranges used in forwarding order management. a) In Customizing for SAP TM, choose SAP Transportation Management —> Transportation Management —> Forwarding Order Management —> Define Number Range Intervals for Forwarding Order Management. b) Choose

Execute.

c) Choose the

Display Intervals button.

d) Explore the intervals defined. You can assign any of the intervals to a transportation requirement type. e) Exit the screen. 2. Remain in Customizing for SAP TM. Create a new order-based transportation requirement type to support your freight unit planning and integration. Use the following data:

0

Field

Value

OTR Type

OT##

Description

GR## Order Type


01

Automatic Freight Unit Building

Selected

Text Schema

ERP_DFLT

Propagate Changes

Synchronous Propagation of Changes, Fall back to Asynchronous

Default Weight UoM

LB

Default Volume UoM

M3

Plan on Req/Cnf Qty

Plan on Confirmed Quantities


FUBRJTMlll



a) Choose SAP Transportation Management —> Transportation Management —> Integration —> ERP Logistics Integration —> Order- Based Transportation Requirement —> Define Order-Based Transportation Requirement Types. b) Choose

Execute.

c) Choose New Entries. d) Enter the data from the table. e) Save your data and exit the screen. Transportation Requirement Type Determination Most of your configuration for SAP ERP and SAP TM integration is complete. You now need to create a condition record that instructs TM to create the correct OTR type and FU based on your integration scenario.

1. In Customizing for SAP TM, review the document type code for SAP ERP documents in TM. Choose SAP Transportation Management —> Transportation Management —>General Settings for Order Management —> Define Business Transaction Document Type Codes. 2. What is document type code 001? Purchase Order_______________________________________________________________ 3. What is document type code 73? Outbound Delivery_____________________________________________________________ 4. What is document type code 114? Sales Order__________________________________________________________________ 5. In NWBC, review the condition ZOTR_TYPE. Make sure that an OTR type determination condition record exists in TM that will map a document type code and sales order type to your new OTR type. This should correspond with the data in the following table: Field

Value

Condition Name

ZOTR_TYPE

TR Original Order C

Sales Order

TR ERP Order Type

ZA##

TR Destination Location

No value

Buyer Origin Document

No value

OTR Type

OT##



a) In NWBC, choose Application Administration —> General Settings —>Conditions —>Display Condition. b) Enter the condition name from the table above and choose Continue. c) Review the entries of the decision table and verify that an entry according with the table above exists.




•




Preparing SAP ERP for Integration of Transportation Requirements

LESSON OVERVIEW To finalize integration with SAP TM, you need to trigger the transfer of the order data from SAP ERP to SAP TM. In this lesson, you begin to configure the necessary settings to send your sales orders to SAP TM. In this lesson specifically, you learn about requisite business functions and the role of control keys. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Business Functions Integration of SAP ERP orders and deliveries facilitates transportation planning and execution in SAP TM based on orders and deliveries created in an SAP ERP system. The orders and deliveries are represented by transportation requirements in SAP TM. Integration with SAP ERP enables you to: •

Collectively plan transportation for all orders and across order types.

•

Perform transportation planning in SAP TM based on SAP ERP orders before delivery creation. This forecasts transportation and resource demands.

•

Perform tendering, subcontracting, and execution in SAP TM based on SAP ERP orders before delivery creation.

•

Propose and create deliveries based on dates and quantities according to transportation planning results. This takes into account transportation constraints such as resource availability and transportation durations.

Order and delivery data can be transferred between SAP TM and SAP ERP using enterprise services. This communication can be realized either via SAP NetWeaver Process Integration or using point-to-point communication (Web Services Reliable Messaging). Required Configuration

0



In SAP ERP, there are three requirements to establish integration with SAP TM. 1. Your ERP system must use enhancement pack 5 for SAP ERP 6.0. This requires the activation of several business functions. 2. Determine which SAP ERP documents are to be transferred to TM. 3. On an order or delivery level, activate the orders or deliveries to be transferred. Business Function Selection Name

Description

Purpose

LOG_TM_ORD_l NT

ERP-TMS: Order Integration

Order integration with sales order scheduling

LOG TM ORD INT TR Q

ERP-TMS: Basic Order Integration

Order integration without sales order scheduling

LOG_ESOA_OPS_2

Operations, Enterprise Services 2

Transfer purchase orders and stock transport orders

O P SAD V R E TU R N S1

Advanced Returns Management

Transfer returns orders to SAP TM

SD_01

Logistics S&D Simplification

Transfer sales orders to SAP TM

ESOA_OPS01

Operations, Enterprise Services

Transfer sales orders to SAP TM

Prerequisites:

Or

Recommended:

Or

| Figure 26: Business Functions

The first step in integration is to activate the appropriate business functions in SAP ERP. Choose between business functions l o g _ t m _ o r d _ i n t or l o g _ t m _ o r d _ i n t _ t r q . Between these two, you determine if sales order scheduling is relevant.



Business Functions

For the business functions l o g _ t m _ o r d _ int or l o g _ tm _ o r d _ i nt _ t r q ,no dependencies are explicitly defined for other business functions (using transaction sfw2). Depending on which business processes you have and which service operations you want to use, the following business functions must also be activated: • sd _01 or e s o a _ o p s 01 (s a p _a p p l 602) - Both business functions activate the Lean Order Framework (LORD). This is required if you do not want to send order data to SAP TM using the service operations s l o _ t r a n s p o r t a t i o n r e q u e s t s u i t e r e q u e s t _ o u t or CRP_t r a n s p o r t a t i o n r e q u e s t s u i t e r e q u e s t _ o u t immediately in the dialog (VA01, VA02) but want to process the messages (SE38 rsnastoo) at a later stage or again in a separate and asynchronous step. Without LORD, message processing can only be carried out manually and immediately. Therefore, you activate one of the two business functions. • LOG_ESOA_OPS_2 (SAP_APPL, Enhancement Package 3) - If you want to send purchase orders from SAP ERP to SAP TM, you must activate this business function. This business function activates the workflow technology in purchasing to generate the corresponding service operations. p o p _ t r a n s p o r t a t i o n r e q u e s t s u i t e r e q u e s t _ o u t and POP_TRANSPORTATIONREQUESTSUITECANCELLATIONREQUEST_OUT use this procedure. • o p s _a d v r e t u r n s _1 (SAP_APPL, Enhancement Package 4) - This business function activates Advanced Returns Management. This function provides a mechanism that ensures a purchase order contains only returns items or only nonreturns items. Documents with mixed items are no longer possible. This is necessary to ensure a clear separation of the service operations from the delivery side. An outbound delivery must be generated for returns items using service operation o d p _ t r a n s p o r t a t i o n r e q u e s t s u i t e r e q u e s t _ o u t .An inbound delivery must be generated for normal purchase order items using service operation ODP TRANSPORTATIONREQUESTSUITEREQUEST OUT.



Business Function

Available From

LOG_TM_ORD_INT_TRQ (ERP-TMS: Basic Order Integration)

-

LOG_TM_ORD_INT (ERP-TMS: Order Integration)

-

-

-

Included functionality

SAP TM 8.0 SAP ERP 6.0 EhP4 SP09

-

SAP TM 8.0 SAP ERP 6.0 EhP5

-

Perform tran sp o rtatio n planning fo r ERP ord e rs and deliveries in SAP T M

- C reate in bou nd and o u tb o u n d deliveries in SAP ERP fro m SAP T M and tran sfer deliveries to SAP T M Perform tran sp o rtatio n planning fo r ERP ord e rs and deliveries in SAP T M -

Perform sales o rd e r scheduling in SAP T M

-

C reate in bou nd and o u tb o u n d deliveries in SAP ERP fro m SAP T M and tran sfer deliveries to SAP T M

LOG_TM_ORD_INT_l (ERP-TMS: Order Integration 1)

- SAP TM 8.1 - SAP ERP 6.0 EhP5 SP09

- Trigger delivery u p d a te /s p lit in SAP ERP based on planning changes in SAP T M -

Display in SAP ERP th e SAP T M d o c u m e n t status and d o c u m e n t flo w

-

LOG_TM_ORD_INT_ll (ERP-TMS: Order Integration 2)

-

LOG_TM_ORD_l NT_111 (ERP-TMS: Order Integration 3)

-

SAP TM 9.0 SAP ERP 6.0 EhP6 SP04 SAP TM 9.1 SAP ERP 6.0 EhP7

Enable integration scenario E W M - ERP - T M

- Sam e fu nction al scope as LO G _TM _O R D _IN T _l (For technical reasons LO G _TM _O R D _IN T _l has been created to d o w n p o rt fu n ctio n ality fro m EhP6 to EhP5) - Transfer purchase o rd e r co n firm ed qu an tities fro m SAP ERP to SAP T M - Transfer h a nd over lo cations/dates in SAP ERP purchase orders to SAP T M - Transfer sh ipm en t blocking reasons to SAP T M

LOG_TM_ORD_INT_IV

-

SAP TM 9.2 SAP ERP 6.0 EhP7 SP06

-

M a in ta in shipping types fo r external purchase orders

-

M o n ito r changes to shipping conditions fo r sales orders

-

M a in ta in Shipping co nd itio n fo r PO (M a p p e d to service level co de in T M )

-

Provide h a n d o ve r d a te fo r confirm atio ns in PO

Figure 27: Order Integration Business Functions

Control Keys

Ctrl Key

0001

SO to TM

PO to TM

Outbound delivery

Inbound delivery

SO Scheduling

PO Confirmations

w b

Sales order is relevant for transfer Ctrl Key

SO to TM

PO to TM

Outbound delivery is relevant for transfer Outbound delivery

Inbound delivery

s o

Scheduling

PO Confirmations

0 0 0 2

I Sales order is relevant for transfer Figure 28: Relevancy for Transfer Control Key

In SAP ERP, you can display the available control keys for the document transfer.



Control keys are configured in Customizing for SAP ERP: Integration with Other SAP Components —> Transportation Management —> Logistics Integration —> Define Control Keys for Document Transfer. In the Activate Order Integration in SAP ERP activity, assign a control key to your sales order document types to integrate sales orders, customer returns, and their corresponding deliveries as well as SD scheduling agreements. The control key that you assign must have the SO to TM checkbox selected. If you want to transfer deliveries for this order, the Outbd Del. checkbox must also be selected in the control key. To integrate purchase orders, stock transport orders, return purchase orders, return stock transport orders, and their corresponding deliveries as well as MM scheduling agreements, assign a control key to your purchasing document types. The control key that you assign must have the PO to TM checkbox selected. If you want to transfer deliveries for this order, the Inbd Del. checkbox (for Purchase Order), must also be selected in the control key. Activation fo r Sales Orders

Sales org.

Distr. channel

Division

Sales order type

Shipping condition

Ctrl key

1000

10

00

OR

01

0001 ) 800

SO to TM

r U to TM

V l

Sales order is relevant for transfer

Outbound delivery

Inbound delivery

SO Scheduling

TM No.

PO Confirmations

0 i

Outbound delivery is relevant for transfer

Figure 29: Relevancy for Transfer: Activation for Sales Orders

Relevancy for the transfer of sales orders and SD scheduling agreements is configured in Customizing for SAP ERP: Integration with Other SAP Components —> Transportation Management —> Logistics Integration —> Activate Transfer of Sales Documents. When you define your different document integration scenarios, you then assign the control key to a sales organization, distribution channel, division order type, and shipping condition. You also assign it to the TM client with which you will be interfacing. When the sales order is relevant for transfer, the control key is copied to the sales order document (table VBAK, field tm_ctrl_key ).The TM number can be used to differentiate the SAP TM systems if multiple systems are used. Process Integration (PI) can route messages to the proper TM system using this control key. In purchasing scenarios, you also assign your control key to a purchasing organization, purchasing group, purchase order type, and TM client.



Another Customizing activity is available to activate the transfer of delivery documents based on shipping point, delivery type, and shipping condition. This Customizing is only evaluated for deliveries that are based on orders that were not transferred to SAP TM. In case an order was transferred to SAP TM based on the corresponding Customizing, the decision whether the corresponding deliveries are transferred to TM has already been taken by the control key that was determined for the order. The following Business Add-Ins (BAdls) are available to control the transfer of documents from SAPERPto SAP TM:

CHANGE_TM_CTRL_KEY: You can use this BAdl method to change to control key assigned to the sales document types. CHANGE_LOG_TM_NR: You can use this BAdl method to change the technical transportation management number assigned to the sales document types. There is also a BAdl that allows you change the integration process between ERP and TM. The BAdl method CHANGE_TM_CTRL_KEY changes the control key that was determined using the maintained Customizing. Method CHANGE_LOG_TM_NR allows you to change the technical transportation management number that was determined using the maintained Customizing. Both methods can be used to incorporate additional attributes for determination, that are not available in Customizing. Custom fields can also be used here. LESSON SUMMARY You should now be able to:

•




Unit 3 Lesson 3 Integrating Sales Orders and Deliveries into SAP TM

LESSON OVERVIEW To finalize integration with SAP TM, you need to trigger the transfer of the order data from SAP ERP to SAP TM. In this lesson and the previous lesson, you configure the necessary settings to send your sales orders to SAP TM. In this lesson specifically, you learn about the configuration of appropriate outputs. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Purpose of Output Types D itp U y TM S ta n d a rd O rd e r 1 5 0 2 0 : O v e rv ie w

* 4J A * c.' •-

• • *» 15*20

‘■ aro fra

cwroo-M

ShP-Toftrty

nmoo-M im

eeiMno«

Item oaanrBw 2

NOtvAM

S*,640.00 IMO

0) 1

Qm*ftteirflWoofl'« a a pqhkq

Rsrri i t u

0T-1C-M14

fi* rn g furty

1 n o ru m n

I

£§ '! » ( « )

Raata') la mjartcr

TMSUbx

Ds*«i rtjrl Tot* Woa>t • fttn g elite

Eodn

D ts p ta y T M 100 G r o u p 0 1 D O T 1 1 0 0 0 0 0 4 0 0 ( S a t e s O r d e r 1 6 0 2 0 )

US* teisl&tWL (»WorJtawf v*r, Cto&dvefcn

»w<— zr»i

wo

M mk

IMW HIUIK •V*

IMS

'I li

Figure 30: Integrating Sales Orders and Deliveries into SAP TM

When integrating ERP sales orders with SAP TM, the ERP process flow is not altered compared to an SAP ERP system not integrated with SAP TM. The sales order is created in the usual way and

0



saved. Upon saving, the ERP system creates an XML message in the background that is sent to SAP TM. The integration of sales orders and deliveries into SAP TM from Sales and Distribution (SD) is achieved using TM-specific output types. The corresponding document in SAP TM is the Order-Based Transportation Requirement (OTR). The OTR is created by the system when the XML message from ERP arrives. As shown in figure Sales Order Integration, the OTR document contains all transportation-relevant information about the sales order, as required by SAP TM. When creating sales orders we usually talk about outbound transportation. However, SAP TM does not differentiate between outbound and inbound transportation. Therefore, the OTR does not state any information about outbound or inbound scenarios. The ship-to party is incorporated into the OTR document as the destination location. It is therefore mandatory to transfer all master data from ERP to TM using the Core Interface (CIF) framework before integrating transactional data. The shipping point determined in ERP is used as the source location of the OTR. Because different shipping points may be determined per line item, the shipping point as the source location is stored on item level in the OTR. Output Types in SD

Output is a means of communication. It allows partners and systems to exchange information. You can transmit output for different sales documents, such as quotations, orders, deliveries, or invoices. Output determination can depend on different criteria using the condition technique. We differentiate between header output and item output. Header output issues the whole document. Item output issues each individual item in the document. The transmission medium determines how output is issued. For example, you can agree with the customer that order confirmation is sent by EDI, or that Internet notification is given.



Lesson: Integrating Sales Orders and Deliveries into SAP TM

Output processing is controlled by the relevant processing program. A program with the relevant layout sets can be assigned to each output type and transmission medium. Outbound Messages for the Sales Document Object

Output type

Program

Sales order

TRSO

OPS_SE_SOC_SEND_MESSAGE

Figure 32: Outbound Message for Sales Document

The transfer of the sales order is launched using output determination. Output condition records are configured to allow messages to be sent. XML messages are generated by an SAP-delivered output program. Output type TRSO is used to trigger integration of sales orders to SAP TM, TRRO to trigger integration of customer returns, and TRDO to trigger integration of deliveries. Output Determination You can determine when an output is to be issued. The following times are available: •

The output to be sent is selected by a standard program ( r s n a s t o O) that is set to run at regular intervals. You decide if an output is to be selected the next time the program runs (transmission time-spot 1) or at a time specified by the user (transmission time-spot 2).•

•

There is a special selection program for different sales documents such as delivery and billing documents. You use it to process output online or in batches (transmission time-spot 3). You can schedule a batch to ensure regular processing (as for time 1).

•

The output is issued automatically as soon as a document is posted (transmission time-spot 4).



The Condition Technique

Output is determined using the condition technique. A condition record for an output type contains the requirements for that output type. If the requirements are met, the system proposes that particular output type. You determine the transmission medium, the time, and the partner function in the condition record. Output is sent to the partner who matches the partner function in the underlying object, such as the sales order. It is possible to create output that is not dependent on a particular partner, such as labels. You can use the analysis function on the output screen in the sales documents to check the output determination. You can see why a particular output was proposed, or why it was not determined. The Access Sequence The access sequence is a search strategy used by the SAP system to search for the valid output condition records. Each access step contains the name of a condition table that in turn contains the key fields for the output condition records. The rule that governs the sequence in which the system searches states is: From the specific to the general. To create a new access sequence, copy a similar and existing access sequence. Make any necessary changes to the copy. If you define your own access sequences, the keys start with Y or Z, as these namespaces remain free in the standard SAP system for this purpose.



Configure Appropriate Outputs from a Sales Document

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure appropriate outputs from the sales document to transfer transportation requirement data to SAP TM. 1. In Customizing for SAP ERP, review output types for sales order integration. Check whether output type TRSO is defined. 2. What does output type TRSO indicate?

3. In SAP ERP, assign your order type ZA## to output type TRSO. Use the following data: Field

Value

Output Type

TRSO

Sales Document Type

ZA##

Medium

8 Special Function

Date/Time

4 Send immediately (when saving application)

Language

EN

4. In Customizing for SAP ERP, review output types for delivery integration. Check if output type TRDO is defined. Is output type TRDO defined?5

5. In SAP ERP, verify that delivery document type LF is assigned to output type TRDO.

0



Configure Appropriate Outputs from a Sales Document

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure appropriate outputs from the sales document to transfer transportation requirement data to SAP TM. 1. In Customizing for SAP ERP, review output types for sales order integration. Check whether output type TRSO is defined. a) In Customizing for SAP ERP, choose Sales and Distribution —> Basic Functions —> Output Control —> Output Determination —► Output Determination Using the Condition Technique —> Maintain Output Determination for Sales Documents —> Maintain Output Types b) Choose

Execute.

c) Check to verify that output type TRSO is defined. For more details, select the appropriate line in the Output Types table and then choose the Details icon. 2. What does output type TRSO indicate? Order to Ext. TMS_____________________________________________________________ 3. In SAP ERP, assign your order type ZA## to output type TRSO. Use the following data:______ Field

Value

Output Type

TRSO

Sales Document Type

ZA##

Medium

8 Special Function

Date/Time

4 Send immediately (when saving application)

Language

EN

a) In SAP ERP, on the SAP Easy Access screen, choose Logistics —> Sales and Distribution —► Master Data —*■ Output —» Sales Document —► Create (transaction w i l ) .

b) Enter TRSO in the Output Type field and press ENTER.



Lesson: Integrating Sales Orders and Deliveries into SAP TM

c) Enter the data as specified in the table and then save. 4. In Customizing for SAP ERP, review output types for delivery integration. Check if output type TRDO is defined. a) In Customizing for SAP ERP, choose Logistics Execution —► Shipping —> Basic Shipping Functions —*• Output Control —> Output Determination —> Maintain Output Determination for Outbound Deliveries —*• Maintain Output Types. b) Choose

Execute.

c) Check whether output type TRDO is defined. Is output type TRDO defined? Yes________________________________________________________________________ 5. In SAP ERP. verify that delivery document type LF is assigned to output type TRDO. a) On the SAP Easy Access screen, choose Logistics —> Logistics Execution —> Master Data —*• Output —*• Shipping —> Outbound Deliveries —► Display (transaction W23).

b) Enter output type TRDO and press ENTER. c) Enter delivery type lf and choose Execute.





Activate Order Integration in SAP ERP

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure appropriate Customizing settings required to activate order integration from SAP ERP to SAP TM. 1. In Customizing for SAP ERP, review the control keys to activate integration for sales orders and deliveries to TM. Verify the following data: Field

Value

Ctrl Key

0001

Control Key Description

Stnd Sales Order, and Delivery, Order Scheduling Inactive

2. What option is assigned to control key 0005?

3. Exit the Customizing activity. 4. In Customizing for SAP ERP, activate the transfer of sales documents for your sales order type. Use the following data: Field

Value

Sales Organization

3000

Distribution Channel

10

Division

00

Sales document type

ZA##

Control Key

0001

TM Number

8 00

5. In Customizing for SAP ERP, review the configuration for activating delivery integration.

0



6. What control key is assigned to shipping point 3100 and delivery type LF?



Activate Order Integration in SAP ERP

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure appropriate Customizing settings required to activate order integration from SAP ERP to SAP TM. 1. In Customizing for SAP ERP, review the control keys to activate integration for sales orders and deliveries to TM. Verify the following data: Field

Value

Ctrl Key

0001

Control Key Description

Stnd Sales Order, and Delivery, Order Scheduling Inactive

a) In Customizing for SAP ERP, choose Integration with Other SAP Components —► Transportation Management —*• Logistics Integration —► Define Control Keys for Document Transfer. b) Choose

Execute.

c) Review the entry for the control key described in the table. 2. What option is assigned to control key 0005? Outbd Del. (Transfer Outbound Deliveries to TM)_________________________________ 3. Exit the Customizing activity. 4. In Customizing for SAP ERP, activate the transfer of sales documents for your sales order type. Use the following data:

0

Field

Value

Sales Organization

3000


10

Division

00

Sales document type

ZA##

Control Key

0001



Field

Value

TM Number

800

a) In Customizing for SAP ERP, choose Integration with Other SAP Components —*■ Transportation Management —> Logistics Integration —> Activate Transfer of Sales Documents. b) Choose

Execute.

c) Choose New Entries. d) Enter the data from the table. e) Save your data and exit the screen. 5. In Customizing for SAP ERP, review the configuration for activating delivery integration. a) In Customizing for SAP ERP, choose Integration with Other SAP Components —> Transportation Management —> Logistics Integration —> Activate Transfer of Delivery Documents. 6. What control key is assigned to shipping point 3100 and delivery type LF? Control key 0005



LESSON SUMMARY You should now be able to: •

0




Generating Transportation Requirements in SAP TM

LESSON OVERVIEW There are several different planning scenarios modeled in SAP TM. In this lesson, you learn to make sure that your ERP document types map to your TM document types. This ensures you can generate transportation requirements with ERP integration. You learn about integration troubleshooting and the impact of changes to the shipping condition. LESSON OBJECTIVES After completing this lesson, you will be able to: •


•


Process Integration

Provides additional capabilities ■ Logical & technical receiver addressing separated ■ Delegated receiver determination & message split possible ■ Message & protocol adaptation ■ Centralized configuration and monitoring

Reliable message delivery Technical receiver addressing by sender Compatible interfaces required Distributed configuration at run-time

Figure 34: Process Integration



The technical communication between SAP ERP and SAP TM is achieved using Web Services / XML messages. It can be established either by a mediated communication channel using SAP NetWeaver PI as a middleware or by a point-to-point connection via Web-Service ReliableMessaging (WS-RM). The figure Process Integration shows the advantages of both channels. Integration Troubleshooting

There are various steps to monitor the integration with SAP TM. For a sales order, as a first step you can check whether output type TRSO has been determined and executed successfully. In the figure Status or Output message in the Sales Document, you can see how the status of the output shows that the message has launched properly. This is indicated by a green light. This is now available directly from sales order processing. Useful Monitoring Transactions Monitoring ■

SXMB_MONI

Integration Engine: Monitoring

■

SXMVKDNITOR

Monitor for processed XML messages

P o s tp ro c e s s in g D e s k to p

B

■

/S A P P 0/P P 0 2

Edit Postprocessing Order

■

/S A P P 0/P P 0 3

Display Postprocessing Order

Figure 36: Useful Monitoring Transactions

If output has been triggered successfully, two monitoring transactions are available to review the status of message processing, as follows: •

Monitor for processed XML messages

•

Postprocessing desktop



Monitor for Processed XML Messages

Processed successfully m Scheduled \ M Application error - Manual restart possible Transfer to external application (postprocessing desktop)

>

M o n ito r fo r P rocessed XM L M essages □ □ Display

f i t Error Information

►> Referencing Messages

Q

qo

(^R estart

^

te i Expand

^ Expand Al Me!

N um ber of Displas ed X M L M e ssa g e s 1

ran s m o o a f o i r a n f i s w i XML Messages H i Status Ack. Status Executed From* StartTme* Executed U 07.09.2011 10:00:53 07.09.2011 A

_______________ E n d T iry ' sender Interface 10:00:=*^ SLO_Transportatx>nRequestSUITERequest_Out

Figure 37: Monitor for Processed XML Messages

With the monitor for processed XML messages, you can review whether the XML message was processed. This monitor is available on both the sending system and the receiving system. In case PI is used as middleware, the same monitor can even be used here. In case of short dumps on the receiving system, the message can be re-triggered from here. An XML message type is used to create the order-based transportation request: TransportationRequestSUITERequest Postprocessing Desktop

Postprocessing records are created whenever messages cannot be created by the SAP TM application. They can be reviewed, corrected, and reprocessed. In case of application errors, such as failed validations, locked objects, or missing master data, the message is forwarded to the Postprocessing Desktop. In the monitor for processed XML messages, these messages are displayed with status Transferred to external application. These messages must not be reprocessed from the monitor for processed XML messages, but only from the



Postprocessing Desktop. Messages can also be discarded in the Postprocessing Desktop, for example, if a problem is solved with a new updated message.





Create Transportation Requirements with SAP ERP Integration

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create transportation requirements with ERP integration required for transportation planning. 1. In SAP ERP, create a sales order using your order type and using the default delivery date. Use3 6 5 4 the following data: Field

Value

Order Type

ZA##

Sales Organization

3000


10

Division

00

Sold-to Party

Cust##-16

PO Number

GR##_101

Material

PRODTM-OO

Quantity

50

2. What sales order number is created?

3. In SAP ERP, on the SAP Easy Access screen, start transaction code s x m b _ m o n i . Using XI Monitor, display that the message content was transferred from ERP. 4. Using XI Monitor in SAP TM, display that the message content was received in SAP TM. 5. Validate in NWBC that the OTR has been created for the sales order by reviewing the transfer requirements. 6. Review the information in the General Data tab and compare it to the information contained in the original order in SAP ERP.

0



7. What TM Document Type was created for order type ZA##?

8. What is the life cycle status?

9. What is the consumption status?

10. Review the item data and compare it to the original order information in SAP ERP. 11. On the Document Flow tab, check whether a freight unit was created. 12. Open the newly created freight unit and review the data. 13. Which document type(freight unit type) was used?

14. Which freight unit building rule was used?

15. Review the item data. 16. Repeat the steps in this exercise to create another sales order to generate another transportation requirement in SAP TM. Use the following data: Field

Value

Order Type

ZA##

Sales Organization

3000


10

Division

00

Sold-to Party

Cust##-17

PO Number

GR##_201

Material

PRODTM-00



0

Field

Value

Quantity

50



Create Transportation Requirements with SAP ERP Integration

Business Example ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create transportation requirements with ERP integration required for transportation planning. 1. In SAP ERP, create a sales order using your order type and using the default delivery date. Use the following data: Field

Value

Order Type

ZA##

Sales Organization

3000


10

Division

00

Sold-to Party

Cust##-16

PO Number

GR##_101

Material

PRODTM-OO

Quantity

50

a) On the SAP Easy Access screen, choose Logistics —> Sales and Distribution —> Sales —> Order —> Create (transaction vaoi ). b) Enter the data from the the first four rows of the table and press ENTER. c) Enter the remaining data from the table and press ENTER. d) If A TP Check (Delivery Proposal screen) appears, choose Continue. e) Save your data. f) Record your sales order number. 2. What sales order number is created? Unique sales order number:_____________________________________________________



3. In SAP ERP, on the SAP Easy Access screen, start transaction code s x m b _ m o n i . Using XI Monitor, display that the message content was transferred from ERP. a) On the Integration Engine: Monitoring screen choose Monitor for processed XML Messages and then choose b) Choose

Execute.

Execute.

c) In the Monitor for Processed XML Messages screen, choose

Execute.

d) Verify that there are no green lightning bolt status icons (if there are, then raise your hand for instructor help).

Note:

fir indicates that the content was transferred but not executed. f i r indicates that the content was transferred and successfully executed in the system.

e) Exit the screen. 4. Using XI Monitor in SAP TM, display that the message content was received in SAP TM. a) In SAP TM, start transaction sxmb_moni . b) Choose Monitor for Processed XML Messages. c) Choose

Execute.

d) In the Monitor for Processed XML Messages screen, choose

Execute.

e) Verify that there are no green lightning bolt status icons. (If there are, then raise your hand for instructor help). f) Exit the screen. 5. Validate in NWBC that the OTR has been created for the sales order by reviewing the transfer requirements. a) In NWBC, choose ERP Logistics Integration —> Worklist —> Overview Transportation Requirements. b) If necessary, refresh the query. c) In the Original Order column, locate the number corresponding to your sales order. d) Drill into the document number for your sales order (click the TM OTR document number in the first column).6 6. Review the information in the General Data tab and compare it to the information contained in the original order in SAP ERP.



7. What TM Document Type was created for order type ZA##? OT##______________________________________________________________ 8. What is the life cycle status? In Planning._________________________________________________________ 9. What is the consumption status? Not consumed. This means no delivery has been received for this order yet.______ 10. Review the item data and compare it to the original order information in SAP ERP. 11. On the Document Flow tab, check whether a freight unit was created. a) Open the Document Flow tab. b) Verify that a freight unit has been created. 12. Open the newly created freight unit and review the data. a) In the Document Flow tab, click the freight unit number. b) On the General Data tab, review the locations, dates, and weight. c) Review the Label and verify that it corresponds to the sales order number. 13. Which document type(freight unit type) was used? FU##______________________________________________________________ 14. Which freight unit building rule was used? FUBR##_TM111______________________________________________________ 15. Review the item data. a) On the Items tab, scroll to the right to review the assigned requirement. b) Select the item and review the product details. 16. Repeat the steps in this exercise to create another sales order to generate another transportation requirement in SAP TM. Use the following data: Field

Value

Order Type

ZA##

Sales Organization

3000


10

Division

00

Sold-to Party

Cust##-17



Field

Value

PO Number

GR##_201

Material

PRODTM-OO

Quantity

50



Shipping Conditions The shipping condition of a sales order is one of the attributes that controls the transfer of sales orders to SAP TM. Therefore, changes to the shipping condition in a sales order can classify a sales order that has already been transferred from ERP as no longer relevant for TM or, on the contrary, a sales order which has not yet been transferred to TM as relevant. Changes to Shipping Conditions for Transferred Orders

Sales Order 5004

Sales Order 5004 Change Shipping

Shipping

Condition

Condition: 01

Shipping Condition: 03

A

V Sales Document Transfer SOrg. DChl Dv SaTy SC Ctrl Key lOOOl 01 01 ZTOR 01 0001 0001 01 01 ZTOR 02 0001

TMNo. C001 C002

Control Key Descnpoon Transfer Sales Order, O. Delvery; Order Sctiedukng nactve Transfer Sales Order, O. Delvery; Order Schedulng nactve

If

Cancel OTR


Figure 39: Changes to Shipping Condition for Transferred Orders

If a sales order is created that has a shipping condition assigned which is relevant for the transfer to SAP TM, the sales order creates an output message and an OTR is created in SAP TM. If the shipping condition is then changed in ERP, to a shipping condition that is not listed in the activation table for the transfer to SAP TM, the OTR is cancelled together with all freight units that were created out of the OTR. This is valid only for sales orders in ERP, for which a delivery has not yet been created. As soon as a delivery exists, no further messages for creation or cancellation are sent to TM. If the target TM system is changed based on a new shipping condition, a message is raised for the user. For exceptions, the user is informed that the change of shipping condition cannot be supported.

Note: Remember that if no shipping condition has been defined in the activation table for a sales order type, all shipping conditions are considered relevant for transfer to SAP TM.



Changes to Shipping Condition for Orders Awaiting Transfer

Figure 40: Changes to Shipping Condition for Orders Awaiting Transfer

As the activation of a sales order transfer can be dependent on the shipping condition of the sales order document, changes to an existing document need to be monitored and respected. Such change scenarios are considered in SAP TM. If a sales order has a shipping condition assigned which is not relevant for the transfer to SAP TM, neither an output message or an OTR is created in SAP TM. If the shipping condition is then changed (in ERP) to a shipping condition that is relevant for the transfer to SAP TM, a message is created and sent to SAP TM, and an OTR is created.




•


•




Unit 3 Lesson 5 Integrating Purchase Orders into SAP TM

LESSON OVERVIEW In this lesson, you learn about purchase orders, stock transport orders, and the workflow technology used in the integration of purchase orders. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Purchase Orders and Stock Transport Orders ] Internet Purchasng Detvery/Involce Perch. Org. Perch. Group Company Code

- 4500017127 Vendor Conditions

Texts

nL-VN-02 in. vendor 1 Commurcatton Partners

Address

Doc date

07 - 27-2011

Additional Data

Qrg Data

Status

Processno

TMStatus

lOOO' CCS Deutschland 002 Hamisch.H. 1000 CCS AG

Hf- S.. Itm A 1 Material Short Text PO Quantity 1 |l0 IIl-PROD-Ol Pchmer BJk (Int-lrboen. -------------------------------------------------------

0... C Detv. Date Net Pnce Curr... Per SOTO D 12-24-2011 1,000.00EW 1

0. .. Mad Group Pint TO Material Gro. Dresden

Star. U

—

*

General Data

Locations and DatesyTimes

B u s i e s t Ftotrer

Notes

Ooe tr-ens Flow

Source

Adnwiistrabve Del*

Destination Souks Location

iit-VN-02

DoBnabon LOCOSon

ML Vanda' 1

l>voo« ng Point

Address

Address S w a t N ous NumMr Potto) Ccdo Oty

Mom Sihm

7880

81812*

Sfonxnen

CM

CNno

StmeVHouB Number

Pottai Codo.’Oty

R ape"

="""r

item *4ersiefty

»

i j piMwtt 9 1 Scrodu

l_

10 1...

Mo_

Poly...

Bog-on

Bus n o s Tronsefion Document 1

Souiea Loco? on

Doamotion Location

XC-VK02

SP12O0

ML-VN-C2

SP12O0

□oiiuafy Oslo (Piom)

24 12 2011

Rad Ou

Ou

open Ou

G res

GnOB 1M*.

30

30

30

. 30 000 ...

30

30

30

xooo ...

LoJ

1

Figure 41: Purchase Orders

Like SAP ERP sales orders, purchase orders can also be integrated into SAP TM. The integration technology behind the integration of purchase orders is different to that behind the integration of sales orders. Instead of output management, workflow technology is used to create the XML message. However, once the XML message is created in SAP ERP it is sent to SAP TM and the same process is triggered as for a sales order.

0



As with a sales order, the message received in SAP TM is used to create an order-based transportation requirement. Recall from the previous lesson that SAP TM does not differentiate between inbound and outbound transports. This is reflected in the fact that OTRs are created for both purchase orders and sales orders. As you can also see in the figure Purchase Orders, in case of purchase orders, the source location, being the vendor, is defined on the header level of the OTR while the destination location is only defined on item level. This is because the receiving plant can differ from item line to item line while the vendor needs to be maintained on the header level of the purchase order. Freight unit building runs in exactly the same way as for sales orders. With purchase orders, you can decide whether you want to plan based on the ordered quantities of the purchase order, or with quantities confirmed by the vendor. In any case, the OTR is created based on the ordered quantities. However, if planning should only happen based on confirmed quantities, the freight unit will not be created until the vendor's confirmation has been posted. Stock Transport Orders

Stock transport orders, being a special type of purchase order, can also be transferred to SAP TM. As with sales orders and purchase orders, stock transport orders transferred to SAP TM create an OTR document. The delivering plant is the unique source location on the root level of the OTR. The receiving plants, which may differ from item to item, correspond to the destination locations on the OTR, which are stored on item level. Because stock transport orders are a special type of purchase order, the same workflow technology in SAP ERP is used to create the XML message that is transferred to SAP TM.



Workflow Technology

Purchase order created

Workflow started automatically

Events triggered

Event Type Linkages Object Category ObjectType

Event

Receiver Type

Type inka... Enable ev...

ABAP Class

▼ CL SE PUR PO UF OUT CHANGED

¥353800008

o

□

ABAP Class

▼ CL_SE_PUR_PO_WF_OUT CREATED

¥353800008

0

□

XML outbound message created and sent Figure 43: Workflow Technology

Unlike sales orders and outbound deliveries, purchase orders and inbound deliveries use different technologies to create the outbound XML message. The reason for this is that documents in the Material Management (MM) module of SAP ERP do not use output management in the same way as documents in the SD module. Once an MM document is created, a workflow is automatically started. This triggers different events that are configured in the workflow in SAP ERP. The triggered events have ABAP classes assigned which then create the outbound XML message. This XML message is sent to SAP TM to create the OTR (as is the XML message created for sales orders). In fact, the message created out of the purchase order is exactly the same as the one created out of a sales order.





Unit 3 Exercise 7 Create a Purchase Order

Business Example

To reduce costs within your transportation network, your company wants to manage not only outbound freight planning, but inbound freight planning as well. Your manager has tasked you with gaining an understanding how SAP TM can improve your company's chance of reducing overall transportation logistics costs. 1. In SAP ERP, create a standard purchase order using transaction ME21N. Field

Value

Vendor

PO Quantity

VEND-00-01 3000 TM 3000 RAWTM-00 10

Deliv. Date

Enter a date 5 weeks in the future

Pint.

3100 0001

Purch. Org Purch. Group Company Code Material

Stor. Location

2. Save the purchase order and make a note of the PO number. Review th e O rder-Based Transportation Requirem ent fo r a Purchase O rder

An order-based transportation requirement (OTR) is the starting point of the transportation process in SAP TM. The OTR is created automatically in the SAP TM system as a replication of a sales order, purchase order, or STO from the ERP system. 1. In NWBC, view the OTR for the PO you created in ERP. 2. Choose the General Data tab. What is the original ERP order type and what is the TM document type?

0



3. Does this OTR contain dangerous goods?

4. What is the life cycle status of this OTR?

5. Has a freight unit been created for this OTR? (Hint: Go to the Document Flow tab.)

6. Review the information in the Business Partner tab. What is the shipper ID and name?7

7. Under Items, select product item 10 and then choose the Locations and Dates/Times tab. What is the receiving plant?



Unit 3 Solution 7 Create a Purchase Order

Business Example

To reduce costs within your transportation network, your company wants to manage not only outbound freight planning, but inbound freight planning as well. Your manager has tasked you with gaining an understanding how SAP TM can improve your company's chance of reducing overall transportation logistics costs. 1. In SAP ERP, create a standard purchase order using transaction ME21N. Field

Value

Vendor

PO Quantity

VEND-00-01 3000 TM 3000 RAWTM-00 10

Deliv. Date

Enter a date 5 weeks in the future

Pint.

3100 0001

Purch. Org Purch. Group Company Code Material

Stor. Location

a) In SAP ERP, on the SAP Easy Access screen, choose Logistics —>Materials Management —*• Purchasing —>Purchase order —>Create —>Vendor/Supplying Plant Known (transaction code ME21N). b) Ensure standard po nb is selected for the Order Type field (shopping cart icon), and then enter the data as per the table. You may need to choose the Org. Data tab. 2. Save the purchase order and make a note of the PO number. Review th e O rder-Based Transportation Requirem ent fo r a Purchase O rder

An order-based transportation requirement (OTR) is the starting point of the transportation process in SAP TM. The OTR is created automatically in the SAP TM system as a replication of a sales order, purchase order, or STO from the ERP system. 1. In NWBC, view the OTR for the PO you created in ERP.

0



a) In NWBC, choose the ERP Logistics Integration —> Worklist —> Overview Transportation Requirements. b) Ensure that the All link for Order-Based Transportation Requirements is highlighted. c) Find the PO you created in the first part of this exercise, by searching for its number in the Original Order column. You may need to refresh the table. If so, choose the Refresh link in the top right of the screen. d) Highlight the row containing your PO and choose Display. 2. Choose the General Data tab. What is the original ERP order type and what is the TM document type? The original ERP order type is NB and the TM document type is NBLF.___________________ 3. Does this OTR contain dangerous goods? No. The checkbox for dangerous goods is not selected.________________________________ 4. What is the life cycle status of this OTR? In Planning___________________________________________________________________ 5. Has a freight unit been created for this OTR? (Hint: Go to the Document Flow tab.) Yes. For this OTR type, automatic freight unit building is activated. The existence of a freight*6 7 unit is also the reason for the life cycle status In Planning.______________________________ 6. Review the information in the Business Partner tab. What is the shipper ID and name? VEND-00-01, Manning Manufacturing._____________________________________________ 7. Under Items, select product item 10 and then choose the Locations and Dates/Times tab. What is the receiving plant? The receiving plant (destination location) is SP3100.




•




Unit 3 Lesson 6 Integrating Scheduling Agreements into SAP TM

LESSON OVERVIEW

This lesson outlines the integration of Scheduling Agreements into SAP TM. LESSON OBJECTIVES

After completing this lesson, you will be able to: •

Explain the generation of transportation requirements in SAP TM from scheduling agreements inSAPERP

Integration of ERP Scheduling Agreements into SAP TM A Scheduling Agreement is a framework purchase agreement or sales agreement under which materials are procured (on buying side). Products are delivered (on selling sides) on predetermined dates within a certain time period. The future delivery quantities and dates are entered as schedule lines in a delivery schedule. To reflect forecasted quantities and dates along with the more detailed requirements, two different types of scheduling agreement delivery schedules can be used. These are the following: •

Forecast delivery schedules (FRC schedules)

•

Just-in-time delivery schedules (JIT schedules)

The most important transactions related to scheduling agreements can be found at Logistics —*• Materials Management —*• Purchasing —>Outline Agreement —>Scheduling Agreement resp. Logistics —>Sales and Distribution —>Sales —>Scheduling Agreement. Up to release TM 9.2, integration of Materials Management (MM) and Sales and Distribution (SD) scheduling agreements were not supported by SAP TM. With SAP TM 9.3, scheduling agreements with their delivery schedules can be transferred between SAP ERP and SAP TM. You can control the communication between the two systems by using specific time horizons. Communication is based on eSOA services, supporting both process integration (PI) based communication and web services reliable messaging (WS-RM). The integration can be triggered by the creation of, or a change of delivery schedules. On the ERP side, the relevant development has been delivered with ECC6.17 SP06. Within SAP ERP, the functionality is controlled via business function LOG_TM_SAG_INT_l. New IMG activities allow control over how delivery schedules are transferred between ERP and TM. Batch reports are available to enable the transfer of schedule lines that were not relevant at the time of the initial transfer but become relevant over time. These batch reports are as follows: •

TMINT_SAGMM_TRANSFER (for MM Scheduling Agreements)



•

TMINT_SAGSD_TRANSFER (for Sales Scheduling Agreements)

Integration of ERP Scheduling Agreem ents into SAP TM (2 )

The integration of ERP Scheduling Agreements into SAP TM is based on the exchange of delivery schedules between a customer ERP system and a supplier ERP system. The relevant schedule lines are typically transmitted using business-to-business (B2B) communication. Both the customer and the supplier can make use of TM planning and execution capabilities in the following context: •

A customer can manage their inbound deliveries (purchasing) by creating corresponding transportation requirements in SAP TM. This is a MM Scheduling Agreement scenario.

•

A supplier can manage their outbound deliveries (sales) by creating corresponding transportation requirements in SAP TM. This is a Sales Scheduling Agreement scenario.

In both cases, the transportation planning is done based on the planned quantities and dates that are reflected by the FRC and JIT delivery schedules. Therefore the line items of these FRC and JIT delivery schedules are transferred from SAP ERP to SAP TM and stored as Order-based Transportation Requirements (OTR). The subsequent planning activities result in Freight Orders (FOR) created in SAP TM. These are used to define the schedule of the deliveries that shall be created in SAP ERP. To do so, a delivery proposal for the Freight Order is created in SAP TM and sent to SAP ERP. Based on this, an inbound or outbound delivery for the scheduling agreement is created on SAP ERP side, which in turn triggers the creation of a Delivery-based Transportation Requirement (DTR) in SAP TM.



Transfer of Delivery Schedule Items from SAP ERP to SAP TM

q

SAP ERP

Type

Date

Quantity

S chedule 01

Delivery Schedule

FRC

0 1 .0 5 .201x

50

S chedule 01

FRC

01.06.201x

55

S chedule 01

FRC

01.07.201x

60

S chedule 02

JIT

0 /l.05.201x

1 10

S chedule 02

JIT

08.05.201x

S chedule 02

JIT

12.05.201x

SAP TM

S chedule 02

JIT

16.05.201x

JIT

20.05.201x

10 |

S chedule 02

JIT

24.05.201x

15

Type

S chedule 02

JIT

1 5 20 1

S chedule 02

H orizon (o ptional): 10 days

on 04.05.201x

D e liv e ry S chedule

I |

D ate 04.05.201x

Transferred

I schedule lines

CD on 10.05.201x

Type

Date

Q u an tity

10

Schedule 02

JIT

04.05.201x

10

JIT

08.05.201x

15

12.05.201x

20

Q u a n tity

D eliv ery Schedule

S chedule 02

JIT

08.05.201x

15

Schedule 02

S chedule 02

JIT

12.05.201x

20

Schedule 02

JIT

Schedule 02

JIT

lG.05.201x

15

Schedule 02

JIT

20.05.201x

10

FRC: Forecast delivery schedules JIT: Just-in-time delivery schedules Figure 45: Transfer of Delivery Schedule Items from SAP ERP to SAP TM

The figure, Transfer of delivery Schedule Items from SAP ERP to SAP TM, shows a basic example of how delivery schedule line items are created and updated in SAP TM. The key steps are as follows: 1. Initial creation in SAP ERP A Scheduling Agreement is created in SAP ERP, with both a forecast (FRC) delivery schedule and a just-in-time (JIT) delivery schedule. 2. First transfer to SAP TM on 04.05.201x The relevant ERP schedule lines within the (optionally) defined time horizon are sent to SAP TM. This means that the planned quantities from that day until 10 days into the future are transmitted. The transfer of FRC delivery schedules depends on the customizing settings in SAP MM or SD. If no corresponding customizing has been maintained, the availability of schedules that are relevant to be transferred is the decisive factor. 3. Batch report run on 10.05.201x The batch report retriggers the transfer of schedule lines to SAP TM (for a delivery schedule that has already been transferred). The relevant time window is shifted accordingly. Previously transferred schedule lines on past dates are kept in SAP TM.



Materials Management Scheduling Agreements Using the integration of MM scheduling agreements to SAP TM, companies can provide their vendors with forecasts on the desired quantities of the relevant materials. Based on these forecasts, companies can plan their production and deliveries accordingly. To provide the respective vendors with that information, scheduling agreements with corresponding delivery schedules are created in SAP MM. These can then be integrated to SAP TM to plan and execute inbound transportation activities which are needed to physically provide the materials to the receiving plants.

ERP

Create MM scheduling agreement

Maintain delivery schedule for agreement item

(ME31L)

(ME38)

Create releases for delivery schedule

(ME38, ME84)

Transfer schedule lines to SAP TM

TM


Figure 46: Creation of Agreement Delivery, Schedule, and Releases

In SAP ERP, an MM scheduling agreement needs to be created first, using transaction ME31L. Within this scheduling agreement, single or multiple items can be inserted. As a basis for the integration into SAP TM, a delivery schedule for the relevant items needs to be maintained, using transaction ME38. The corresponding dates and scheduled quantities for the schedule lines can be entered by choosing Item —>Delivery Schedule in the top-bar navigation. In order to transfer schedule lines from SAP ERP to SAP TM, corresponding releases have to be created for the delivery schedule. This can be done either by entering transaction ME84 or by choosing Item —*• Generate Fore. Schd. resp. Item —► Generate JIT Sched. in the top-bar navigation of the delivery schedule maintenance screen (transaction ME38). When the schedule lines are transferred to SAP TM, an order-based transportation requirement (OTR) is created.



O rder-based Transportation R equirem ent from MM Scheduling A greem ent

Display ZAK1 OTR 31 Q00001?'l|(Ptnch.isinf] Scheduling Agreement ?).l)0Qn0QQ6‘i) I

*•

/E M

p4

General Data

Notes

Document Flow

Charge*

A dm nsteabrs Data

O rder Details

:i'-" ^

Lite Cycle Statue

Planned

Execution Statue

Execution Not Staled

ConsurcMn Status Custonw' PO teanOer OnJtf Type

ZAK

S*w t( Level

Consumed PartaH/

Detecry Stocked

•

Ptennrg Stock

•

NotDucted

Execution Olock

e

NotDucted

NotDueled

O rganizational Data Saee Oigmczoon Sales O lke Order Comoration AMowed

»

Sates Orouo

Parti* Detvery Conrol Pten On

Item teerarchy

Plan on Requested Quenme6

Item

Product

item Destitution

D

Dt#»ec, Scncrfje

Oetoeo ScModus Release Type

Dunnes® Source Location Traraachon Document Iter

Deetruooo Locaton

Detetry Dale (From)

Requested Quantity

Rtfl Cordoned Ouantty Ouantty Unt

•0

ZAK_H4AA_3®C7QSI3

ZAK_HAWA_3

1

Forecast C«‘

SUZAK_\fN001£2

PLZAK10O7OS13

3*

TO

a n S f'w aj# im t

to

ZAK_HAAA_3£07Q513

ZAK_HAWA_3

1

Forecast D
SUZAKVTteJOiaO

PLZAK10O7OS13

U03XI1S

13

TO

ao

10..

ZAX_KAAA_3®Q7Q513

ZAK_MAWO

1

Forecast Cell

SUZAK_VEN001®0.

PLZAK10O7Q513

1S03ZD15

IS

TO

• ,$2 Product

u<»

COft Ouantry Unrt

Figure 47: Order-based Transportation Requirement from MM Scheduling Agreement

Based on the delivery schedule previously maintained in SAP MM, an Order-based Transportation Requirements (OTR) is created in SAP TM. In the OTR, the scheduling agreement and the delivery schedules with schedule items are stored as follows: •

The MM Scheduling Agreement is referenced as original order type and with its original ERP ID.

•

The delivery schedules are referenced with their original ERP IDs on OTR item level.

•

The relevant release type (Forecast delivery schedule or Just-in-time delivery schedule) is also referenced on OTR item level.

Freight units can be created similarly to OTRs with other types of original order types. In order to plan the freight units created with the OTR, the Transportation Cockpit can be accessed and then (among other options) drag & drop can be used to assign them. For example, to a vehicle resource. Based on the planning results, the delivery proposal functionality can be used in SAP TM to trigger the creation of inbound deliveries in SAP ERP.



Setup of MM Scheduling Agreement Integration

SAP ERP Customizing Settings

Figure 48: Setup of MM Scheduling Agreement Integration

The integration of MM Scheduling Agreements into SAP TM requires a few basic customizing settings. For instance, it needs to be configured which purchasing document types andcorresponding inbound deliveries shall be transferred from ERP to TM. In SAP ERP, you need to define the TM relevance for MM scheduling agreements using control keys in IMG activity IMG —* Integration with Other SAP Components —>Transportation Management —>Logistics Integration —>Activate Transfer of Purchasing Documents. This is the same activity that is used to activate the transfer of purchase orders to SAP TM. In this customizing activity, you can maintain the relevant Scheduling Agreement type (indicated as purchasing order type) to be used for the transfer to SAP TM. This setting also includes the corresponding inbound deliveries to be transferred Furthermore, you can optionally define a time horizon in number of days to restrict the relevant future schedule lines of a scheduling agreement depending on their date in IMG activity IMG —*• Integration with Other SAP Components —>Transportation Management —*• Logistics Integration —>Define Settings for MM Scheduling Agreements Integration. The calculation always starts from the current date. A set of four parameters (purchasing document type, purchasing organization, purchasing group, receiving plant) allows for further specification of which combination this setting applies. In the same customizing table, it is also possible to specify the relevant scheduling agreement release types. Based on this setting, the system decides whether JIT delivery schedules or FRC delivery schedules (or none) will be transferred to SAP TM. In addition, you should define at least one release creation profile for MM scheduling agreements in IMG activity IMG —*• Materials Management —>Purchasing —>Scheduling Agreement —*■ Maint. Rel. Creation Profile for Sched. Agmt. with Rel. Docu. In this configuration table, you can



determine which criteria are used to generate releases for a scheduling agreement, mainly the periodicity of the releases and the way in which the quantities are aggregated. As schedule lines need to be released to trigger the transfer to SAP TM, the definition of a release creation profile is a necessary step to determine which criteria are applied to generate such releases against a scheduling agreement. Besides general parameters like the creation strategy and so on, the aggregation and release horizon as well as the release creation periodicity can be defined in the creation profile. Finally the release creation profile is assigned to a scheduling agreement item. In SAP TM, you need to define at least one OTR (Order-based Transportation Requirement) type in IMG activity IMG —*• Transportation Management —>Integration —>ERP Logistics Integration —>Order based Transportation Requirements —>Define Order Based Transportation Requirements. In this configuration table, you can maintain the relevant OTR type(s) to be used for the integration of MM Scheduling Agreements. Furthermore you need to define at least one DTR (Delivery-based Transportation Requirement) type in order to enable the creation of DTRs based on ERP deliveries in the MM scheduling agreements scenario. Sales Scheduling A greem ents

Using the integration of sales scheduling agreements to SAP TM, companies can offer a just-intime (JIT) oriented delivery service to its customers. They provide their forecasts based on which the customer can plan the production and initiate the procurement accordingly. On the basis of such delivery schedule data received from customers by EDI, scheduling agreements with corresponding delivery schedules are created in SAP SD. These can then be integrated to SAP TM to plan and execute outbound transportation activities which are needed to physically provide the materials to the respective consignees.

Create sales scheduling agreement

Maintain delivery schedule for agreement item

(VA31)

(VA31)

VHHP I_____ --------- --------------------

Transfer schedule lines to SAP TM

TM


__________________________ ________ ______ r Figure 49: Creation of Agreement and Delivery Schedule



In SAP ERP, a sales scheduling agreement needs to be created first, using transaction VA31. Within the scheduling agreement, one or multiple item(s) can be inserted. As a basis for the integration into SAP TM, a forecast delivery schedule and/or a JIT delivery schedule with schedule lines can be defined for the relevant items of the scheduling agreement. This can be done directly in transaction VA31, no separate transaction is used. Other than for MM scheduling agreements, it is not required to create releases for sales scheduling agreements. When the schedule lines are transferred to SAP TM, an Order-based transportation requirement (OTR) is created. Order-based Transportation Requirements from Sales Scheduling Agreement Display US01 Conf Quan 310000021 ^ (Sales Scheduling Agreement 30000082)~|

-

p

General Data

euwms Pal

1 i" e-.

Note*

Document Flo*

Internal Charges

O rder D etails

Cl

Adm.ru**a live Data S ta tu s e s

Document T,pe

U901 Sare# Scheaeng Agreement

Sennce Level

mFânrmg

E»«cubon Stahs

Exec u*on Not Started

Consumption Status

|

Custom** f O xtoTm

UK Cycle Status

Snipping

Partiaty

•

Not Stocked

Planting B eck

■

Not B o d e d

Execution (Sock

•

Not B o d e d

12 S to w 'd

Consumed

Oetveny BBCMO

O rganizational Data

Oetoery Pnonty

Pnorty 1

Sales Orgarszatcn

STM

SIT Sunon Enpr Corp

S a h a O M te

STT-

S a m Office STTi

Trarapoftaien Mode Order cononaoon Aimed

Pan*Oetvery Corwot Plan On

SB

sa*s Group

P a n * D e i .e v Plan o r Requested Q u ard b m

tocoSerms Incoisim

OOP

Delivered Duty P a d

Q uantities 40

M3

Gross Wecrc

40

TO

Nstwe^r*

40

TO

item ►eenartrtr

item

»

Product Schedule Lne

B

Gross v o u n e

Product

«*ro Descnpeon

to

2AK_HA«A_3ea7QS13

10..

2AK.HAWA.39070S13

into**™ Location (Free Tent)

MC02

N otes

O

Dei.**, Scnedue Reem c Type

ZAK_HAWA_3

s a - . cx . c;

JuSHn-Trw

3PZAK3©Q7Q513

CUZAKS9Q7QS13

50

TO

60

TO

ZAK.HAWA.3

s a '_ ck _c:

JjC .ln.-rr*

SPZAK3QQ7QS13

CUZA»C4^Q7Q613

21 04 201 £

20

TO

20

TO

9PZA»C3®07OS13

CUZA40®070513

24 04 2015

20

TO

20

TO

SPZA»0©Q7Q513

CUZAKS^Q7QS13

i» 04 2015

20

TO

20

TO

3U Schedule Ire

10

7AK_HAiVA_3Q O70? 13

ZAK_HAWA_3

F.A’ . r x . c ;

JuK-ln-'m*

<90 Schedule m e

10..

ZM_MAAA_3©07QS13

ZAK_HAWA_3

SA’ .CX.Ci

J j« In * n c

Ousress Sovxc* Loceear Transacson Document Ran

O a fw an locason

Deirrory Dare

Requested OuarWty

Confirmed Red Cuartx, Quarety UnH

Devrery S
Coti Ouarr

Figure 50: Order-based Transportation Requirements from Sales Scheduling Agreement

Based on the delivery schedule previously maintained in SAP SD, an Order-based Transportation Requirement (OTR) is created on TM side. In the OTR, the scheduling agreement and the delivery schedules with schedule items are stored as follows: •

The Sales Scheduling Agreement is referenced as original order type and with its original ERP ID.

•

The Delivery Schedules are referenced with their original ERP IDs on OTR item level.

•

The relevant release type (Forecast delivery schedule or Just-in-time delivery schedule) is also referenced on OTR item level.

Freight units can be created similar to OTRs with other types of original order types. Transportation planning can be executed for the Freight Units (FUs) of the Order-based



Transportation Requirements (OTRs). Based on the planning results, the delivery proposal functionality can be used in SAP TM to trigger the creation of outbound deliveries in SAP ERP. Setup of Sales Scheduling Agreement Integration

The integration of Sales Scheduling Agreements into SAP TM requires a few basic customizing settings. For instance, configuration is needed for to which sales document type(s) & corresponding outbound deliveries shall be transferred from ERP to TM. In SAP ERP, you need to define the TM relevance for sales scheduling agreements using control keys in IMG activity IMG —* Integration with Other SAP Components —> Transportation Management —» Logistics Integration —>Activate Transfer of Sales Documents. This same activity that is used to activate the transfer of sales orders to SAP TM. In this customizing activity, you can maintain the relevant Scheduling Agreement type (indicated as sales document type) to be used for the transfer to SAP TM. This setting also includes the corresponding outbound deliveries to be transferred. Furthermore, you can optionally define a time horizon in number of days to restrict the relevant future schedule lines of a scheduling agreement depending on their date in IMG activity IMG —*• Integration with Other SAP Components —> Transportation Management —*• Logistics Integration —>Define Settings for Sales Scheduling Agreements Integration. The calculation always starts from the current date. A set of five parameter (sales document type, sales organization, distribution channel, division, delivering plant) allows to further specify for which combination this setting applies. In SAP TM, you need to define at least one OTR (Order-based Transportation Requirement) type in IMG activity IMG —*• Transportation Management —>Integration —>ERP Logistics Integration —>Order based Transportation Requirements —>Define Order Based Transportation Requirements. In this configuration table, you can maintain the relevant OTR type(s) to be used for the integration of Sales Scheduling Agreements.



Furthermore you need to define at least one DTR (Delivery-based Transportation Requirement) type in order to enable the creation of DTRs based on ERP deliveries in the sales scheduling agreements scenario.





Unit 3 Exercise 8 Create a Scheduling Agreement

Business Example

Using the integration of sales scheduling agreements into SAP TM, your company can offer a just-in-time (JIT) oriented delivery service to its customers. By creating a sales scheduling agreement, you provide your forecasts on which the customer can plan the production and initiate the procurement accordingly. The products are delivered on predetermined dates within a certain time period. The sales scheduling agreement are integrated to SAP TM to plan and execute outbound transportation activities which are needed to physically provide the materials to the respective consignees. Task 1: Create a Scheduling Agreement

1. In SAP ERP, create a scheduling agreement. Include the settings from the following tables: Sched. Agreement Type

SAG

Sales Organization

3000


10

Division

00

Sales Office

3000

Sold-to Party

15001

PO Number

Sched Agreem ##

Valid from

Today

Valid to

Today +1 month

Material

PRODTM-OO

Rounding Qty

100

Customer material number

PRODTM-OO

2. Create a forecast delivery schedule. Use the following data:

0

Dlv. schedule

SAG_##

Dlv. sched. date

Today —1 month

Date

Today +1 week



Order quantity

100

3. Create a just in time (JIT) delivery schedule. Use the following data: Dlv.schedule

SAG_##

Dlv.sched.date

Today —1 month

JIThor.

Today +3 weeks

Date

Today +3 working days

Order quantity

40

Date

Today +1 week

Order quantity

40

4. Save your scheduling agreement and note the document ID.

Task 2: Check transfer of Scheduling Agreement in SAP TM

1. In SAP TM, check the OTR type determination condition for a mapping entry for sales scheduling agreements. 2. Check that your scheduling agreement was transferred to SAP TM and created an Orderbased Transportation Requirement (OTR). Check which delivery schedule was transferred to SAPTM. 3. Check that Freight Units were created for the items.



Unit 3 Solution 8 Create a Scheduling Agreement

Business Example

Using the integration of sales scheduling agreements into SAP TM, your company can offer a just-in-time (JIT) oriented delivery service to its customers. By creating a sales scheduling agreement, you provide your forecasts on which the customer can plan the production and initiate the procurement accordingly. The products are delivered on predetermined dates within a certain time period. The sales scheduling agreement are integrated to SAP TM to plan and execute outbound transportation activities which are needed to physically provide the materials to the respective consignees. Task 1: Create a Scheduling Agreement

1. In SAP ERP, create a scheduling agreement. Include the settings from the following tables: Sched. Agreement Type

SAG

Sales Organization

3000


10

Division

00

Sales Office

3000

Sold-to Party

15001

PO Number

Sched Agreem ##

Valid from

Today

Valid to

Today +1 month

Material

PRODTM-OO

Rounding Qty

100

Customer material number

PRODTM-OO

a) In SAP ERP, go to Logistics —>Sales and Distribution —>Sales —>Scheduling Agreement —> VA31 Create. b) Create the settings from the first table in Step 1.

0



c) Choose Enter. d) Input the data from the second table in Step 1. e) Choose Enter. In case a warning message states that there is a scheduling agreement with the same data, choose Enter again to confirm the warning message. 2. Create a forecast delivery schedule. Use the following data: Dlv. schedule

SAG_##

Dlv.sched.date

Today —1 month

Date

Today +1 week

Order quantity

100

a) Highlight item 10, and choose ForeDISch. b) Enter the data from the table in Step 2. c) Choose Enter. 3. Create a just in time (JIT) delivery schedule. Use the following data: Dlv.schedule

SAG_##

Dlv.sched.date

Today —1 month

JIThor.

Today +3 weeks

Date

Today +3 working days

Order quantity

40

Date

Today +1 week

Order quantity

40

a) On the JIT delivery schedule tab, enter the data from the table in Step 3 b) Choose Enter. 4. Save your scheduling agreement and note the document ID. a) Choose Save. b) Write down the document number.

Task 2: Check transfer of Scheduling Agreement in SAP TM

1. In SAP TM, check the OTR type determination condition for a mapping entry for sales scheduling agreements.



a) In SAP TM, in NWBC, go to Application Administration —>General Settings —>Conditions —>Display Condition. b) Enter the condition name zotr_type ,and choose Continue. c) In the decision table, scroll to the end of the table. Review the entry for Original Order Category Sales Scheduling Agreement (734) and ERP Order Type SAG. 2. Check that your scheduling agreement was transferred to SAP TM and created an Orderbased Transportation Requirement (OTR). Check which delivery schedule was transferred to SAPTM. a) In NWBC, go to ERP Logistics Integration —> Worklist —>Overview Transportation Requirements. b) In the Original Order column, look for your scheduling agreement number (in case you can't find it, choose Refresh). c) Select the corresponding line and choose Display. d) Review the data displayed on the General Data tab. e) Scroll down to the Items section. Two schedule lines should be displayed; one for each schedule line in the JIT schedule. 3. Check that Freight Units were created for the items. a) Navigate to the Document Flow tab. Two freight units are shown as successor documents. b) Open the first freight unit, and review the General Data and Items.




•

Explain the generation of transportation requirements in SAP TM from scheduling agreements inSAPERP



Unit 3

Learning Assessment

1. Both for order-based and delivery-based transportation requirements, SAP TM provides type Customizing to define certain parameters that influence how the system processes these business documents. Determine whether this statement is true or false. | True False 2. Which settings can be maintained in the transportation requirement type Customizing? Choose the correct answers. | A Freight Unit Building Rules B Charge Calculation Profile | C Planning based on requested or confirmed quantities 3. Transportation requirement types can be determined in SAP TM based on conditions. Determine whether this statement is true or false. | True False 4. Which settings are necessary in SAP ERP to enable order and delivery integration with SAP TM? Choose the correct answers. | A Control Keys B Business Functions | C Type Customizing

0



5. Which settings can be maintained in a control key? Choose the correct answers. | A TM Number B Outbound Delivery to SAP TM C Purchase order to SAP TM D Sales order Scheduling — Active 6. Based on which attributes can the integration of sales orders be maintained? Choose the correct answers. | A Shipping Condition B Division C Sales Organization D Ship-to Party 7. Which output types are used for order and delivery integration to SAP TM? Choose the correct answers. | A TRSO B TRDO | C TRRO 8. Messages that have been forwarded to the Postprocessing Desktop can also be restarted from the monitor for processed XML messages. Determine whether this statement is true or false. | True False



9. Changing the shipping condition after sales order transfer doesn’t have any impact on TM integration. Determine whether this statement is true or false.

□ □

True False

10. Purchase order integration to SAP TM is achieved using output control. Determine whether this statement is true or false.

□ □

True False

11. On which level are locations stored on OTRs? Choose the correct answers. □

A For sales orders, source locations are stored on root level.

□

B For sales orders, destination locations are stored on root level.

□

c For purchase orders, source locations are stored on item level.

□

B For purchase orders, destination locations are stored on item level.




1. Both for order-based and delivery-based transportation requirements, SAP TM provides type Customizing to define certain parameters that influence how the system processes these business documents. Determine whether this statement is true or false. 0

True False

2. Which settings can be maintained in the transportation requirement type Customizing? Choose the correct answers. |~X~| A Freight Unit Building Rules B Charge Calculation Profile

|~xj

C Planning based on requested or confirmed quantities

3. Transportation requirement types can be determined in SAP TM based on conditions. Determine whether this statement is true or false. [x ] True False

4. Which settings are necessary in SAP ERP to enable order and delivery integration with SAP TM? Choose the correct answers.

|~xj

A Control Keys

|~X~| B Business Functions C Type Customizing



5. Which settings can be maintained in a control key? Choose the correct answers. | A TM Number [x ] B Outbound Delivery to SAP TM [x ] C Purchase order to SAP TM

[~xj

D Sales order Scheduling — Active

6. Based on which attributes can the integration of sales orders be maintained? Choose the correct answers. [x ] A Shipping Condition [x~| B Division

[~xj

C Sales Organization D Ship-to Party

7. Which output types are used for order and delivery integration to SAP TM? Choose the correct answers. [x ] A TRSO \x \ B TRDO \x \ C TRRO

8. Messages that have been forwarded to the Postprocessing Desktop can also be restarted from the monitor for processed XML messages. Determine whether this statement is true or false. True \x \ False Correct.



9. Changing the shipping condition after sales order transfer doesn’t have any impact on TM integration. Determine whether this statement is true or false.

□

True

0 False Correct. If no integration is set up for the new shipping condition, the OTR is canceled. 10. Purchase order integration to SAP TM is achieved using output control. Determine whether this statement is true or false.

□

True

0 False Correct. Workflow technology is used for MM documents. Output control is only used for SD documents like sales orders. 11. On which level are locations stored on OTRs? Choose the correct answers.

□

A For sales orders, source locations are stored on root level.

0

B For sales orders, destination locations are stored on root level.

□

C For purchase orders, source locations are stored on item level.

0

D For purchase orders, destination locations are stored on item level.



UNIT 4

Transportation Requirement Processing

Lesson 1 Integrating Routing Information from SAP ERP

126

Lesson 2 Retaining Consistency Across Systems Exercise 9: Manage Cross-System Changes

132 139

Lesson 3 Scheduling Sales Orders with SAP TM

144

UNIT OBJECTIVES

0

•

Determine routing based on Incoterms

•

Manage cross-system visibility

•

Manage cross-system changes

•

Schedule sales orders



Unit 4 Lesson 1 Integrating Routing Information from SAP ERP

LESSON OVERVIEW In this lesson you learn about the integration of routing information, stage building and the use of incoterms, incoterm locations, and handover locations. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Incoterm s

Incoterms are intended to clearly communicate the tasks, costs, and risks associated with the transportation and delivery of goods. They define a contractual agreement between supplier and consignee to determine who is responsible for which stage of the transport and where and when the responsibilities of each partner start and end. Incoterms can be maintained in Customizing



for SAP TM under SAP Transportation Management —> SCM Basis —> Master Data —> Define Incoterms. Incoterm s in SAP TM Delivery Custom izing

Table 3: Incoterms Included in SAP TM Delivery Customizing SAP TM delivery Customizing contains several common incoterms, as outlined in the following table: Incoterm

Description

EXW

Ex Works

FAS

Free Alongside Ship

FOB

Free On Board

CFR

Cost and Freight

CIF

Cost, Insurance, and Freight

CPT

Carriage paid To

DES

Delivered Ex Ship

DEQ

Delivered Ex Quay

DAF

Delivered At Frontier

DDP

Delivered Duty Paid

DDU

Delivered Duty Unpaid

FCA

Free Carrier

CIP

Carriage and Insurance Paid To



Incoterm Locations

Display Freight Unit - Inbound Logistic 100000200 0 Edit III <\> III Follow Up^| | Direct Shipment A ▼

General Data

B usiness Partner

S tages

Document Flow

Sent

Notes

Attachments

Destination

Source

Location:

IIL-VN-02

Location:

IIL Vendor 1

7589 Mam Street/ Additional Data

Label: Freight Unit Type:

IIL1

Freight Unit - Inbound Logistic

Movement Type:

Incoterm Location:

Shipping Point Dresden

Required Capacity

4500017173

Shipping Type:

Incoterm:

SP1200

Pilmzerstr 245 / 01069 Dresden

Weight:

13.700

KG

Volume:

10

M3

Pieces:

1

PC

Density Factor: FOB

1/0.7

Free on Board

IlL-CNSHA

General Data Insert,

Merge ,

Stacjies

Business Partr

issign Fi ght Document

Stage

Source Location

Destination Location

10

IIL-VN-02

IlL-CNSHA

20

IlL-CNSHA

SP1200

A(

Figure 53: Incoterm Locations

Some of these incoterms require a location, at which tasks, costs, and risks are transferred from the seller to the buyer. The incoterm location is the place where the goods are physically handed over and where the responsibilities for the goods change. This setting (incoterm location) is part of the Customizing for SAP TM. If one of the SAP-delivered incoterms is used in an SAP TM document, it is mandatory to enter the incoterm location. The incoterm location is a master data location in SAP TM and can be used for routing purposes. In case of SAP ERP order integration with SAP TM, the Incoterms (Part 2) field can be used to define the incoterm location. You can map Incoterms (Part 2) to an SAP TM master data location in Customizing for SAP TM under SAP Transportation Management —> Transportation Management —> Master Data —> Transportation Network —> Assign Location to Incoterm Location. You can build two stages — from the source location to the incoterm location, and from incoterm location to the destination location.



Stage Building Based on Incoterms

In SAP TM, you can build stages based on the incoterm location. The Incoterm Location Stage Building field in the OTR/DTR Type customizing defines how stages are built based on source location, incoterm location, and destination location. The stage building rule values define which stage(s) will be built in OTRs and/or DTRs if the incoterm location is used for stage building. The system uses the incoterm location for stage building if the incoterm has set the Incoterm Location flag (a flag that indicates that you must enter a location with this incoterm) in the SAP TM system (and usually also in the SAP ERP system). If no incoterm is specified, the system does not use the incoterm location for stage building and the system creates only one stage from the source to the destination location. If an incoterm is specified but this incoterm has not set the Incoterm Location flag, the system does not use the incoterm location for stage building. Instead the system creates only one stage from the source to the destination location. Possible Stage Building Rules

•

Two Active Stages — Type 1 and Type 2 Two planning-relevant stages are created with this setting.

•

Source Location to Incoterm Location — Type 1 One stage is created, from the delivering plant (source) to the incoterm location.

•

Source Location to Incoterm Location — Type 2



Two stages are created — an active stage from the source location to the incoterm location, and an additional stage, which is not relevant for planning, from the incoterm location to the destination location. •

Incoterm Location to Destination — Type 1 One stage is created, from the incoterm location to the receiving plant (destination). This rule is relevant, for example, to a consignee who plans only the route from the incoterm location to point of goods receipt.

•

Incoterm Location to Destination — Type 2 Two stages are created — an active stage from the incoterm location to the destination location, and an additional stage, which is not relevant for planning, from the source location to the incoterm location.

Handover Location

Incoterms Incoterm Incoterm Location incoterm Location (Free Text)

FOB

Free on Board

General Data

IIL-CNSHA

Business Pan

Insert d Merge A ^

TM

S ta g e s

CN SHA HOL

Stage

Source Location


10

IIL-VN-02

CN_SHA_HOL

20

CN_SHA_HOL

SP1200

Figure 55: Handover Location

As of SAP TM 9.1 a handover location (HOL) can be used when integrating external SAP ERP purchase orders to SAP TM. This can be used instead of the Incoterms (Part 2) field. Usage of the \ncoterms(Part 2) field for stage building is still supported. If both Handover Location and \ncoterms(Part 2) fields are filled, the handover location is used for stage building. Handover locations can be maintained in SAP ERP as vendor master data, and this can be transferred to SAP TM using the Core Interface (CIF) to create location master data in SAP TM. Using this new (SAP TM 9.1 )solution means that mapping between lncoterms(Part 2) and SAP TM location master data is no longer necessary. This ensures a reliable interface between SAP



ERP and SAP TM, without failed message processing due to failed mappings from Incoterms (Part 2) to location master data in SAP TM. If an SAP ERP document has an incoterm with an active LOC flag (meaning the lncoterms(Part 2) field is filled), and if a handover location has also been specified, the Handover Location field takes precedence over the lncoterms(Part 2) field. This means that the incoterm location can be determined in one of the following ways: •

Based on the lncoterms(Part 2) field of the SAP ERP document To determine a location from the lncoterms(Part 2) string you must assign a location to an incoterm location.

•

Based on the handover location (HOL) of the SAP ERP document. No additional mapping is needed. The HOL is represented as a location of type 1011 (Vendor) in the SAP TM system.

In addition to the handover location, a Handover Date field for delivery schedule of the PO is available. After the handover date is transferred to SAP TM, it is available in the OTR (and is used for freight unit building). After the planning and creation of deliveries in SAP TM, the handover location is sent back from SAP TM to SAP ERP and the ERP inbound delivery is updated accordingly. The handover location and date are copied into the header level of the SAP ERP inbound delivery upon creation. When the SAP TM system receives handover locations from an SAP ERP order, the SAP TM system decides whether to build one or two stages and whether to designate one of them as “statistical” . If two stages are built and neither is designated “ statistical", then the logic of delivery creation is the same as that for a scenario without handover location. This means that the original source and destination locations from the SAP ERP order are relevant for transportation planning and for the date and time fields in the delivery proposal. If two stages are built and one is designated as “statistical", or only one stage is built, then the handover location becomes relevant for transportation planning and delivery proposal. LESSON SUMMARY You should now be able to:•

•




Unit 4 Lesson 2 Retaining Consistency Across Systems

LESSON OVERVIEW In this lesson you learn about keeping SAP ERP and SAP TM in sync, specifically in relation to cross-system document flow, maintaining cross-system visibility, and change control. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Document Flows »

General Data

>1

t>»

Business Partner

Items

Stages

Utilization

Docum ent FlOW

Subcontracting

Administrative Data

Charges

Execution

Notes

Display

Document Hierarchy

Business Document Type (Descnpbon)

Business Document

Business Document Life Cycle

» OCa TM100 Freight Order ORPOO6100000700

TM100 Fre-ght Order GRPOO

6100000700

In Process

DOT Freight Unit Type

300001852

In Process

Delivery-Based Requirement

1190000040

Planned

Outbound Delivery

80120196

TM111 GR99 Order-Based Transp Rqmnt

1100000394

Saes Order

15013

DOT Freight Unit Type

300001853

In Process

Delivery-Based Requirement

1190000041

Planned

Outbound Delivery

80120197 C X

TM111 GR99 Order-Based Transp Rcmnt

1100000395

Saes Order

15014

(S Predecessor Bus-ness Documents » oca DOT Freight Umt Type 300001852

w Delivery-Based Requirement 119000CC40 (Outbound Delivery 80120196) Outbound Delivery 80120198 » TM111 GR99 Oroer-Based Transp Rgmnt 1100000394 (Sales Order 15013) Sates Order 15013

w OCa DOT Freight Umt Type 300001853 » Delivery-Based Requirement 1190000041 (Outbound Delivery 80120197) Outbound Delivery 80120197 * TM111 GR99 Order-Based TranspRomnt 1100000395 (Sales Order 15014) Sates Order 15014

Completed

'Vk

Completed

^

w 3) Successor Business Documents

I

ERP Smpment

ERP Shipment

w Default Freight Settlement Document 8100000070 Seduce Entry Sheet 100000218 Purchase Order 4500017179

Default Freight Settlement Document

8100000070

Servoe Entry Sheet

100000218

Purchase Order

4500017179

Jj Cf

Delivery 80120197 Display: Overview Menu,

4 [ Back

Outbound aefrv

00120197

Smp-to party

CUST99-17

|

Hem Oveiview

|

Planned Gl

Picking 2 8 .08.2014

Actual Gl date

Em

Cancei

System A Display<->Change

Document Oats 3

i Accruals Posted

Jj

other OuBsound Delivery

1 9 .08.2014

Douglas Corp/599 Northwestern/LouisviHe KY40212

Loading

Transport

Status Overview

00:00

Total Weight

00:00

No of packages

Goods Movement Data

5 .0 0 0

TMSM m

lb

[q

All Items Rm ifl

Material PRgpm-M

Deiiv Qty so

Un box

Bat RCa

Description TM100 Product 1 0 -On

Pallets

TAN

Figure 56: Document Flow in SAP TM



Business documents in SAP TM comprise a document flow that shows a list of preceding and succeeding documents (related to the current document). The document flow is available for order-based and delivery-based transportation requirements, for freight units, freight orders and freight bookings, and further documents. For documents included in the document flow, relevant status information, such as life cycle status, is displayed. The document flow also includes the corresponding SAP ERP documents such as sales or purchase orders, outbound or inbound deliveries, shipments, and other documents. Document IDs are displayed as links and can be used to display the corresponding document in full. You can access both the SAP TM and SAP ERP business documents if there is a trusted relationship between the SAP TM and SAP ERP systems and if your user exists in both systems. This provides you with an overview of all relevant SAP ERP documents directly within SAP TM, and enables you to navigate to the SAP ERP documents to review the document details. Document Flow in SAP ERP TM Docum ent Flow fo r Sales Order 1 5 0 1 4

Consumption Status

Sales Document

Consumed Completely

Tendenng Status

Life Cycle Status

In Process

Execution Status

Not Started

Invoicing Status

Confirmation Status

No Confirmation Yet

Execution Block

Not Blocked

Subcontracting Sts

Carrier Assigned

Planning Block

Not Blocked

St*]'M U

IQ I'lRjTÎ 11 TMDocument || ERPDocument || DisplayFUItems 11j

ERP-TM Document Flow - ©< Sales Order w 5 ^ Oder-Based Transportation Requirement ” Q Sales Order Item • 3 Schedule Line ~ [g^ Delivery-Based Transportation Requrement * Q Outbound Defcvery Item * ©• Freitfit Unit • 6 ^ Freight Oder • Freight Settlement Document

ERP Doc 15014 15014 15014 15014 80120197 80120197 80120197 80120197 80120197

ERP Item

ScM Lne

10 10

100001

10 10 10 10

Conf. Sts BTD ID Status Life Cycle Subcon.Sts 15014 £• In Process Carrier Assigned No Confirmation Yet In Process Carrier Assigned No Confirmation Yet 1100000395 1100000395 & In Process Carrier Assigned No Confirmation Yet 1100000395 1190000041 £ ■ In Process Carrier Assorted No Confirmation Yet 1190000041 £> In Process Carrier Assigned No Confirmation Yet 300001853 £> In Process Carrier Assigned No Confirmation Yet In Process Carrier Assigned No Confirmation Yet 6100000700 8100000070 f

Exec. Sts Not Started Not Started Not Started Not Started Not Started Not Started Not Started

© ■Status fw Freight Order 6100000700

Status Name

Status Desorption

LIFECYCLE

In Process

EXECUTION

Not Started

CONFIRMATION

No Confutation Yet

SUBCONTRACTING

Carrier Assigned

BLK_EXEC

Not Blocked

BLK_PLAN

Not Blocked

Figure 57: Document Flow in SAP ERP

The SAP TM document flow for a specific SAP ERP order or delivery can be displayed in the SAP ERP system (available as of SAP enhancement package 6 for SAP ERP 6.0, support package 4). SAP TM provides SAP ERP with information about the documents created for an order or delivery (for example, freight units, freight orders, and freight settlement documents) and also about the status of the documents (for example, life cycle status and execution status). This gives the user an overview of the entire ERP-TM process for an individual SAP ERP document and enables the user to track the status of document processing in SAP TM from the SAP ERP system. You can see the SAP TM document flow for sales orders, purchase orders, outbound and inbound deliveries on header level and item level. Selecting a TM document and then choosing the TM



Document button opens the corresponding TM document in a separate window. Selecting a freight unit and then choosing the Display FU Items button shows the FU details on item level. Change Control SAP ERP

SAP TM

Read only Order / Delivery

Transportation Requirement

Quantity Change, Date Change, Location Change, 1 New Item, ... 2 ____________ J

2l

I

Configuration

Automatic Updates

r

Freight Order / Booking

Freight Unit

TJ

)

Evaluate Changes Determine Strategy ^

----

----

d

(r) Remove Plan, Stop Tendering, Inform Carrier, Send Alert, ...

)

Figure 58: Change Control

Whenever there are changes to transportation requirements, for which follow-up documents already exist, SAP TM provides support to react to these changes. For example, if the quantity of a sales order changes, and that sales order is already planned in SAP TM, you might have to adjust your transportation plan. SAP TM provides a configurable, flexible framework to support change processes. In the example of a quantity change, the system can check the resource capacity and remove freight units from planning if the resource is overloaded. In addition, a user could be informed of changes via alert. In relation to an SAP ERP order and delivery integration, ERP is the leading system. That means, all changes to the affected objects need to be performed in the SAP ERP system. The orderbased and delivery-based documents in SAP TM are read-only documents and can not be changed manually by the user. Whenever an SAP ERP order or delivery is changed, an update message is automatically sent to SAP TM to update the corresponding transportation requirement. SAP TM then automatically updates the assigned freight units to keep transportation requirements and freight units aligned. Logistics integration with SAP ERP supports changes to and the deletion of orders in SAP ERP. It also supports changes to and the deletion and splitting of deliveries in SAP ERP. If SAP TM receives an updated order or delivery, the system communicates the changes to the freight units of the corresponding transportation requirement.



Change Controller Strategy

If freight units are already planned and assigned to follow-up documents (freight orders/ bookings), SAP TM provides functionality to define how the system should react. Based on configuration, the changes and other attributes of the freight units are evaluated and a change strategy is executed. This functionality is provided by a component called Change Controller. Once freight units have been adapted, the change controller can process subsequent documents further, depending on strategies. The system processes a change controller strategy if a business document has been changed. The change controller strategy specifies how the change controller is to react to these changes. The change controller checks whether one of the following business documents have changed and how the system is to process these changes: •

Freight unit

•

Transportation unit

•

Freight order

•

Freight booking

•

Service order

Planning-Relevant Changes to Which the Change Controller Can React*

•

Changes to quantity

•

Changes to dates/times

•

Changes to source locations, intermediate stops, and destination locations

•

Reported execution information

•

Additional or deleted freight units or locations in the context of an OTR or DTR

*This is not an exhaustive list. You can also react to other changes, and even to custom fields. If you want to enhance the standard logic of the change controller for determining changes to business documents, you must make the necessary settings for the following BAdl: BAdl: Determination of Changes for Change Controller. Example Change Controller Actions in Response to Changes

•

Remove corresponding freight units from the transportation plan

•

Invalidate successor business documents such as freight orders

•

Stop the current associated tendering processes

•

Stop and restart the current associated tendering processes

•

Issue alerts

You can also define your own actions. SAP TM provides a set of predefined change strategies. You use strategies to define complete processes. Methods define the individual process steps of a strategy.



You can also define your own strategies and methods, and in doing so, the way in which your process is executed. If the system is unable process a change controller strategy due to a locking issue, you can use the background program /SCMTMS/PROCESS_TRIGGER_BGD to reprocess the strategy. Change Controller Settings

/

Transportation Requirement Type Customizing

Freight Unit / Freight Order / Freight Booking Type Customizing

Synchronous/Asynchronous Propagation of Changes

Default Change Strategy Strategy Det. Condition Quantity Tolerance Condition' Date Tolerance Condition

Date Change < 10 minutes

No Change

< 2 hours

Non-Critical Change

> 2 hours

Loc. Change

Subcontr. Stat.

...

Change Strategy

Non-Criticai

Sent

Inform Carrier

Critical

In Tendering

Restart Tendering

Critical Change X

Remove Plan & Send Alert &...

Figure 59: Change Controller Settings

The propagation of changes from an order-based or delivery-based transportation requirement to freight units can be performed synchronously or asynchronously. You can define your preferred setting in the Customizing settings for the transportation requirement type. Change Propagation Options

•

Synchronous The system propagates changes to the successor documents immediately after the change of the business documents. In case of lock issues, where the changes cannot be propagated to successor documents, the system issues an error message.

•

Asynchronous The system propagates changes to the successor documents after a specified time. In case of lock issues, the propagation is restarted automatically (and repeatedly) after a specified time until the changes to the successor documents can be propagated successfully.•

•

Synchronous with Fallback to Asynchronous



The system first tries to propagate the changes to the successor documents immediately after the change of the business documents. In case of lock issues, the changes are propagated asynchronously. The configuration settings relating to how changes should be processed on a freight unit, freight order, or freight bookings are located in the type customizing of these documents. You can specify the change controller settings for the business document types in Customizing for SAP TM. Change Controller Strategy Settings

•

Default Change Strategy You can assign a default change controller strategy (default strategy) to each business document type. If you have defined several change controller strategies, you can use a condition for determining the adequate change controller strategy.

•

Strategy Determination Condition If you indicate a strategy determination condition, the system uses the change strategy found via the condition. The system determines the change controller strategy at runtime based on the strategy determination condition. If you do not indicate a condition or if the condition does not return a strategy, the system automatically uses the default change strategy.

•

Quantity Tolerance Determination Condition You can use a tolerance determination condition to determine tolerances that are to be taken into account in the case of a quantity change in a business document (freight unit, freight booking, or freight order). This means that if a quantity is changed, the change controller evaluates this condition to dynamically check if a quantity change can be tolerated. If no condition of this type is assigned to a business document, only the standard logic to classify quantity changes is processed. The standard logic classifies all quantity changes as relevant quantity changes. This means that in case of a quantity change, the change controller evaluates this condition to dynamically determine if this quantity change can be classified as relevant or if it can be ignored. You assign this quantity tolerance determination condition to your business document type (for example, freight unit type). The result of a tolerance determination condition has an impact on the evaluation of the change controller condition that is assigned to the same business document type. The indicator for a quantity change that is provided as a data access definition to the change controller condition can change from "Relevant Quantity Change Determined" to "No Relevant Quantity Change Determined" if the quantity change is within the tolerances found.

•

Date tolerance determination condition You can use a date tolerance determination condition to determine the tolerances for a date change in a business document. This means that in case of a date change, the change controller evaluates this condition to dynamically determine if this date change can be classified as critical or uncritical or if it can be ignored. If you want to classify date changes according to your own logic, you can use this condition to enhance the standard logic. If no condition of this type is assigned to a business document (freight unit, freight booking, or freight order), only the standard logic to classify date changes is processed. The standard logic classifies all date changes as critical changes. You assign this date tolerance determination condition to your business document type (for example, freight unit type). The



result of a date tolerance determination condition has an impact on the evaluation of the change controller condition that is assigned to the same business document type. The indicator for a date change that is provided as a data access definition to the change controller condition can change from “Critical Change" to “ Non-Critical Change” or “ No Change” if the date change is within the tolerances found.



Unit 4 Exercise 9 Manage Cross-System Changes

Business Example Your company uses SAP TM in conjunction with SAP ERP. You must be able to verify the transferal of changes made in one system to the other. 1. In SAP ERP, create a new sales order. Use the following data: Field

Value

Order Type

ZA## 3000 10 00 CUST##-16 GR##_301 PRODTM-OO 50

Sales Organization Distribution Channel Division Sold-to Party PO Number Material Quantity

2. Identify the resulting transportation requirement in SAP TM, using the POWL. 3. Execute transportation planning for the transportation requirement and review the new freight order. 4. Review Change Strategy Determination Condition TMlll_CHACO. Which strategy is determined for location changes? 5. Assign the Change Strategy Determination Condition TMlll_CHACO to your Freight Unit Type FU##. 6. In SAP ERP, change the Sold-To-Party of your sales order to cust##-17. 7. Review the freight order in SAP TM. Is the freight order still assigned to the sales order and the freight unit? What is the freight order's life cycle status? What is the freight unit’s planning status?

0



Unit 4 Solution 9 Manage Cross-System Changes

Business Example Your company uses SAP TM in conjunction with SAP ERP. You must be able to verify the transferal of changes made in one system to the other. 1. In SAP ERP, create a new sales order. Use the following data: Field

Value

Order Type

ZA##

Sales Organization

3000


10

Division

00

Sold-to Party

CUST##-16

PO Number

GR##_301

Material

PRODTM-OO

Quantity

50

a) On the SAP Easy Access screen, choose Logistics —>Sales and Distribution —► Sales —► Order —► Create (transaction code VAOl). b) On the initial screen, enter the appropriate data from the table and press ENTER. c) On the overview screen, enter the remaining data from the table and press ENTER. d) If the ATP Check (Delivery Proposal) screen appears, choose Continue. e) Save your data. f) Record your sales order number. 2. Identify the resulting transportation requirement in SAP TM, using the POWL. a) In NWBC, choose ERP Logistics Integration —*• Worklist —► Overview Transportation Requirements. b) Choose Refresh at the top of your worklist. c) Locate the sales order number you recorded. 3. Execute transportation planning for the transportation requirement and review the new freight order.



a) In the POWL, select the line with your OTR and choose Start Transportation Cockpit. b) On the Profile and Layout Sets screen, choose New to create a new profile and layout set. c) Enter Planning Profile plan_tm 100_## d) Save your settings. e) Select the created line and choose Continue. f) On the transportation cockpit main screen, make sure that only your freight unit is selected and then choose Optimizer Planning —> Selected Entries with All Resources. g) On the Optimizer Result screen, choose Accept. h) In the transportation cockpit main screen, verify that the planning status of your freight unit has changed to Planned. You can see this in the Planning Status column. i) Save your work. j) Open the new freight order from the Freight Orders/Freight Bookings area. k) On the Document Flow tab, review the assignment to your sales order and your freight unit. l)

Leave the freight order screen open in display mode.

4. Review Change Strategy Determination Condition TMlll_CHACO. Which strategy is determined for location changes? a) In NWBC, choose Application Administration —> General Settings —> Conditions —> Display Condition. Enter t m i h _chaco and choose Continue. b) Enter tmiii_chaco and choose Continue. c) Verify that strategy REM_CANC is determined for location changes. 5. Assign the Change Strategy Determination Condition TMlll_CHACO to your Freight Unit Type FU##. a) In Customizing for SAP TM, choose SAP Transportation Management —*• Transportation Management —>Planning —>Freight Unit —>Define Freight Unit Types. b) Open the details of your Freight Unit Type FU##. c) Enter tmiii_chaco in the Change Strategy Determination Cond. field. d) Save your work and exit the screen. 6. In SAP ERP, change the Sold-To-Party of your sales order to cust ##-17. a) On the SAP Easy Access screen, choose Logistics —*■ Sales and Distribution —>Sales —► Order — > Change (transaction code VA02). b) Enter the number of the previously created sales order and press ENTER. c) Change the Sold-To-Party to cust ##-17. d) Confirm all popups and choose Redetermine where applicable.



e) Save your changes. 7. Review the freight order in SAP TM. Is the freight order still assigned to the sales order and the freight unit? What is the freight order's life cycle status? What is the freight unit’s planning status? No, the freight order is no longer assigned. The freight order’s life cycle status has changed to canceled. The freight unit status has changed to Unplanned.___________________________ a) Return to your freight order in NWBC. b) Choose Refresh. c) On the Document Flow tab, review that the assignments to the freight unit and the sales order have been removed. d) On the Document Flow tab, verify that the freight order's life cycle status has changed to Canceled. e) Return to the transportation cockpit screen (which should still be open). f) Choose Refresh. g) Verify that the freight unit's planning status is Unplanned.





•




Unit 4 Lesson 3 Scheduling Sales Orders with SAP TM

LESSON OVERVIEW In this lesson, you examine the process of sales order scheduling in SAP TM, including segment scheduling, and the determination of loading and unloading durations. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Sales Order Scheduling with SAP TM You can use the scheduling service of SAP TM while creating, changing, or rescheduling sales orders in SAP ERP. During order processing in SAP ERP, the transportation planning scenario in SAP TM is taken into account when calculating feasible dates and quantities for order items. This ensures that the sales order situation and the ATP situation are synchronized with the current planning scenario in transportation. Benefits and Restrictions of Sales Order Scheduling in TM

The benefits of sales order scheduling with TM are: •

Synchronous integration of SAP TM constraints enables you to make better and more profitable decisions.

•

In critical ATP situations, you can better use the resources and buffer less.

•

You can serve more customers and increase delivery reliability.

The restrictions of sales order scheduling with TM are: •

SAP TM does not support integration with ATP in SAP Supply Chain Management including GATP (Global Available-to-Promise).•

•

Scheduling for sales order items using product selection is not supported in SAP TM.



Backward and Forward Scheduling

SAP ERP

SAPTM

I tm 1 S ch ed uling S ervice

Create Sales Order

Scheduling call of SAP TM

R equested D elivery Dates Pick and pack time

Corresponding M aterial Staging Dates Availability Check (in ERP)

Schedule lines m ay be split

ATP check (if enabled):

N ew M aterial Staging Dates Pick and pack time

Second scheduling ( call of TM Corresponding D elivery Dates

B H B H I

“Backward Scheduling”: - Create transp. req. - Build freight units - Transportation planning - Schedule Material Staging Date

“Forward Scheduling”: - Schedule loading date(s) - Create transp. req. - Build freight units - Transportation planning - Schedule delivery date

Figure 60: Sales Order Scheduling

During the scheduling call, backward scheduling is first performed based on the requested delivery date. An ATP check is then carried out in ERP based on the determined material staging dates.If the ATP check fails, TM is called a second time and performs forward scheduling starting from the earliest ATP date. Segment Scheduling When scheduling transportation, TM considers the necessary transit duration to transport goods and any picking, packing, loading, and unloading time required.



OFFSET

PLANNING HORIZON

<----------------- 3>

UNLOAD TRANSIT LOAD PICK/PACK

MATERIAL AVAILABILITY DATE

REQUESTED DELIVERY DATE

TIM E

Figure 61: Scheduling Segments

Transit Time W ithout geographical information system (GIS)

Straight Line Distance 80 X

Distance Factor (1.3) (from Means-of-Transport)

_ Runtjme Lane Distance 104

Distance / Average Speed Per Unit = Duration W ith GIS ■

S\

By connecting to a GIS, distance and duration can be calculated for each means of transport within a transportation lane using exact road details.

Figure 62: Distance and Duration Calculation



Transit time is calculated in SAP TM based on the distance from the transportation lane and the speed of the means of transport. Transit time duration can also be taken from a Geographical Information System (GIS) if such a system is used along with SAP TM. If you use schedules for planning, the transit duration is taken over from the schedule. Loading and unloading times are defined in the planning profile. They can also be determined flexibly using a condition, based on freight units and/or means of transport attributes. The pick and pack time is defined for each shipping point in Customizing for SAP ERP, and is sent to SAP TM in the scheduling call. An offset can be defined in the planning profile so that the planning horizon is shifted into the future. This leaves some buffer time to organize shipping and transportation activities. Determination of Loading and Unloading Duration Standard: Loading and Unloading Duration Dependence:

Freight Unit and MTr Independent

Loading/Unloading Duration:

v

00:30:00

Condition Loading and Unloading Duration Dependence:


* Condition for Loading/Unloading Duration: C^piT-LDUR-COND-oT^>

D ecision Table: DIT_LDUR_COND_01__________________________________________________________________________ , ,________________________ Addbonal Ackons ,

Cornea Overview

Start Svnulakon

Table Contents -

■

-

✓

:•

■»

<**

Prenous

Dependence

Means or Transport

Business Document Ty

Load

Unload

AiFreijntUn* and MTr Dependent)-;

CXT_UT10(O«T Trucks o< earner CMT-CR-...

DIT3 (OfT Freight UnrtTrpe)r.

• obi

•Or

A(Freight Und and MTr Dependent) {•;

OfT_MTJ0 (OfT Trucks Of carter OnT-CR. ..

DTT3 (OfT Freight Unit Type) ft

120 K

120 R

Figure 63: Loading and Unloading Times

Loading and unloading durations are defined in the planning profile using either standard values or conditions. The system calculates loading and unloading durations automatically during transportation planning. You can define loading and unloading durations for each freight unit based on the freight unit attributes or means of transport, or both. You then define a condition with the condition type for loading and unloading durations for freight units. You specify this condition in the planning profile. The system evaluates the condition and returns the loading or unloading duration as the output value.

Note: If you enter the loading or unloading duration in both the HH:MM format and in seconds, the system adds both values together.







Unit 4

Learning Assessment

1. SAP TM enables stage building based on incoterm locations. Determine whether this statement is true or false. | True False 2. If an incoterm location is defined in the Incoterms (Part 2) field of a purchase order, no handover location can be defined and transferred to SAP TM for stage building. Determine whether this statement is true or false. | True False 3. SAP TM provides document flows that include SAP ERP documents and enables navigation to the details of these documents. Determine whether this statement is true or false. | True False 4. SAP ERP provides document flows that include SAP TM documents and enables navigation to the details of these documents. Determine whether this statement is true or false. | True False

0



5. The change controller can react to changes on which documents? Choose the correct answers. | A Order-Based Transportation Requirement B Delivery-Based Transportation Requirement | C Freight Unit D Freight Order E Freight Booking 6. Which change controller settings can be maintained in the freight order type Customizing? Choose the correct answers. | A Default change strategy B Business Add-In (BAdl) to be used for custom enhancements C Strategy determination condition D Quantity tolerance condition 7. Sales order scheduling with SAP TM can be used for both forward and backward scheduling. Determine whether this statement is true or false. | True False 8. During sales order scheduling with SAP TM, which times are calculated directly in SAP TM based on settings maintained in SAP TM? Choose the correct answers. | A Pick and pack time B Loading and unloading time C Transit time



Unit 4


1. SAP TM enables stage building based on incoterm locations. Determine whether this statement is true or false. [x ] True False

2. If an incoterm location is defined in the Incoterms (Part 2) field of a purchase order, no handover location can be defined and transferred to SAP TM for stage building. Determine whether this statement is true or false. | True \x \ False Correct. Both the Incoterms field and the handover location can be maintained on the purchase order and transferred to SAP TM. (In such a case, SAP TM uses the handover location for stage building.) 3. SAP TM provides document flows that include SAP ERP documents and enables navigation to the details of these documents. Determine whether this statement is true or false. [x ] True False

4. SAP ERP provides document flows that include SAP TM documents and enables navigation to the details of these documents. Determine whether this statement is true or false. [x ] True False

0



5. The change controller can react to changes on which documents? Choose the correct answers. | A Order-Based Transportation Requirement B Delivery-Based Transportation Requirement \x \ C Freight Unit [x ] D Freight Order

|~xj

E Freight Booking

6. Which change controller settings can be maintained in the freight order type Customizing? Choose the correct answers.

|~xj

A Default change strategy B Business Add-In (BAdl) to be used for custom enhancements

|~xj

C Strategy determination condition

|~xj

D Quantity tolerance condition

7. Sales order scheduling with SAP TM can be used for both forward and backward scheduling. Determine whether this statement is true or false. [x ] True False

8. During sales order scheduling with SAP TM, which times are calculated directly in SAP TM based on settings maintained in SAP TM? Choose the correct answers. | A Pick and pack time

|~xj

B Loading and unloading time

|~xj

C Transit time



UNIT 5

Delivery Integration with SAP TM

Lesson 1 Triggering Delivery Creation from SAP TM

154

Exercise 10: Create a Delivery

163

Lesson 2 Updating and Splitting Deliveries

169

Lesson 3 Managing Blocks

175

Lesson 4 Integrating Handling Units

180

U N IT OBJECTIVES

0

•

Describe delivery documents

•

Create a delivery

•

Update and split a delivery

•

Explain the interaction of SAP ERP and SAP TM in case of blocks

•

Manage handling units and packaging material requirements in SAP ERP deliveries

•

Integrate handling units in SAP TM



Unit 5 Lesson 1 Triggering Delivery Creation from SAP TM

LESSON OVERVIEW

As your order approaches a shipping date, the order document typically moves towards “ Committed” status, or what in SAP terms is called a delivery. In this lesson, you learn about the delivery integration process, freight unit consumption, as well as dealing with delivery updates and split deliveries. LESSON OBJECTIVES



•

Create a delivery

Delivery Integration Process



Employees using other processes for buying and selling may also need to complete shipping activities. The delivery document controls, supports, and monitors numerous subprocesses for shipment processing, such as picking, packing, loading, and posting the goods issue. In addition, the delivery document can be used as a reference document for the creation of other shipment documents, such as a bill of lading. Outbound deliveries and inbound deliveries that are created in SAP ERP can be transferred to SAP TM, where they are stored as delivery-based transportation requirements. They can be transferred as a starting point for TM integration or as follow-up documents of ERP orders. In the latter case, either an outbound or inbound delivery is expected by SAP TM based on the preceding order. Delivery integration between SAP ERP and SAP TM is standard integration by Web Service. Delivery Integration Process

TO R = Transportation Order

Figure 65: Delivery Integration Process

Delivery creation in SAP ERP can be triggered from SAP TM based on the results of transportation planning such as consolidation and dates, taking into account transportationplanning-relevant information such as resource availability and transportation durations. After creation of the delivery in SAP ERP, the delivery is transferred to SAP TM to create a delivery-based transportation requirement. Deliveries can be transferred to SAP TM regardless of whether the delivery creation was triggered by SAP TM or not. The delivery-based transportation requirement replaces the order-based transportation requirement as the requirement relevant for transportation planning and execution.



SAP ERP is the leading system — updates to and cancellations of deliveries need to be carried out in SAP ERP and are transferred to SAP TM to update or cancel the delivery-based transportation requirement. If a delivery is changed, split, or deleted in SAP ERP, this information is sent to SAP TM. SAP TM adjusts the corresponding delivery-based transportation requirement based on this information. You can also split an outbound delivery in SAP ERP based on planning changes in SAP TM, and you can update the goods issue date, loading date, transportation start date, and delivery date in the outbound delivery based on changed dates in SAP TM. Since TM 9.1 it is also possible to transfer planning changes in SAP TM back to SAP ERP to update delivery times or to split deliveries. SAP TM is the triggering system in this case. Delivery Creation from SAP TM

Figure 66: Delivery Creation from SAP TM

Creation of a delivery document can be triggered either in SAP ERP or in SAP TM (and then sent to SAP ERP). Triggered in SAP ERP When the delivery is created, it is sent to SAP TM as a delivery-based transportation requirement (DTR). This is a specific instance of the transportation request object (TRQ). Due to the fact that the source document (the delivery) originates in SAP ERP, not all functions and changes are possible (in comparison with a forwarding order created in SAP TM). Triggered in SAP TM



The second scenario is one in which the creation of deliveries is triggered from SAP TM and based on transportation planning performed in SAP TM. This solution offers the possibility of combining and planning multiple orders in SAP TM, and of creating a single delivery and transport. If handling unit management is being used in SAP ERP, these handling units are created as packages in the DTR in SAP TM. SAP TM can generate proposals for delivery creation in SAP ERP based on order-based transportation requirements, based on dates and quantities according to transportation planning results, and taking into account transportation constraints such as resource availability and transportation durations. SAP TM can also trigger the creation of deliveries prior to transportation planning. SAP TM can propose inbound deliveries and outbound deliveries and send these proposals to SAP ERP to trigger the creation of deliveries. After the delivery proposals have been created and sent to SAP ERP, the system creates an entry in the application log. The application log entry includes the delivery proposals that were sent to SAP ERP. Furthermore, the freight units for which a delivery proposal is sent to SAP ERP are marked with a send timestamp. SAP ERP creates the deliveries when it receives the request to do so. These can be inbound or outbound deliveries. SAP ERP may split the proposed deliveries further, for example, based on additional split criteria. However, SAP ERP will not change the dates that were proposed by SAP TM nor consolidate proposed deliveries. Once the deliveries have been created, SAP ERP sends a confirmation to SAP TM, together with a request to create a delivery-based transportation requirement in SAP TM. SAP TM creates an entry in the application log. The application log entry includes the system messages that were created in SAP ERP during delivery creation as well as the numbers and document IDs of deliveries created in SAP ERP. If an error occurred during delivery creation in SAP ERP, SAP TM generates an alert. When a confirmation is received, SAP TM sets a confirmation timestamp in the relevant freight units. The timestamp is used to monitor whether SAP ERP has responded.

Note: For error handling purposes, two additional worklists are available: •

One for all OTRs for which delivery creation has been triggered but no response has arrived from SAP ERP.

•

One for all OTRs for which delivery creation has been triggered and the confirmation has arrived from SAP ERP, but for which an error occurred during delivery creation (and for which the delivery creation needs to be triggered again).

Methods for Delivery Creation

•

Background Report

•

Interactive Delivery Creation

Background Report Delivery proposals can be created for order-based transportation requirements by using a background report (report /SCMTMS/DLV_BATCH). The user can enter selection criteria or use



a selection profile. In both cases, the user can also enter a delivery profile. Delivery profiles include settings for delivery creation and will be covered later. The system selects the documents, creates the delivery proposals, and sends them to SAP ERP. If a freight unit is used for the creation of a delivery proposal, but no delivery-based transportation requirement is ultimately created, the same report cannot be used to create a new delivery proposal for that freight unit. Instead, a new delivery proposal must be created interactively in SAP NetWeaver Business Client. Interactive Delivery Creation Possible Approaches in Interactive Delivery Creation

•

Input Selection with Profiles The user specifies one or more profiles according to which the system selects and displays a list of documents. The user can then select the relevant documents in the list and trigger delivery proposal creation. The user can review the delivery proposals before sending them to SAP ERP.

•

For Specific Documents The user can trigger delivery creation for specific business documents from worklists. The system automatically sends the proposals to SAP ERP to create deliveries. It also displays the proposals before sending. The following are worklists from which delivery creation can be triggered: -

OTR Worklist

-

Freight Unit Worklist

-

Freight Order Worklist

-

Ocean/Air Freight Booking Worklist

The user can also trigger the creation and sending of delivery proposals for a specific freight order in the freight order Ul. •

After Planning The user can trigger delivery creation for specific documents after carrying out planning in the transportation cockpit. The system displays the delivery proposals, which the user can then review before sending them to SAP ERP.

Data Sources

SAP TM considers data for delivery creation from the order-based transportation requirements and from the assigned freight units, freight orders, and freight bookings. Based on the chosen input, SAP TM creates delivery proposals. A proposal consists of groups of freight units that can be delivered together. Data Collected by SAP TM

•

Dates SAP TM uses dates from the freight order or freight booking. If the order-based transportation requirement is not planned, that is no freight order or freight booking exists, then SAP TM uses dates from the freight units.



•

Quantities SAP TM uses quantities from the freight units.

•

SAP ERP Document References SAP TM retrieves document references (such as order document number) from the orderbased transportation requirement.

Consolidation If order-based transportation requirements have been planned, and freight orders or freight bookings exist for the transportation requirements, SAP TM uses only one freight order or one freight booking for each delivery proposal. That is, only freight units that belong to the same freight order or freight booking can be consolidated into a single delivery proposal. In this way, freight units from various order-based transportation requirements can be consolidated into a single delivery proposal if they belong to the same freight order or freight booking. If, however, freight units from a single order-based transportation requirement are distributed across multiple freight orders or freight bookings, then multiple deliveries are proposed for the freight units of this one order-based transportation requirement. If order combination is not allowed for an order-based transportation requirement, SAP TM does not group freight units from this transportation requirement together with freight units from other order-based transportation requirements. If freight units for such order-based transportation requirements have been consolidated into the same freight order or freight booking during planning, SAP TM does not include them in the same delivery proposal, but instead creates multiple delivery proposals. In addition, freight units can only be consolidated into the same delivery proposal if the following data is the same: •

SAP ERP system from which the order was received

•

Source location

•

Destination location

•

Incoterms

•

Shipping conditions

•

SAP ERP document type, such as purchase order or sales order

•

Start stop (if planning has already been done)

•

Destination stop (if planning has already been done)

Delivery Profiles The delivery profile controls how deliveries are created in SAP ERP from SAP TM. Delivery profiles can be selected in the Delivery Creation worklist, or they can be configured in the customizing of freight order types. Delivery Profile Settings

•

You can define that during delivery creation the system fixes the planning results for freight units, freight orders, or freight bookings that have already been planned. If you specified a delivery profile that requires the planning results to be fixed for planned freight units, freight



orders, or freight bookings, the system fixes the planning results during delivery proposal creation. Otherwise, the system does not fix the planning results. •

You can define how the system creates deliveries when a user triggers delivery creation in SAP ERP for freight units that have not been planned (for example, one delivery per item in an order-based transportation requirement).

•

You can specify incompatibility settings. In the incompatibility settings, you can define attributes that prevent freight units from being combined into one delivery, for example.

•

You can define whether freight units/orders/bookings that are blocked for planning or for execution should be included in delivery proposal creation.

Impact of Delivery Profile on Delivery Creation

Delivery Profile A •

AT

Fix Planning Results • Delivery creation per OTR • Incompatibilities • Exclude blocked documents

---- >

I I

I

One delivery

Freight Unit

Delivery Profile B

---- >

I

• • • •

Don’t Fix Planning Results Delivery creation per OTR item Incompatibilities Include blocked documents

I

I

Two deliveries

Figure 67: Delivery Profile

The figure, Delivery Profile, illustrates the impact of delivery profiles on delivery creation.



Freight Unit Consumption

When a delivery is created in SAP ERP, a delivery-based transportation requirement (DTR) is created in SAP TM. The DTR consumes the freight units assigned to the relevant order-based transportation requirements (OTR) if the corresponding orders were previously sent to SAP TM. SAP TM uses the SAP ERP order (base document) number that is referenced in the DTR item to find the corresponding OTR items (the base document number and item number is also referenced in the OTR items). If there are differences between the freight unit or item and the DTR, SAP TM adapts the freight units accordingly so that the information in the freight unit corresponds to the transportation requirement. Freight Unit Determination, Splits, and OTR Updates

Determination of Freight Units As described under Freight Unit Consumption (above), the system can determine the freight units which are assigned to OTR items. SAP TM reassigns the freight units from the OTRs to the DTRs. If multiple freight unit items are determined, SAP TM assigns the freight unit items to the items of the DTR in chronological order (according the dates of the schedule lines that the freight unit items reference). Once a freight unit is assigned to a DTR, the freight unit cannot be assigned to another DTR. If SAP TM does not determine any freight units, SAP TM can build new freight units for the DTR, as long as automatic freight unit building is allowed for the DTR type. This situation might occur, for example, if deliveries are created in the SAP ERP system without a preceding delivery proposal being sent from SAP TM. Splitting Freight Units If, in the course of transportation requirement consumption, a freight unit is to be reassigned, but not all freight unit items or quantities are relevant for the DTR, SAP TM splits the freight unit. One of the resulting freight units contains only the relevant freight unit items and is assigned to the



DTR. The other resulting freight unit contains the non-relevant freight unit items and is assigned to the OTR. If the quantity in a DTR item is less than the quantity in the associated freight unit, SAP TM splits the freight unit. If there are other differences between the freight unit or item and the DTR, SAP TM adapts the freight units accordingly so that the information in the freight unit corresponds to the transportation requirement. Updating an OTR During the consumption process, the open quantities and the consumption status are updated on the OTR. The open quantity in an OTR represents the quantity that has not been assigned to a DTR. When freight units are reassigned to a DTR, the open quantity of the OTR is reduced accordingly. Initially, the OTR has the consumption status Not Consumed. If at least one OTR item, or part of an item, has been consumed by a DTR item, the consumption status of the OTR changes to Consumed Partially. If all items in an OTR have been consumed, the system changes the consumption status to Consumed Completely. Once the consumption status is Consumed Completely, the system changes the life cycle status to Completed.



Unit 5 Exercise 10 Create a Delivery

Business Example

You intend to use delivery documents for recording and monitoring the shipping process after the shipment has been planned. You need to understand how to trigger delivery creation from SAP TM. 1. In NWBC, locate the three order-based transportation requirements with Customer PO numbers GR##_101. GR##_201. GR##_301. 2. What is the consumption status?

3. Execute transportation planning for the transportation requirements. 4. Review the result of transportation planning. What is the planning status of your freight units?

5. How many freight orders have been created?

6. Review the stops and the planned dates in the freight order. 7. In the POWL, initiate the creation of deliveries in ERP for your three sales orders based on your transportation planning results. 8. On the Create Deliveries in ERP screen, create delivery proposals based on your three freight units. 9. How many delivery proposals are created? Why?

0



10. Review the delivery proposals. Which dates are proposed?

11. Determine which freight units and sales orders / sales order items are included in which delivery proposal. Delivery 1 Delivery 2 12. Send the delivery proposals to SAP ERP. 13. In the POWL, review your order-based transportation requirements. What is the consumption status? Hint: Refresh your worklist. It might take some time until the status changes.

14. Open one of your order-based transportation requirements and review the document flow. To which document are the freight unit and freight order now assigned?

15. Open the assigned delivery-based transportation requirement by clicking the link in the Business Document column. Which delivery type was used in SAP ERP?



Unit 5 Solution 10 Create a Delivery

Business Example

You intend to use delivery documents for recording and monitoring the shipping process after the shipment has been planned. You need to understand how to trigger delivery creation from SAP TM. 1. In NWBC, locate the three order-based transportation requirements with Customer PO numbers GR##_101. GR##_201. GR##_301. a) In NWBC, choose ERP Logistics Integration —> Worklist —> Overview Transfer Requirements. b) Choose Refresh at the top of your worklist. c) Locate the three order-based transportation requirements. 2. What is the consumption status? Not consumed.________________________________________________________________ 3. Execute transportation planning for the transportation requirements. a) On the POWL, select the three OTRs and choose Start Transportation Cockpit.

b) If the Profile and Layout Sets screen is displayed, use Planning Profile plan_ tmioo _## and then continue (ignore any warning messages). c) In the Transportation Cockpit main screen, make sure that only your three freight units are selected and then choose Optimizer Planning —> Selected Entries with All Resources. d) In the Optimizer Result screen, choose Accept. e) In the Transportation Cockpit main screen, choose Save. 4. Review the result of transportation planning. What is the planning status of your freight units? Planned._____________________________________________________________________ 5. How many freight orders have been created? All three freight units are planned on one multi-stop freight order. 6. Review the stops and the planned dates in the freight order.

0



a) Select the line with the freight order in the Freight Orders/Freight Bookings panel and then scroll down to see the overview. Choose the Maximize button. b) Review the sequence of the different stops and the loading and unloading activities of the three freight units. c) Review the start and end of activities at the different stops. d) Choose Restore to minimize the overview tab. e) Close the transportation cockpit. 7. In the POWL, initiate the creation of deliveries in ERP for your three sales orders based on your transportation planning results. a) Return the worklist of order-based transportation requirements, which should still be open. b) Make sure your three transportation requirements are selected. c) Choose Create Deliveries in ERP. d) If the Create Deliveries in ERP: Profile and Layout Sets screen appears, choose New to create a new line. Select the new line (do not add any entries), and then choose the Start Creating Deliveries button. 8. On the Create Deliveries in ERP screen, create delivery proposals based on your three freight units. a) Make sure your three freight units are displayed and selected. b) Review the freight units' locations. c) Choose Create Delivery Proposals. 9. How many delivery proposals are created? Why? Two delivery proposals are created, one for each destination location._____________________

10. Review the delivery proposals. Which dates are proposed? The planned dates of the freight order are proposed._____________________________________

11. Determine which freight units and sales orders / sales order items are included in which delivery proposal. a) Select the first delivery proposal and go to the Delivery Proposal Details tab. b) Review the included freight units and sales orders / sales order items. c) Repeat the steps with the second delivery proposal. Delivery 1



Delivery 2 12. Send the delivery proposals to SAP ERP. a) Choose Send delivery proposals to ERP. b) Make sure that the system confirms that 2 delivery proposals have been sent to ERP. 13. In the POWL, review your order-based transportation requirements. What is the consumption status? Hint: Refresh your worklist. It might take some time until the status changes. The status has changed to Consumed Completely.___________________________________ 14. Open one of your order-based transportation requirements and review the document flow. To which document are the freight unit and freight order now assigned? The freight unit and freight order are now assigned to a delivery-based transportation requirement.__________________________________________________________________ 15. Open the assigned delivery-based transportation requirement by clicking the link in the Business Document column. Which delivery type was used in SAP ERP? LF




•


•

Create a delivery



Unit 5 Lesson 2 Updating and Splitting Deliveries

LESSON OVERVIEW This lesson outlines how to update, and how to split a delivery. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Delivery Updates Delivery updates can be triggered both from SAP ERP and from SAP TM (since TM 9.1). Updates from SAP TM are based on planning changes, the delivery-based transportation requirement itself is read-only and can't be changed directly in SAP TM.

If a delivery is changed or deleted in SAP ERP, this information is sent to SAP TM. SAP TM adjusts the corresponding delivery-based transportation requirement based on this information. The freight units are adjusted according to the changes in the delivery-based transportation requirement. If the quantity of the delivery-based transportation requirement has changed and the delivery-based transportation requirement is assigned to freight units that were consumed from an order-based transportation requirement, the freight units are adjusted.

0



If the quantity of the delivery-based transportation requirement has decreased, the open quantity of the corresponding order-based transportation requirements is increased accordingly; and the freight units of the delivery-based transportation requirement are split. Freight units are retained by the delivery-based transportation requirement to cover the reduced quantity of the deliverybased transportation requirement, and the remaining freight units are assigned to the corresponding order-based transportation requirement. If the quantity of the delivery-based transportation requirement has increased, and there are still open quantities in the corresponding order-based transportation requirement, the system reassigns the freight units from the order-based transportation requirement to cover this increased delivery quantity. The system then reduces the open quantity of the order-based transportation requirements. Delivery Updates Triggered by SAP TM

Figure 70: Delivery Updates Triggered by SAP TM

You can also update the goods issue date, loading date, transportation start date, and delivery date in the outbound delivery based on changed planning dates in SAP TM. When SAP ERP receives a request for an update, it makes the necessary changes in outbound delivery processing and sends the delivery data back to SAP TM. SAP TM can then make the required changes to the delivery-based transportation requirements. You perform planning or change the existing planning of freight units that belong to a DTR that is based on an outbound delivery. Dates are changed during planning. Alternatively, you change the dates of the relevant freight order. When you save the planning results or the changed freight order, SAP TM determines that the dates in the freight order no longer match the dates in the DTR and the original SAP ERP delivery.



SAP TM determines whether the SAP ERP delivery can still be changed by checking the delivery status. If the delivery can be changed, SAP TM sends the changed dates to SAP ERP and requests the update of the outbound delivery. Based on the request received from SAP TM, SAP ERP updates the relevant dates. SAP ERP informs SAP TM about whether the delivery update was successful. The confirmation is received in SAP TM. SAP ERP sends the updated outbound delivery to SAP TM. In SAP TM, the delivery is received. Note that SAP TM can trigger the update of outbound deliveries only. It cannot trigger the update of inbound deliveries. Split Delivery Delivery splits can be triggered both from SAP ERP and from SAP TM (since TM 9.1). Splits from SAP TM are based on planning changes.

DTR Type Custom izing

Discard Planning • of new DTR? • of original DTR? • of both DTRs?

Figure 71: Delivery Splits Triggered by SAP ERP

SAP ERP splits a delivery that has already been sent to SAP TM. SAP ERP sends the following information in separate messages, as follows:• •

The new delivery that has been created for the items split from the original delivery. The data sent includes a reference to the original delivery. When SAP TM receives the delivery data, it creates the new delivery-based transportation requirement.



•

The changed original delivery. The data sent includes a reference to the new delivery. When SAP TM receives the delivery data, it updates the original delivery-based transportation requirement.

SAP TM creates the new DTR first by reassigning the freight units from the original DTR to the new DTR. It then updates the original DTR. The system determines the required changes to freight unit planning for the freight units assigned to the new DTR and the original DTR. For example, the system discards the planning of the freight units assigned to the new DTR and keeps the planning of the freight units assigned to the original DTR. After reassigning the freight units, the system must determine whether the planning of the freight units in the new DTR or the original DTR is to be discarded or kept. To determine which action is required, the system checks different criteria, one of which is Delivery Split/Update Type customizing, which is assigned to the DTR Type customizing. Delivery Splits Triggered by SAP TM

Figure 72: Delivery Splits Triggered by SAP TM

You can split an outbound delivery in SAP ERP based on planning changes in SAP TM. When SAP ERP receives a request for a split, it makes the necessary changes in outbound delivery processing and sends the delivery data back to SAP TM. SAP TM can then make the required changes to the delivery-based transportation requirements (DTRs). Note that SAP TM can trigger the split of outbound deliveries only. It cannot trigger the split of inbound deliveries. You perform planning or change the existing planning of freight units that belong to a DTR that is based on an outbound delivery. When you save the planning results, the system determines that a delivery split is required. For example, freight units that belong to the DTR have been assigned to different freight orders, or only some of the FUs that belong to a DTR



have been assigned to freight orders and the other FUs have not been assigned. Note that the split is required only if the first stage or the last stage of the transportation chain is affected. SAP TM determines whether the SAP ERP delivery can still be changed by checking the delivery status. If the delivery can be changed, SAP TM sends the required delivery split to SAP ERP. SAP TM sends the details of the items that are to be split from the original delivery (that is, IDs of the items in the original delivery, split quantity, unit of measure, and the required dates for the new delivery). Based on a split request received from SAP TM, SAP ERP creates a new outbound delivery and changes the original outbound delivery (that is, it removes the relevant items from the original delivery and creates a new delivery for these items). If you specified a split reason in the delivery split/update type customizing, SAP ERP splits the delivery according to the settings in the corresponding split profile. SAP ERP informs SAP TM about whether the delivery split was successful. The confirmation is received in SAP TM. SAP ERP sends the following information in separate messages: •

The new delivery that has been created for the items split from the original delivery. The data sent includes a reference to the original delivery and the triggering application SAP TM.

•

The changed original delivery. The data sent includes a reference to the new delivery.

SAP TM creates the new DTR first by reassigning the freight units from the original DTR to the new DTR. It then updates the original DTR. The triggering application is included in the message sent by SAP ERP. This enables SAP TM to distinguish between a split that is triggered by SAP TM (planning is correct) and a split triggered by SAP ERP or SAP EWM (planning is no longer correct and must be updated).



Transportation Planning Changes in SAP TM Transportation planning changes in SAP TM requiring...

... a Delivery Split:

... a Delivery Update:

•

Assigning FUs to different Freight Orders / Freight Bookings

Changing Freight Order or Freight Booking Dates: Start Date or End Date

•

Assigning FUs only partly to a Freight Order / Freight Booking

Re-assigning FUs to a Freight Order / Freight Booking w ith different dates

•

Unassigning FUs partly from a Freight Order / Freight Booking

... no Split or Update:

•

Freight O rd e r/F re ig h t Booking is not the first or the last in the transportation chain

•

All FUs o f a DTR are handled in the same way

•

Other relevance criteria are not fulfilled

Figure 73: Transportation Planning Changes in SAP TM

Changes to transportation planning in SAP TM can result in several actions, as summarized in figure Transportation Planning Changes in SAP TM. LESSON SUMMARY You should now be able to:

•




Unit 5 Lesson 3 Managing Blocks

LESSON OVERVIEW In this lesson, you learn about blocks (shipment and delivery blocks), and how to exclude blocked freight units during the process of delivery creation. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Shipment Blocks

Shipment blocks in SAP ERP define that ERP documents may not be planned on shipment documents. Shipment blocks are set on outbound deliveries. This means that the outbound deliveries can still be processed, but they cannot be planned on shipment documents that represent the actual transportation execution.

0



Delivery Blocks

Sales O rder

V J \

Delivery Block = X

O utbound D elivery

^

A

Delivery Blocks DB Descnption

DkTy Description

01

Credit tnmt

LF

Outbound Dekvery)

02

Political reasons

LF

Outbound Dekvery

03

Bottleneck material

LF

Outbound Dekvery

04

Export papers mssng

LF

Outbound Dekvery

05 Check free of ch.dfv

LF

Outbound Dekvery

07

LF

Outbound Delivery

Change n quantity

Figure 75: Delivery Block

As with shipment blocks, delivery blocks in SAP ERP indicate that even though the sales order may still be processed, the outbound delivery may not be created. This restriction could be due to several factors, as shown in figure Delivery Block. For example, an issue with payment terms, a credit limit, or a bottleneck material are examples of possible reasons for delivery blocks being applied.



Block Handling in Integrated Orders

Delivery Block

Shipment Block

Defcefy Blocks

D efinition of delivery blocks in SAP ERP:

D efinition o f sh ip m e nt

06

Dwcnooor

DkrTy

Descrpton

01 02 03 04 as 0?

Crtdt tm*

If

OrXboond OetstH Outbound Delrery Outbound Det/erv Outbound Dokrery Outbound Delrery Outbound Delrery

PX t

at tenons

ir

Bottleneck materai Export paper? mssng Checkfree of cfi.dr Change n Quantity

IT

IT IT If

blocks in ERP:

ShpmtBRsn DescnpDon Return defcvery 02 Goods are checked

J01

D efne D elrery Bock Reasons Descnption

Block Reason

D efinition o f delivery

□»

block reasons in TM:

D efinition o f sh ip m e nt

C rtd* U m t P o k m l reasons

planning block reasons

.Jo s Export paper? t b v q Check free of ch.dlr

!95

Define Shpment Pbnnng Block Reasons Block Reason Descrpton 01 Return debery rGoods are checked 02

in TM:

Change n quantity

+ D efinition o f delivery blocks in TM:

D efinition o f sh ip m e nt planning block in TM:

Oefae Blocks Bated on IKP DoMry Bocks Det/ery Stock Reason Desertion lot

|02 04 !°4

OeOt Lrxt Rokical reason* Export paper? mesne Export papers mcsng

D t'r t Blocks Based on ERP Shpment P4m ng Bocks Document Type 111 S eles 0«4et 114 S ales C rie r 114 S sles C rie r *3 Outbound D e llv .

Ptsrnrg Stock Executor Block * • -

Shcrnent Ph. Btock Reaton Desertion Document Type Cl Return delrery ’ 3 Outbound de live ry Cl Good* are chocked 13 Outbound Delivery

51 r

PlnnsiB Stock Executor Block *

0)

*

□

91

V &

■

Figure 76: Setup for Block Handling in Integrated Orders

As we have seen, blocks in SAP ERP define how documents may be processed or handled. A sales order with a delivery block may not be delivered, which means no delivery may be created for it. Deliveries with shipment blocks may not be transported, which means they may not be planned on shipment documents. The entire transportation process is not driven solely by the SAP ERP system. The SAP TM system also plays an integral role. For example, deliveries can be created from a delivery proposal sent from SAP TM to SAP ERP or a shipment can be created from an SAP TM freight order. The blocks set on ERP documents need to be respected in SAP TM. Therefore, you can maintain block reasons in Customizing for SAP TM as shown in figure Setup for Block Handling in Integrated Orders. Note that the block reasons created in Customizing for SAP TM need to be the same, that is, the block reason codes need to match across both systems. For each block reason in SAP TM, you can define how to handle this block in further processing. As shown in figure Setup for Block Handling in Integrated Orders, the ERP block mapped in SAP TM can either cause a planning block or an execution block. As the names suggest, a planning block means a freight unit that is created out of an OTR may not yet be planned. A freight unit with an execution block may still be planned but any freight order containing this freight unit cannot be executed. If neither planning nor execution is blocked, you are able to create freight units, plan them on transportation orders, and even start execution in SAP TM, but delivery or shipment creation in SAP ERP is not possible as long as there is a block on the order.



Example Block Handling in Integrated Orders

Define Blocks Based on ERP Delivery Blocks Dekvery Block Reason Descrption

Document Type

02

Poktical reasons)

01

Credit Limit

114 S a le s O rder w 1______________________ 114 S a le s O rder w

Planning Block

Execution Block

0

□

0

0

Figure 77: Example Block Handling in Integrated Orders

Delivery blocks in SAP ERP can be set either on header level or on item level. Therefore, the planning and execution blocks in SAP TM can also be defined on header or item level. The figure Example Block Handling in Integrated Orders describes how the blocks can be defined. The example in the figure shows a sales order that contains a delivery block for political reasons on header level. The sales order contains two schedule lines, one with a delivery block due to a failed credit limit check and one that takes over the delivery block from the header level. The sales order creates an OTR in SAP TM which takes over the block reasons from the sales order both on header and on item level. Depending on the Customizing settings applied in SAP TM, planning and execution blocks are set on header and item level. The blocks on the items are then taken over into the freight unit. If no blocks are set separately on the items, the block from the header level is taken over into the item upon creation of the OTR. In case of shipment blocks, the blocks should be mapped to planning blocks so that freight units that are based on ERP orders or deliveries with a shipment block may not be planned. Delivery block reasons set in an SAP ERP sales order (on header or schedule line) are considered and used to determine if an execution and/or planning block is set on the OTR header or item. Delivery block reasons set in an ERP outbound delivery are considered and used to determine if an execution and/or planning block is set on the DTR.



Shipment planning blocks on SAP ERP outbound deliveries can be used to determine the planning and/or execution block on DTR header level. The shipment planning block and reason set on the outbound delivery header is taken over into the DTR header. The planning and execution blocks for the DTR header are retrieved from the Customizing of the respective shipment planning block reason. If a planning block is set on a DTR header, the FU is created automatically with blocks on the header for both planning and execution. An OTR or DTR with planning and/or execution blocks still triggers the creation of a freight unit. The freight unit inherits the execution and/or planning blocks from the OTR or DTR. Furthermore, a negative credit check status on a sales order header is mapped to a dedicated delivery block reason (Credit Limit) in SAP TM. The planning and execution block settings of this dedicated delivery block are taken over accordingly into the OTR header and all its schedule lines as well as into the FU header. Delivery Creation Blocking New Delivery Profile DP_001 @ S ave

•

C an e d

\

EeM

IQ ]

C neek

|

|

Q,

G eneral Data

General Data * Dekvery Profile Description

Control DPJXJ1

c?

Delivery Profile e x d blocked docum ents

Fix P ta n n n g R esults

** |

Delivery Creation: incompebbilrty Settings_______ Exclude FUs/FOs blocked for execution Exclude FUs/FOs blocked for planning

[7

Display

~7 a

Figure 78: Block Delivery Creation

If an SAP ERP sales order has a delivery block, it means that no deliveries may be created for this order. Therefore, when integrating the order into SAP TM, you need to ensure that no deliveries are proposed for these orders (in SAP TM, during the delivery proposal process). When a block is in place, any attempt to create a delivery fails. However, it is preferable that no delivery proposals are generated at all (when the system knows the block is in place). When creating a delivery profile, you can be decide whether delivery proposals should also be created for freight units that contain blocks. This means that you can determine if freight units/orders/ bookings with a planning block or execution block are considered for building a delivery proposal and triggering delivery creation in SAP ERP. Note that once an OTR/DTR and freight unit are created, SAP TM can no longer differentiate whether any block on the freight unit derives from a delivery block in SAP ERP or was set in SAP TM due to time conflicts, missing information, and so on. Therefore, in the delivery profile freight units can only be excluded due to the fact that they have a planning or execution block, regardless of whether this block was set internally in SAP TM, or derived from SAP ERP. LESSON SUMMARY You should now be able to: •




Unit 5 Lesson 4 Integrating Handling Units

LESSON OVERVIEW Goods, products, or materials are not typically shipped without some form of packaging material. In this lesson, you learn about packaging material integration and the consolidation of packaging materials and goods into handling units. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Handling Units

H an dling u n it no. 1234567890

_____________ w P a ckag ing m aterial

Figure 79: Handling Units

A handling unit (HU) is a logistic unit consisting of packaging materials and goods (materials). Typically, a company does not move individual pieces of different materials, rather quantities of materials grouped together as packages. You can depict this situation in the SAP System using Handling Unit Management. When you use Handling Unit Management, the system tracks the entire HU rather than individual materials. The HU is the common unit for material and information flow. A business transaction for a HU implies corresponding business transactions in the background for the materials and



packaging materials it contains. In this way, one business transaction entry takes the place of several individual material-movement entries. You can use handling units and can pass them to partners throughout the supply chain. Handling units have a single identification number that uniquely identifies the handling unit across the various processes through which it moves. Using handling units in a cross-system logistics chain usually requires an identification number that is unique worldwide. You therefore have the option of assigning a Serial Shipping Container Code (SSCC) number to each handling unit. Packaging Materials Packaging materials are intended to enclose or hold together the materials that are to be transported. The packaging materials and the goods material together comprise the handling unit, as we have seen. The material that is to be packed can be packed into or onto the packaging material. The packaging material can also be a load carrier, such as a pallet. The most important packaging materials include crates, boxes, containers, wire baskets, and pallets. You have to maintain the material master data for each packaging material you want to use. When creating material master records for packaging materials, enter either material type, VERP (packaging) or a customer-specific material type that you have already set in Customizing. Material type VERP contains additional packing-relevant fields ( Sales: General/Plant Data screen). You can use the field selection to make the additional fields available for input for all of the material types. Tare W eight and Volum e

The gross weight and the volume that you enter in the material master have special significance for packaging. When you create a handling unit (HU), the system automatically copies the packaging material’s master data and uses the gross weight and volume as the packaging material's tare weight and tare volume. The tare weight and tare volume refer to the gross weight and gross volume of the packaging material. In the case of a container, the tare weight is the weight of the unloaded container (the total weight less the weight of the goods and packaging materials that are packed in the container).



Packaging Material Integration

Before handling units can be integrated from SAP ERP to SAP TM, the relevant packaging material has to be transferred to SAP TM. In the same way that a product needs to be transferred to SAP TM, product master data also needs to exist in SAP TM for the packaging material. This integration can be achieved using the Core Interface (CIF), as is the case with material master data for products. Handing Unit Integration ,| D isp lay H an d lin g U n its fo r O utb o un d D e liv e ry 0 0 8 0 1 2 0 1 9 9

Pack material

Pack HUs

Ttl content

Gen.header data

General overview of al HUs with hierarchy levels Hera... line Identification Material/Packagng Material Packed quantity 0 603 TM-080 1 1 0080120199 000010 PROOTM-OO 10 1 0080120199 000020 PROOTM-Ol 10

S... Descnption Grossweight PC Container 20' 2,908 BOXTM100 Product 10 - On Palets 1.000 BOXTM100 Product 11 - On Palets 1.000

Display Outbound Transportation DTR TM100 GROO 1190000042 (Outbound Delivery 80120199)

-

Items

|l Item Hierarchy

Item

»

2893

Handling Unit

Item Description

Product

Pack.

Packag...

TM-080

603

V080

Deli. Qua.

Deliv Qua. Unit

Gross Weight

Gross Weight UoM

1 PC

2.908 TO

jQ Product

10

TM100 Product 10 - On Pallets

PRODTM-OO

10 CRT

1.000 LB

53 Product

20

TM100 Product 11 - On Pallets

PRODTM-01

10 CRT

1 000 LB

Figure 81: DTR Handling Unit Integration



During the packing process in SAP ERP, handling units can be created to reflect items such as containers, rail cars, or pallets. In SAP TM you can configure the system to use the appropriate item category to create the packaging information in SAP TM. The item structure of the DTR may differ from the structure in the OTR due to the handling unit information in the delivery received from SAP ERP. If a handling unit has been created, a handling unit is added to the DTR. This handling unit item is transportation-relevant and includes the complete quantity of both the packaging and goods that are to be transported. The handling unit item can contain one or more product items or packaging items. The freight units (or parts thereof) that are determined for the items of this handling unit item are consolidated into one single freight unit item, which is assigned to the handling unit item. The gross weight of the freight units is based on the handling unit item, not on the included product items. In addition to the product weight, it includes the tare weight of the packaging material. Handling Unit and Freight Units


Sales Order Item 10: Product 1 Item 20: Product 2 Item 30: Product 3

— >

Item 10: Product 1 Item 20: Product 2 Item 30: Product 3

Freight Unit 1 Item 10: Product 1

Freight Unit 2

Freight Unit 3

Item 10: Product 2

Item 10: Product 3

Delivery Handling Unit Item 10: Product 1 Item 20: Product 2 Item 30: Product 3

Delivery-Based Transportation Requirement Handling Unit Item 10: Product 1 Item 20: Product 2 Item 30: Product 3

Freight Unit Handling Unit Item 10: Product 1 Item 20: Product 2 Item 30: Product 3

Figure 82: Handling Unit and Freight Units

When a DTR includes handling unit items, the freight units are adjusted accordingly when they are reassigned from the OTR during the consumption process. All product items that have been packaged into one handling unit are included in one freight unit; they are not split across several freight units. In this way, it is ensured that parts of a handling unit are not assigned to different vehicle resources during transportation planning.



If the freight units as they were built based on the OTR do not reflect this structure, the freight units are adjusted during the consumption process. If, for example, separate freight units were built per product for the OTR, and these products are consolidated into one handling unit, the separate freight units are merged into one freight unit. There is not necessarily a one-to-one relationship between handling units and freight units. One freight unit can contain several handling units. If desired, freight unit building can be set up to create one freight unit per handling unit. LESSON SUMMARY You should now be able to:

•


•




Unit 5

Learning Assessment

1. Which of the following settings can be maintained in the delivery profile? Choose the correct answers. | A Fixing of planning results B Consolidation options for planned freight units | C Incompatibilities D Inclusion of blocked documents 2. Delivery creation can be triggered from SAP TM both interactively and using a batch report. Determine whether this statement is true or false. | True False 3. What are triggers for a delivery update by SAP TM? Choose the correct answers. | A Changing the dates on a DTR B Changing the dates on a freight order C Re-assigning freight units to a freight order with different dates 4. In the case of a delivery split after transportation planning, the DTRs are always removed from planning. Determine whether this statement is true or false. | True False

0



5. Which of the following may be the result of a delivery block on an ERP sales order in SAP TM? Choose the correct answers. | A Planning block B Execution block C Invoicing block D Freight units excluded from delivery creation 6. It is possible to set up delivery proposal creation to include or exclude freight units/orders/ bookings with a planning or execution block. Determine whether this statement is true or false. | True False 7. How are packaging materials incorporated to SAP TM for handling unit integration? Choose the correct answer. | A No master data is needed in SAP TM for packaging materials B Packaging materials can be transferred to SAP TM using the core interface (CIF) 8. Freight units may be adjusted during the transportation requirement consumption process if the integrated ERP delivery includes handling units. Determine whether this statement is true or false. | True False 9. A handling unit can be represented by several freight units in SAP TM. Determine whether this statement is true or false. | True False



Unit 5


1. Which of the following settings can be maintained in the delivery profile? Choose the correct answers. [x ] A Fixing of planning results B Consolidation options for planned freight units

[~xj

C Incompatibilities

[x ] D Inclusion of blocked documents

2. Delivery creation can be triggered from SAP TM both interactively and using a batch report. Determine whether this statement is true or false. [x ] True False

3. What are triggers for a delivery update by SAP TM? Choose the correct answers. | A Changing the dates on a DTR |~X~| B Changing the dates on a freight order [x ] C Re-assigning freight units to a freight order with different dates

4. In the case of a delivery split after transportation planning, the DTRs are always removed from planning. Determine whether this statement is true or false. | True \x \ False Correct. This depends on the Delivery Update/Split Type Customizing (among other things).

0



5. Which of the following may be the result of a delivery block on an ERP sales order in SAP TM? Choose the correct answers.

|~xj

A Planning block

|~xj

B Execution block C Invoicing block

|~xj

D Freight units excluded from delivery creation

6. It is possible to set up delivery proposal creation to include or exclude freight units/orders/ bookings with a planning or execution block. Determine whether this statement is true or false. [x ] True False Correct. This can be maintained in the delivery profile. 7. How are packaging materials incorporated to SAP TM for handling unit integration? Choose the correct answer. | A No master data is needed in SAP TM for packaging materials

|~xj

B Packaging materials can be transferred to SAP TM using the core interface (CIF)

8. Freight units may be adjusted during the transportation requirement consumption process if the integrated ERP delivery includes handling units. Determine whether this statement is true or false. [x ] True False

9. A handling unit can be represented by several freight units in SAP TM. Determine whether this statement is true or false. | True \x \ False



UNIT 6

Transportation Demands for Planning

Lesson 1 Building Freight Units Exercise 11: Define Freight Unit Types Exercise 12: Apply Freight Unit Building Rules Exercise13: Create Freight Units

190 197 205 209

Lesson 2 Building Packages Exercise14: Create Freight Units with Packages

217 225

UNIT OBJECTIVES

0

•

Define freight unit types

•

Create freight units and freight unit building rules

•

Create freight units with packages



Unit 6 Lesson 1 Building Freight Units

LESSON OVERVIEW This lesson examines the freight planning process in SAP TM, including freight unit building rules, the definition of freight unit types, and strategies for freight unit building. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Freight Planning Process

Order Management

Order-based Transportation Requirement

Delivery-based Transportation Requirement

L

I . . . i ________

Freight Unit Building

---- 1..

rf

Freight Unit

Figure 83: Document Flow (Freight Unit Building Focus)

The planning process in SAP TM can be configured to be as flexible as required.



The transportation requirement is the document in TM that initiates and supports the planning process. This allows your company to integrate ERP systems and to track and manage the transportation process. Steps in the Freight Planning Process FU Freight Order

N

OTR Sales Order

FU 10 PRODTM-OO 50pc 1500 kg 20 PRODTM-01 100 pc 3000 kg 30 PRODTM -02 200 pc 6000 kg

FU Figure 84: Freight Planning Process

The planning process is broken up into several steps to manage the transportation process. The transportation requirement initiates the planning process. The next step is to determine a transportation planning unit. This planning unit is called a freight unit. During the planning process, freight units can be grouped together to optimize transportation resources. These are called freight orders.



Freight Unit Types Freight units are: ■

A s e t o f g o o d s t h a t ca n b e tr a n s p o rte d to g e th e r

■

U s e d to m e rg e ite m s t h a t c a n b e tr a n s p o rte d to g e th e r

■

T h e s m a lle s t u n it o f fr e ig h t

■

U s e d in th e p la n n in g o f f r e ig h t

Figure 85: Freight Units

Freight units are created from preceding business documents such as forwarding orders, orderbased transportation requirements, or delivery-based transportation requirements. The system uses either the freight unit type from the freight unit building rule, or the default freight unit type defined in customizing.

Note: The freight unit type consists of a four-character identifier. The freight order type, freight booking type, transportation unit type, and freight unit types must be unique across these three business document types. Within the freight unit type, you can define if a freight unit can be deleted or if it must be canceled.



Freight Unit Type Customizing

Settings Related to the Change Controller

You can assign several different settings related to the change controller. These settings impact how TM responds to changes from the ERP system. Additional Strategies

There are a number of additional strategies: •

Creation Strategy: Specifies tasks that the change controller is to perform when creating a freight order, freight booking, and freight unit.

•

Save Strategy: Specifies tasks the change controller is to perform when saving a freight order, freight booking, and freight unit.

•

Delete Strategy: Specifies tasks that the change controller is to perform when a freight order, freight booking, or freight unit is deleted or canceled.

Execution Settings

There are a number of execution settings: •

Execution Track Relevance: Indicator for controlling the tracking of documents. To track certain types of documents, choose 2 (Execution Tracking) or 3 (Execution Tracking with External Event Management). The system sets the initial document execution status to Not Started. If you do not want to track certain types of documents, choose 1 (No Execution Tracking). The system then sets the initial document execution status to Not Relevant.

•

Immediate Processing checkbox.



Event Management Settings

•

Application Object Type: Type of application object to be tracked on the application system necessary for determining event management relevance for an application object. The event manager only processes event messages for these objects.

•

Last Expected Event for Execution of a Document: Last expected event for a document, for example, the unexpected event UnloadEnd.

Default MTr Definition Settings

•

Default MTr for Type: Indicate the default means of transport type

•

Condition for Default MTr

Default Units of Measure

•

Weight

•

Volume

Direct Shipment Options

•

Direct Shipment Option Type: There are three standard options that include no determination of direct shipment options, automatic determination of direct shipment options, and manual determination of direct shipment options.

•

Carrier Selection Settings: Indicates carrier selection settings that are used for determination of direct shipment options.

•

Carrier Selection Conditions: Specifies the condition that the system uses to determine carrier selection settings for direct shipment processes at runtime.

•

Direct Shipment Strategy: Specifies the process controller strategy that can be used to determine the direct shipment options for a freight unit.

Freight Order Determination

•

Freight Order Type: Default freight order type for direct shipment.

•

Freight Order Type Condition: Condition can be created to decide which freight order type is used for direct shipment.

Organizational Unit Determination

•

Default Org Unit: Execution Organization, Purchasing Organization, Execution Group, Purchase Group. These are the organization numbers that are created in Organizational Structures.•

•

Consider Organization Unit of User check box: Considers the organizational unit assigned to the user that creates the freight unit in the determination of the organizational unit responsible for the freight unit.



•

Condition of Determination Rules: Conditions can be created to effect the organizational unit determination.

Additional Settings

•

Track Changes checkbox: Select this box if changes are to be tracked.





Unit 6 Exercise 11 Define Freight Unit Types

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to define freight unit types required for transportation planning. 1. Review the number ranges used in freight order management in Customizing for SAP TM. (In SAP TM, the freight unit is a view of the transportation order. The number range for freight unit and freight orders is maintained as one object.) 2. In Customizing for SAP TM, choose SAP Transportation Management —>Transportation Management —>Planning —>Freight Unit —*• Define Freight Unit Types. Check and update the freight unit type FU## for the following data:

0

Field

Value

Freight Unit Type

FU##

Description

GR## Freight Unit

Time for Drawing

Draw number when saving document


04

Default Change Strategy

DEF_CHACO

Execution Track Relevance

Execution Tracking with External Event Management

Immediate Processing

Enabled

Direct Shipment Option Type

No Determination of Direct Ship ment Options

Weight

US pound

Volume

Cubic meter

Rule for PU/DLV Window

Pick-Up and Delivery as Defined in FWO, FWQ, OTR, or DTR

Text Schema

ERP_DFLT



Unit 6 Solution 11 Define Freight Unit Types

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to define freight unit types required for transportation planning. 1. Review the number ranges used in freight order management in Customizing for SAP TM. (In SAP TM, the freight unit is a view of the transportation order. The number range for freight unit and freight orders is maintained as one object.) a) In Customizing for SAP TM, choose SAP Transportation Management —*• Transportation Management —*■ Freight Order Management —>Define Number Range Intervals for Freight Order Management. b) Execute the activity. c) Choose$g> (Intervals). d) Explore the intervals defined. You can assign any of the intervals to a freight unit type. Note the number ranges assigned and how a number range is assigned in the next step. e) Exit the activity. 2. In Customizing for SAP TM, choose SAP Transportation Management —>Transportation Management —>Planning —>Freight Unit —► Define Freight Unit Types. Check and update the freight unit type FU## for the following data: Field

Value

Freight Unit Type

FU##

Description

GR## Freight Unit

Time for Drawing

Draw number when saving document


04


DEF_CHACO

Execution Track Relevance

Execution Tracking with External Event Management

Immediate Processing

Enabled

Direct Shipment Option Type

No Determination of Direct Ship ment Options

Weight

US pound



Field

Value

Volume

Cubic meter

Rule for PU/DLV Window

Pick-Up and Delivery as Defined in FWO, FWQ, OTR, or DTR

Text Schema

ERP_DFLT

a) Execute the specified Customizing activity. b) Select the freight unit type FU##. c) Enter the freight unit type and description. d) Enter the data from the table and save your work. e) Exit the Customizing activity.



Freight Unit Building Rules Freight unit building rules are required to plan freight in SAP TM and define how freight units are built. The system determines which freight unit building rule will be taken into account for the business document during planning. Possible input for freight unit building are the following documents: •

Forwarding Orders

•

Order-based Transportation Requirements

•

Delivery-based Transportation Requirements

There are three freight unit building rule determination options, as follows: •

The system checks the condition defined in the business document type (FWO, OTR, DTR). If there is no condition or the condition cannot determine a result, the system moves to the second option.

•

The system checks if a freight unit building rule has been maintained in the business document type (FWO, OTR, DTR). If no freight unit building rule is maintained, the system moves to the third option.

•

The system applies standard settings.

Automatic Freight Unit Creation When creating freight units automatically, the system first groups all business document items within the following parameters:• •

Hard constraints. These include source and destination location, and pick-up and delivery dates.

•

Business document attributes and packaging information

•

Incompatibilities

•

Freight unit building rules

Freight units can be built manually, in a batch job, and automatically upon creation of the predecessor document (FWO, OTR, DTR)..

0



Prerequisites for Creating Freight Units

The prerequisites for creating freight units automatically are: 1. A preceding business document exists. 2. You have defined freight unit types in Customizing. Creating Freight Units

The system considers freight units that already exist for these business documents, and creates one or more freight units from these groups. If you define a split quantity and select the checkbox for the item split, the system considers these entries when creating multiple freight units. You can specify an FUB rule when automatically creating freight units. If you do not specify an FUB rule, the system automatically determines the FUB rule. Use strategies to create freight units in accordance with your own requirements. SAP delivers the standard strategy f u b _a u t o for freight unit building.



FUBR Specifications

Within the freight unit building rule, a company must specify the critical quantity. This parameter defines the primary unit of measure that allows a line item on a transport requirement to be split into multiple freight units. Besides that, several planning quantities can be defined, for example, weight and volume. Every planning quantity is considered for capacity checks of resources during transportation planning, and every planning quantity is copied to the freight unit. The split quantities define the maximum capacity of a freight unit. The system calculates the freight unit as a multiple of the rounding quantity. If Item Split Allowed is selected, the freight unit splits the item while it is being built, if it is over the split quantity. The process controller strategy allows you use strategies to define the way in which freight units are created in accordance with your requirements. If you maintain an equipment type in the freight unit building rule, the capacity of the equipment is considered during freight unit building and the items consolidated into one freight unit are loaded into the equipment.



Freight Unit Building Rule Strategy Consolidate Per Item FU

Sales

Order/OTR

PRODTM-OO

10 PRODTM-OO 50pc 1500 kg 20 PRODTM-01 100 pc 3000 kg 30 PRODTM-02 200 pc 6000 kg

PRODTM-01 FU

PRODTM-02 Figure 89: Rule Strategy Consolidate per Item (Do not Consolidate)

One freight unit building rule strategy is to consolidate per item. This strategy creates separate freight units for each item in the transportation requirement. Consolidate per Request (Compatible Parts)

Sales

Order/OTR

10 PRODTM-OO 50 pc 1500 kg 20 PRODTM-01 100 pc 3000 kg 30 PRODTM-02 200 pc 6000 kg

—

►

PRODTM-02 Figure 90: Rule Strategy: Consolidate per Request (Compatible Parts)



Another freight unit building rule strategy is to consolidate per request for compatible parts. The system groups all the items of a business to form a freight unit. It is assumed that compatibility rules are used to group similar items.

Consolidate as Much as Possible

Sales Order/OTR 10 PRODTM-OO 50pc 1500 kg

FU- A001

Sales Order/OTR 10 PRODTM-Ol 100 pc 3000 kg

\1 ___________

10 PRODTM-OO 20 P R O D TM -O l 30 P R O D TM -02

Sales Order/OTR 10 PRODTM-02 200 pc 6000 kg

\ l ______ Figure 91: Rule Strategy Consolidate as Much as Possible

Another freight unit building rule strategy is to consolidate as much as possible. This strategy can only be used with interactive FU creation from POWL or via a batch report. It consolidates several transportation requirements into one freight unit, if there are no other reasons for a split.

0



Apply Freight Unit Building Rules

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to define and apply freight unit building rules required for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Define Freight Unit Types.

1. In NWBC, create a freight unit building rule. Allow an item split. Use the following data: Field

Value


Document Type

FBR## GR## FreightUnit Building Rule FU##

Freight Unit Building Strategy

Consolidate per Item

Critical Quantity

Gross Weight

Item Split Allowed

Enabled

Planning Quantity for Freight Unit Building

Gross Weight

Unit of Measure of Split Quantity

LB 45000 FUB_AUTO

Description

Split Quantity Process Controller Strategy

2. In Customizing for SAP TM, assign your new freight unit building rule FBR## to your new transportation requirement type TR##.

0



Apply Freight Unit Building Rules

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to define and apply freight unit building rules required for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Define Freight Unit Types.

1. In NWBC, create a freight unit building rule. Allow an item split. Use the following data: Field

Value


FBR##

Description

GR## Freig htU n it Building Rule

Document Type

FU##

Freight Unit Building Strategy

Consolidate per Item

Critical Quantity

Gross Weight

Item Split Allowed

Enabled


Gross Weight


LB

Split Quantity

45000

Process Controller Strategy

FUB_AUTO

a) In NWBC, choose Application Administration —> Planning —> General Settings —> Freight Unit Building Rule —*• Create Freight Unit Building Rule. b) Select the General Data tab. c) Enter the data from the table. d) Select the Advanced Settings tab. e) Enter the data from the table.



f) Save your new freight unit building rule. 2. In Customizing for SAP TM, assign your new freight unit building rule FBR## to your new transportation requirement type TR##. a) In Customizing for SAP TM, choose SAP Transportation Management —> Transportation Management —> Integration —> ERP Logistics Integration —>Order- Based Transportation Requirement —► Define Order -Based Transportation Requirement Types. b) Choose

Execute.

c) Select your new TR## and choose

Details.

d) Enter the freight unit building rule FBR## in the Freight Unit Building Rule field. e) Enable automatic freight unit building by selecting the corresponding checkbox. f) Save your data.





Create Freight Units

Business Example

As part of the transportation planning and execution process in your company, you need to be able to generate freight units, both from OTRs in a worklist, and using automatic freight unit creation.

Note: Required: This exercise is dependent on the completion of the exercise Apply Freight Unit Building Rules. Create a Freight Unit Using Automatic Freight Unit Creation

1. In SAP ERP, create a new sales order to generate a new transportation requirement in SAP TM. Use the following data: Field

Value

Order Type

ZT##

Sales Organization

3000


10

Division

00

Sold-to Party

CustOO-17

PO Number

GR##_201

Material

PRODTM-OO

Quantity

50

2. Identify the resulting transportation requirement in SAP TM, using the POWL. 3. What is the life cycle status of the transportation requirement?

4. Open the transportation requirement to review the document flow. 5. Open the new freight unit and review the data.

0



6. Which document type (freight unit type) was used?


Change Customizing to Prevent Automatic Freight Unit Building

1. Remove the flag automatic freight unit building from OTR type TR## Create a Freight Unit from the Personal Object Worklist (POWL)


Value

Order Type

ZT##

Sales Organization

3000


10

Division

00

Sold-to Party

Cust00-17

PO Number

GR##_201

Material

PRODTM-OO

Quantity

50

2. In SAP TM, create freight units directly using the POWL. 3. What is the new life cycle status of the transportation requirement?

4. Open the transportation requirement to review the document flow. 5. Open the newly created freight unit and review the data. 6. Which document type(freight unit type) was used?




8. Review the item data.

0



Create Freight Units

Business Example

As part of the transportation planning and execution process in your company, you need to be able to generate freight units, both from OTRs in a worklist, and using automatic freight unit creation.

Note: Required: This exercise is dependent on the completion of the exercise Apply Freight Unit Building Rules. Create a Freight Unit Using Automatic Freight Unit Creation


Value

Order Type

ZT##

Sales Organization

3000


10

Division

00

Sold-to Party

CustOO-17

PO Number

GR##_201

Material

PRODTM-OO

Quantity

50

a) On the SAP Easy Access screen, start transaction v a o i ,or choose Logistics —*• Sales and Distribution —> Sales —> Order. b) On the initial screen, enter the relevant data from the table and then press ENTER. c) On the overview screen, enter the remaining data from the table and press ENTER. d) Save your work and make a note of the sales order number:________________ 2. Identify the resulting transportation requirement in SAP TM, using the POWL.



a) In NWBC, choose ERP Logistics Integration —> Worklist —*■ Overview Transport Requirements. b) Choose Refresh at the top of your worklist. c) Locate the sales order number you recorded. 3. What is the life cycle status of the transportation requirement? In Planning._________________________________________________________________ 4. Open the transportation requirement to review the document flow. a) Click the document number to open the transportation requirement. b) Open the Document Flow tab. c) Verify that a freight unit has been created. 5. Open the new freight unit and review the data. a) In the document flow, click the freight unit number. b) On the General Data tab, review the locations, dates, and weight. c) Review the Label and verify that it corresponds to the sales order number. 6. Which document type (freight unit type) was used? FU##______________________________________________________________________ 7. Which freight unit building rule was used? FBR##_____________________________________________________________________ Change Customizing to Prevent Automatic Freight Unit Building

1. Remove the flag automatic freight unit building from OTR type TR## a) In Customizing for SAP TM, choose SAP Transportation Management —> Transportation Management —> Integration —► ERP Logistics Integration —> Order- Based Transportation Requirement —> Define Order -Based Transportation Requirement Types. b) Double-click on OTR type TR##. c) Remove the flag automatic freight unit building. d) Choose Save. Create a Freight Unit from the Personal Object Worklist (POWL)


Value

Order Type

ZT##



Field

Value

Sales Organization

3000


10

Division

00

Sold-to Party

Cust00-17

PO Number

GR##_201

Material

PRODTM-OO

Quantity

50

a) On the SAP Easy Access screen, start transaction v a o i ,or choose Logistics Distribution —> Sales —> Order.

—*■

Sales and

b) On the initial screen, enter the relevant data from the table and then press ENTER. c) On the overview screen, enter the remaining data from the table and press ENTER. d) Save your work and make a note of the sales order number:_________________ 2. In SAP TM, create freight units directly using the POWL. a) In NWBC, choose ERP Logistics Integration —► Worklist —> Overview Transportation Requirements. b) Identify your previously created transportation requirement and verify that the life cycle status is New. c) Select your transportation requirement and choose Create Freight Units. 3. What is the new life cycle status of the transportation requirement? In Planning__________________________________________________________________ 4. Open the transportation requirement to review the document flow. a) Click the document number to open the transportation requirement. b) Open the Document Flow tab. c) Verify that a freight unit has been created. 5. Open the newly created freight unit and review the data. a) In the Document Flow tab, click the freight unit number. b) On the General Data tab, review the locations, dates, and weight. c) Review the Label and verify that it corresponds to the sales order number.



6. Which document type(freight unit type) was used? FU##________________________________________________________ 7. Which freight unit building rule was used? FBR##_______________________________________________________ 8. Review the item data. a) On the Items tab, scroll to the right to review the assigned requirement. b) Select the item and review the product details.




•


•




Unit 6 Lesson 2 Building Packages

LESSON OVERVIEW This lesson examines package building in the SAP Transportation Management (TM) planning process. At the end of the lesson, you will be able to create freight units with packages. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Package Building Overview

New rule-based package building engine (SCMB) • Builds product pallets and mixed pallets (layered) • Considers product master data • Considers product to package & equipment type assignment • Considers package building profile Integrated into freight unit building • Creates package items in freight unit • Can also create freight orders, trailer units, railcar units, container units

Figure 92: Package Building Overview

Orders are placed on products which, during the real process, are packaged to create packages and pallets (HUs, TUs, main cargo items, and so on). Packaging is a warehouse process. Warehouse specific information can influence the result (for example, pick sequence). For the end-to-end process, the package information is required long before the warehouse is reached. The goal for SAP TM is to close the gap between orders based on products and the load planning happening for packages and pallets, as well as to enable a package building function that

0



considers warehouse information. Therefore, readily available packaging components and product master data packaging-specific definitions are reused. Package Building in the SAP Transport M anagem ent (T M ) Planning Process

Package Building is inserted into the overall planning process at the freight unit building step. It allows products to be combined into packages. These packages (within freight units) are later used in subsequent planning steps (manual and optimizer planning (VSR) to create freight orders and subsequent load planning).



Package Building P aram eters

Package Type Determination (Business Partner, Location...) Maximum Package Height, Package Type (Unit of Measure) Item Split Factor Determination

Package Building

Alternative Quantities for Packages and Layers MD Material/ Product

t ERP Figure 94: Parameters for Package Building

Package building is defined by the package building profile. This enables certain process steps to be switched on or off, specific behavior to be defined (especially when building mixed packages), and also offers default attributes that can be overwritten by product specific settings. The following are examples of parameters: Process Products by Layer This parameter can turn off the creation of full product packages. By default, this is very seldom required, but gives a mixed package building logic more freedom. For example, a certain customer always requires a specific product combination (even when ordering a high quantity), this can then be implemented in an enhancement receiving a full set of products. Keep Layers Together When building mixed packages, the parameter controls of a product can be split over multiple mixed packages. In some situations, this might result in a better and more efficient plan. However, in more warehouse driven scenarios, it might not be efficient to process a product twice for two packages. Therefore, it can be turned off.

Note: This behavior can be defined more specifically on a product or business partner level. Ignore Product Height When consolidating leftover products that are not filling a complete package, nor a complete product layer, the system tries to build mixed layers combining products with the same



height. This step can be skipped if the product height is not important. As a result, all of the leftover product quantities can be combined directly resulting in standard non-stackable layers. The package building profile is assigned to the freight unit building rule. In addition, for freight unit building you can define the maximum number of package items that can be put into a single freight unit. Product and Package Type Assignm ent

Package M aster Data

The most important definitions on package material level are as follows: Base Unit of Measure Points to the product master data conversion rules (if not overwritten in the product and package type assignment). Weight, Length, Width, and Height of the Package Material Considered when calculating the weight and dimension of the final package containing products. Maximum Weight of the Package Package weight + product weight. This can be reduced in the product package type assignment. Maximum Height of the Package Package height + product height. This can be reduced in the product package type assignment. Closed Package The height is fixed, even if the package is not full.



Product Master Data

The following can be defined at product level, under alternative units of measure: Single product item attributes like weight, length, width, and height These are considered during package attribute determination and mixed package building. How many pieces of a product fit into a full package This is defined by the package unit of measure and includes a definition of how high such a package is. How many pieces fit into a full product layer This is defined by layer unit of measure.

Note: In the product and package type assignment you can specify the layer unit of measure to be used.

Product and Package Type Assignment

The product and package type assignment is a new master data transaction that defines, for each product in the package builder, which package it goes into or onto. To reduce the effort when maintaining those definitions, it is possible to work with generic patterns. The definition can be dependent on the product, business partner, and location. For example, product A is usually delivered with an EU pallet stacked up to 1.5 meters (first entry). However, when delivering this product to customer X from your warehouse Y, you use a different pallet type containing product A stacked up to 1.3 meters, because the customer can only handle pallets up to this height (second entry as exception). The package builder will always prefer the most specific entry. It will start to search for an entry matching all 3 key fields exactly. If nothing is found, it will score all other keys in the following manner: •

How many keys match exactly?

•

How many keys match by pattern?

•

How many keys are initial?

It will then select the key with the highest score.

Note: The package builder will always only pick one entry, rather than combining two.



Package Building S elected Features Layer Types • Define number of product pieces inside layer type • Define number of layers in package type

Package Types

• Consider different package types (length, width, height, weight) • Required package type and allowed maximum height may depend on product & customer

Figure 96: Selected Features of Package Building

The product and package type assignment defines the target package type. One option is to set the package material. When doing so, the base unit of measure of the package, the dimensions, and the weight are all considered. The second option is to set the package unit of measure. This points directly to the product-alternative units of measure for the conversion rules, but no package attributes are considered. When set in combination with the package material, it can overrule the base unit of measure of this package. The third option is to set the definition of the equipment group and type. In SAP TM, this enables the creation of container, trailer, or railcar units. It does not affect the logic, but the package unit of measure must also be defined. Furthermore, the definition allows specific limits to be set regarding the weight and height that the package builder will consider when packing the product. It is possible to set generally valid limits on the package material (i.e. product master data). For example, you can only stack a EU pallet up to 1.8 meters and put 900 kg on it. In the product and package type assignment, you can lower the specific product, customer, and location limits. Stacked Packages

•

Built package item contains data needed for load planning (length, width, height, weight).

•

Pack material required -

One per pallet vs.

-

One below each product layer in a package

Finally, there are flags to steer the process when creating mixed packages and pallets. The layer unit of measure field points to the product master data defintion required to create a mixed package (how many pieces fit into a product layer). In addition, you can define whether a product can be split over multiple mixed packages, if additional packing material is required, and how mixed product layers shall be created.



Package Building Logic M ixed Package B uildin g (phase 2)

P ro d u ct Package B uilding (p hase 1)

M ixed Pallets

P ro du ct Pallets Full

aa

a^

Full

Incom plete

Incom plete

/ _____ / 100 pieces 30 pieces

130 pieces P ro du ct A

/

\

60 pieces 10 pieces

/

10 pieces

mm

10 pieces

70 pieces P ro d u ct B

V r

/

13 pieces P ro d u ct C Result: 7 pallets

Result: 6 pallets

Figure 97: Logic of Package Building

Step 1 Full package building. Step 2 Mixed package building takes the incomplete product pallets as input and combines them into mixed pallets, in order to minimize the total number of pallets. Mixed Package Building (Phase 2 )



Mixed Package Building based on Full Product Layers

•

Split incomplete Product Packages into Product Layers

•

Combine Layers to build Mixed Packages and consider: -

Maximum package height (customer specific)

-

Product compatibility and stacking rules

-

Layer compatibility (incomplete on top)



Unit 6 Exercise 14 Create Freight Units with Packages

Business Example Product Pallet Building Product Pallets


PB1 ## 90 pieces

1 Freight Unit 180 pieces PB PROD A

□

m

60 pieces PB PROD B

PB2 30 pieces

m 2 Freight Units

Result: 4 pallets in total

Figure 99: Create Freight Units with Packages

In this scenario you create a forwarding order with multiple product items. The goal is to put these product items onto pallets by minimizing the number of pallets considering constraints like pallet attributes, product stacking rules, and customer specific requirements. For product A the freight unit Building rule is set up the way that 1 freight unit can consist of a maximum of 10 pallets. For product B the freight unit building rule is set up the way that for each pallet a separate freight unit is created.

Note: Required: This exercise is dependent on the completion of the exercise Create Freight Units. Create a Package Building Profile for Package Building

1.

Create a package building profile that allows the creation of pallets during freight unit building.

Set Up Forwarding Order Management for Package Building

1. Create two freight unit building rules that allow the creation of packages for each forwarding order item. The first FUBR PB1_## allows multiple packages (pallets) in one freight unit, whereas the second FUBR PB2_## creates one freight unit for each package.

0



2. Create a condition PB_FUBR_COND_## to determine the freight unit building rule during freight unit creation. This freight unit building rule is determined based on the product maintained in the forwarding order item. 3. Create a forwarding order type (PB##) by copying forwarding order type FWOX, and assign the freight unit building rule condition (PB_FUBR_COND_##). Additional System Set Up for Package Building

1. Check Product Package Type Assignment. Here, each product is assigned to a specific package type (pallet). 2. To which package are products PB_PROD_A and PB_PROD_B assigned?

3. What is the maximum height of a package of product PB_PROD_A?

4. Review the master data of product PB_PROD_A. How many pieces of product PB_PROD_A can be consolidated into 1 layer (LY1)?

How many pieces of product PB_PROD_B can be consolidated into one package (PL1)?

What is the length, width, and height of one piece?

What is the height of one layer?

Create a Forwarding Order for Package Building



1. Create a forwarding order to test the creation of packages during freight unit building. Use the data from the table to create the forwarding order: Field

Value

Forwarding Order Type

PB##

Movement Type

T2C

Ordering Party

CUST00-25

Shipper

SP3100

Consignee

CUST00-25

Source Location

SP3100

Pick-Up Date

Today + 3 workdays


CUST00-25

Delivery Date

Today + 5 workdays

2. On Item Level, choose Insert Product and make the following entries: Field

Value

Item Type

PRD

Product

PB_PROD_A

Quantity

180

Quantity Unit of Measure

PC


Value

Item Type

PRD

Product

PB_PROD_B

Quantity

60


PC

4. Check the creation of all freight units belonging to your forwarding order. How many freight units have been created?



5. Note down all freight unit document numbers.

6. Identify the freight unit created for PB_PROD_A. Which freight unit building rule has been used for its creation?

How many packages have been created?

7. Identify the freight units created for PB_PROD_B. Which freight unit building rule has been used for their creation?

How many packages have been created in each freight unit?



Unit 6 Solution 14 Create Freight Units with Packages

Business Example Product Pallet Building Product Pallets


PB1_##

1 Freight Unit 180 pieces PB PROD A PB2_##

□

2 Freight Units

m

60 pieces PB PROD B

Result: 4 pallets in total

Figure 99: Create Freight Units with Packages

In this scenario you create a forwarding order with multiple product items. The goal is to put these product items onto pallets by minimizing the number of pallets considering constraints like pallet attributes, product stacking rules, and customer specific requirements. For product A the freight unit Building rule is set up the way that 1 freight unit can consist of a maximum of 10 pallets. For product B the freight unit building rule is set up the way that for each pallet a separate freight unit is created.

Note: Required: This exercise is dependent on the completion of the exercise Create Freight Units. Create a Package Building Profile for Package Building

1. Create a package building profile that allows the creation of pallets during freight unit building. a) In Customizing, go to SAP Transportation M anagem ent^ SCM Basis —» Pack —» Package Building —> Define Package Building Profile. b) Choose New Entries and make the following settings:

0



Field

Value

Profile

PB##

Description

TM200 Package Building Grp # #

Keep Layers Together

Check

c) Choose Save. Set Up Forwarding Order Management for Package Building

1. Create two freight unit building rules that allow the creation of packages for each forwarding order item. The first FUBR PB1_## allows multiple packages (pallets) in one freight unit, whereas the second FUBR PB2_## creates one freight unit for each package. a) In NWBC, goto Application Administration —» Planning—> General Settings —> Freight Unit Building Rule —> Create Freight Unit Building Rule. b) Enter the following data for FUBR 1: Field

Value


PB1_##

Description

TM200 PB FUBR1 # #

Document Type (Freight Unit Type)

PBFU

Critical Quantity

Gross Weight


Gross Weight


LB

Rounding Quantity

1

c) Go to tab Advanced Settings and enter the following data: Field

Value

Package Builder Profile ID

PB##

Maximum Number of Packages per FU

10 (in order to create 1 FU for every 10 pal lets)

d) Save your freight unit building rule. e) In NWBC, goto Application Administration —*• Planning—> General Settings —> Freight Unit Building Rule —> Create Freight Unit Building Rule. f) Enter the following data: Field

Value


PB2_##

Description

TM200 PB FUBR2 ##



Field

Value

Document Type (Freight Unit Type)

PBFU

Critical Quantity

Gross Weight


Gross Weight


LB

Rounding Quantity

1

g) Go to the Advanced Settings and enter the following data: Field

Value

Package Builder Profile ID

PB##

Maximum Number of Packages per FU

1 (in order to create 1 FU per pallet)

h) Save your freight unit building rule. 2. Create a condition PB_FUBR_COND_## to determine the freight unit building rule during freight unit creation. This freight unit building rule is determined based on the product maintained in the forwarding order item. a) In NWBC, goto Application Administration —» General Settings —*■ Conditions—> Create Condition. b) Enter the following data: Field

Value

Condition

PB_FUBR_COND_##

Description

TM200 PB FUBR Cond ##

Condition Type

/SCMTMS/FUBR

Origin of Condition

Condition based on BRFplus Decision Table

c) Choose Continue. d) Go to Data Access Definition. e) Delete both default data access definitions and create the following data access definitions: Field

Value

Name of BO Used in Condition

/SCMTMS/TRQ

Name of BO Node Used in Condition

ITEM

Name of the Field of the BO Node

PRODUCTJD

Filter Definition for Data Access Definition

ITEM_CAT



Field

Value

Key Field Value for BO Node Identif.

PRD

f) Go back to the Decision Table and maintain it in the following way: Field

Value

Product

FUB Rule

PB_PROD_A

PB1_##

PB_PROD_B

PB2_##

g) Save the condition. 3. Create a forwarding order type (PB##) by copying forwarding order type FWOX, and assign the freight unit building rule condition (PB_FUBR_COND_##). a) In Customizing, go to SAP Transportation Management —> Transportation Management —*• Forwarding Order Management —> Forwarding Order —> Define Forwarding Order Types. b) Highlight Forwarding Order Type FWOX. c) Choose Copy. d) Enter the following data:_____________________________________________________ Field

Value


PB##

Description

Forwarding Order Type (TM200) Group # #

FU Building Rule Condition

PB_FUBR_COND_##

e) Save your entries. Additional System Set Up for Package Building

1. Check Product Package Type Assignment. Here, each product is assigned to a specific package type (pallet). a) In NWBC, go to Master Data —» General—> Define Product Package Assignment. 2. To which package are products PB_PROD_A and PB_PROD_B assigned? PB_EUROPAL__________________________________________________________ 3. What is the maximum height of a package of product PB_PROD_A? 1,644m________________________________________________________________ 4. Review the master data of product PB_PROD_A.



How many pieces of product PB_PROD_A can be consolidated into 1 layer (LY1)? On the Unit of Meas. tab: 15 How many pieces of product PB_PROD_B can be consolidated into one package (PL1)? On the Unit of Meas. tab: 90 What is the length, width, and height of one piece? On the Unit of Meas. tab: length: 30 mm, width: 20 mm, height: 25 mm What is the height of one layer? On the Unit of Meas. tab: height: 25 mm_________________________ a) In NWBC, go to Master Data —► General —» Define Product. b) Enter product PB_PROD_A and select Global Data. c) Choose Display. Create a Forwarding Order for Package Building

1. Create a forwarding order to test the creation of packages during freight unit building. Use the data from the table to create the forwarding order: Field

Value


PB##

Movement Type

T2C

Ordering Party

CUSTOO-25

Shipper

SP3100

Consignee

CUSTOO-25

Source Location

SP3100

Pick-Up Date

Today + 3 workdays


CUSTOO-25

Delivery Date

Today + 5 workdays

a) In NWBC, goto Forwarding Order Management —► Forwarding Order —> Create Forwarding Order.



b) On the initial screen, enter the following data and continue: Field

Value


PB##

Movement Type

T2C

c) Change to Fast Order Entry (Land) view and enter the data from the table: Field

Value

Ordering Party

CUST00-25

Shipper

SP3100

Consignee

CUST00-25

Source Location

SP3100

Pick-Up Date

Today + 3 workdays


CUST00-25

Delivery Date

Today + 5 workdays


Value

Item Type

PRD

Product

PB_PROD_A

Quantity

180


PC


Value

Item Type

PRD

Product

PB_PROD_B

Quantity

60


PC

a) Choose Enter. b) Save the forwarding order.



c) Note down the forwarding order number.

4. Check the creation of all freight units belonging to your forwarding order. How many freight units have been created? 3 freight units have been created._______________________________________________ a) In NWBC, goto Forwarding Order Management —> Forwarding Order —> Display Forwarding Order. b) Enter your forwarding order document number. c) Open the Document Flow tab. 5. Note down all freight unit document numbers.

6. Identify the freight unit created for PB_PROD_A. Which freight unit building rule has been used for its creation? PB1_## How many packages have been created? 2 packages with 1 palette and 90 PC each.__________________ 7. Identify the freight units created for PB_PROD_B. Which freight unit building rule has been used for their creation? PB2 ## How many packages have been created in each freight unit? 1 package with 1 palette and 30 PC each.________________




•




Unit 6

Learning Assessment

1. Which settings can be maintained in freight unit type Customizing? Choose the correct answers. | A Change Controller Settings B Pickup/Delivery Settings | C Execution Settings D Dangerous Goods Settings 2. A freight unit can only be assigned to a single freight order or freight booking. Determine whether this statement is true or false. | True False 3. Which of the following are reasons for an automatic freight unit split during freight unit building, using the default freight unit building strategy? Choose the correct answers. | A Vehicle resource capacities B Non-unique source or destination locations C Split rules and quantities in the freight unit building rule D Incompatibilities

0




1. Which settings can be maintained in freight unit type Customizing? Choose the correct answers.

|~xj

A Change Controller Settings

|~xj

B Pickup/Delivery Settings

|~xj

C Execution Settings

|~xj

D Dangerous Goods Settings

2. A freight unit can only be assigned to a single freight order or freight booking. Determine whether this statement is true or false. | True \x \ False Correct. A freight unit could be assigned to a freight order for pre-carriage and a freight booking for main carriage, for example. 3. Which of the following are reasons for an automatic freight unit split during freight unit building, using the default freight unit building strategy? Choose the correct answers. | A Vehicle resource capacities

|~xj

B Non-unique source or destination locations

|~xj

C Split rules and quantities in the freight unit building rule

|~xj

D Incompatibilities



UNIT 7

Transportation Planning

Lesson 1 Defining the Transportation Planning Process

240

Lesson 2 Evaluating Freight Units Exercise 15: Examine a Freight Unit

246 249

Lesson 3 Creating Freight Orders for Shipping Exercise 16: Create a Freight Order

257 263

UNIT OBJECTIVES

0

•

Identify the business process and documentation required for transportation planning

•

Examine freight unit management of individual shipping requirements

•

Create freight orders



Unit 7 Lesson 1 Defining the Transportation Planning Process

LESSON OVERVIEW Your business receives orders for the products it manufactures and then ships these products to the end customer. SAP TM has the capability to perform advance planning to increase your company’s service level and increase profitability.

In this lesson, you examine the planning capabilities of SAP TM. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Reasons for Transportation Planning The goal of SAP Transportation Planning (TM) is to enable customers to either manually or automatically plan and optimize their transportation requests. This includes the ability to perform order consolidation, where a company can group orders with the same ship-from and ship-to locations for more efficient transportation quantities. If multiple orders are being shipped within a predefined transportation zone, your company can try to efficiently schedule and route the multiple orders, and chose the appropriate carrier. The planning and selection can be determined using the most cost effective and timely route from source to destination while considering realworld constraints, costs, and penalties. The optimizer is capable of making multi-modal decisions such as sea, air, truck, train, and any combination thereof. The SAP TM planning function can also perform multi-pickup and stop options. Within the optimization algorithm is the ability to utilize the appropriate resources in terms of availability and capacity. The optimizer can consider incompatibility rules to restrict how freight orders are built, for example, modeling material-specific transport requirements (cooled products). In addition, carrier selection allows your company to determine the right combination of carrier assignments based on cost, equipment availability, priority, and business share goals. Order Consolidation

Order consolidation is the grouping of orders with the same ship-from and ship-to locations to create more efficient shipment quantities. The result of order consolidation is that one or more freight units are combined into one freight order. A freight unit is a business object representing the smallest possible transportation unit. Business examples of order consolidation are multiple orders that have been received over time and can be planned to be shipped together. This can be at individual line item level. Customers who make-to-order, and do not ship complete orders to their customers, may consolidate line items from multiple orders as they are produced and as their delivery-due lists are created.



Routing and Scheduling

The figure Routing, Scheduling and Carrier Selection outlines the process of routing and scheduling in the following way: a freight unit X is first routed using the transportation planning function, for example, a transportation proposal. Based on this routing, three stages are created for freight unit X, as follows: •

A stage for US road pick-up transport

•

A stage for the ocean voyage

•

A stage for EU road delivery transport

Up to a certain point, these stages are planned independently of each other because different (local) planners may be responsible for scheduling each of the three stages. A freight order is created as a result of this stage. Finally, carriers are selected based on specific criteria. This is described as a three-step process but a planner can decide whether to perform planning and carrier selection in two steps or three. It is also possible for the SAP TM optimization function to plan all three steps in one run - this planning strategy is called one step optimization. Process Steps

The steps involved in the process, whether one, two or three step can be described as follows: •

Three step 1. Determine routing (transportation proposal) 2. Vehicle scheduling and routing to create a freight order 3. Carrier selection

•

Two step



1. Vehicle scheduling and routing to create a freight order 2. Carrier selection •

One step 1. One-step optimization determines the route and plan, creates a freight order and selects a carrier

Manual and Automatic Transportation Planning

Transportation planning activities in SAP TM can be performed manually and automatically, as well as interactively and in the background. For interactive planning, the central planning Ul is the transportation cockpit. Both manual and automatic planning activities are performed there based on planning strategies (for example, one-step optimization). Planning Constraints

SAP TM can consider numerous constraints during planning. Which ones are relevant and should be used in a specific scenario largely depends on the scenario itself. Constraints can have physical root causes, such as vehicle capacity or handling capabilities for loading and unloading at certain facilities. On the other hand, constraints can have process-related root causes. For example, a delivery tour should have a maximum of 25 drops in a day. This is a maximum that will fit in a driver’s daily schedule, assuming he has to unload at the door and do some paperwork for each customer drop. Assets, Facilities, Resources and Times

There are a number of assets, facilities, resources, and times: •

Vehicle capacity



•

Vehicle combinations (truck and trailer)

•

Compartments

•

Depot locations

•

Handling resources, opening hours (calendars and shift patterns)

•

Schedules

•

Incompatibilities — constraints by design

Process and Execution Constraints

There are a number of process and execution constraints: •

Vehicle load level

•

Decreasing capacities

•

Max number of transshipment locations

•

Max limits on distance, duration, or stopovers

•

Pick-up and deliver time windows

•

Min and max storage time at hub — cross-docking changeover

•

Loading and unloading durations

•

Scheduling constraints

Transportation Planning Document Structure Planning relies on the following three distinct pillars: •

Master Data Master data objects such as the transportation network (locations, transshipment hierarchies, transportation zones and transportation zone hierarchies, and transportation lanes) and resources are the basis for any planning activities in SAP TM.

•

Selection Profiles Selection profiles specify what should be planned in a certain scenario. For example, selection profiles specify the geography for which a transportation plan shall be created. This could be, for example, all freight units to be transported within California.

•

Planning Profiles Planning profiles specify the “ how" of the process. For example, a planner may only be allowed to schedule standard trucks and not a helicopter for emergency transports. This information dictates how the actual transportation is to be carried out. In the planning profiles, you can specify the resources to use and at what cost.



Planning Profiles

Planning Profile ■ ■

Planning strategy

I

Selection Profiles

Transportation Network /

Geographical Selection

Geography

Attributes

a Transportation zones

Planning horizon

■

a Transportation lanes

Capacity Selection ■

Master Data

a Freight bookings

selection of transportation

a Transshipment locations

Vehicles, trailers

requirements

Resources

a Schedules Planning Cost Settings

i

a Mean of transport

Considering partiallyplanned transportation

a Vehicles, vehicle

requirements (freight units)

combinations

a Penalty costs

Constraints

Optimizer Settings a Proposal settings

Time-Related Selection Attributes

a Operating times

■

a Handling Resources

a Runtime

Using any attribute of the locations or zones for the

a Maximum number of

Pick-up and delivery time windows

Additional Selection Attributes

transshipment locations

i

Additional selection attributes

i

Additional flexible filters

Incompatibilities

Figure 102: SAPTM Planning

Transportation Planning Document Flow SAP ERP

,

1

Sales Order / Purchase Order

Delivery

Forwarding Quotation

1 Order-based Transportation Requirement

:------------- 4 ------------ 1 Delivery-based Transportation Requirement

Forwarding Order

Execution / Subcontr.

Charges / Settlement

S

Freight Settlement Document

Forwarding Settlement Document

Rate Table

Figure 103: SAP TM Document Flow (End-to-End)



The standard planning process begins with creating freight units out of transportation requests. Any of the following may prompt the creation of a freight unit: •

Forwarding Order (FWO)

•

Order-based Transportation Requirement (OTR)

•

Delivery-based Transportation Requirement (DTR)

Short-cut Process Flow

Once created, freight units are used by manual or automatic planning activities to build freight orders, which can subsequently be used for carrier selection or tendering processes. The purpose of the short-cut process is to skip any planning activities, because these may not be required in certain scenarios. For example, if the sales orders that are received by a company already state the required truck size, the freight order could be created directly from the transportation requirement (in this example, an OTR). Technically, this is done during freight unit building by selecting a freight order type instead of a freight unit type.*•

Standard process flow Order Management

Planning

FU

[=£►

FO

< =

Execution / Subcontracting

1P Shortcut process flow (no freight units, no planning) Order Management

P> FO <=

Execution / Subcontracting

Figure 104: Planning View on the Business Objects


•




Unit 7 Lesson 2 Evaluating Freight Units

LESSON OVERVIEW This lesson examines the role of freight units. You explore how freight units are created from transportation requirements such as forwarding orders or order and delivery based transportation requirements. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Freight Units in Planning

Header

Item 1

Standard order Sold-to party Ship-to party Item Material

2387 4876

Quantity

Schedule line 1 10

Item 2 Schedule line 1 Schedule line 2

1400-100

20 PC

Nov 01

20 PC

1400-200

50 PC

1

Nov 01

20 PC

2

Jan 01

30 PC

1

20

Figure 105: Purpose of Freight Units

A sales order originating in SAP ERP will usually comprise a number of different items with different schedule lines. This may be because the customer requires the goods at different points in time, or because of some other specific issue of compatibility or timing. For example, let's assume a retailer orders ice-cream and milk in bulk quantities from its supplying dairy. Because of different temperature requirements, these cannot be shipped in the same truck. Furthermore, if the quantities (by schedule line) exceed a truck capacity, the schedule lines may need to be split because of capacity considerations. A freight unit is an object in SAP TM that groups items that are transported together. Freight units can be created per item and schedule line, but freight units can also group (consolidate) different items if these have similar characteristics with



respect to their transportation options. The same applies to forwarding orders and deliverybased transportation requirements (DTRs). Freight Unit Creation

The most convenient way to create freight units is to create them automatically, based on their predecessor document (FWO, OTR, DTR). Freight units can also be created using a background report, and the creation of freight units can be manually triggered from worklists. If it arises during planning that a freight unit has to be adapted (split or merged, for example), this can be done manually in the transportation cockpit. Freight Units in Planning

As a result of integration with SAP ERP (or another enterprise resource planning system), one or more freight units are generated for each transportation requirement being planned in SAP TM. A freight unit may therefore be described as a collection of goods that are transported together across the entire transportation chain. A freight unit can include transportation constraints that are referenced during transportation planning. A freight unit can be used to merge items from the following business documents that are to be transported together - FWO, OTR, DTR. Freight units are built on the foundation provided by business document data and freight unit building rules. The most important settings for the freight unit are defined in the freight unit type. The freight unit type allows for settings to be applied in the following areas: •

Customizing options

•

Controller maintenance

•

Checks in relation to creating, saving and deleting

•

Tracking settings

•

Organizational unit determination



•

Direct shipment process

•

Default values

•

Pick-up and delivery window calculation

Freight unit type determination is based on freight unit building rules applied in the creation of freight units and on specified conditions.



Unit 7 Exercise 15 Examine a Freight Unit

Business Example

As a manufacturer, you require a planning tool that supports your diverse requirements in relation to shipping various products. You need to investigate how SAP TM builds and plans freight units, as well as learn about the necessary tools to support planning. 1. Create a sales order for 50 pieces of product PRODTM-OO, for customer CUSTOO-25, with reference PO number TM200_00. Use the following organizational data: Field

Value

Order Type

ZT00

Sales Org

3000


10

Division

00

2. Take note of the sales order number.

3. Review the order based transportation requirement in SAP TM. What is the OTR-number that corresponds to your sales order? Which document type has been used for your OTR? Write down the document number of your OTR.

4. Navigate into the OTR and review the information. What is the lifecycle status?

5. What is the consumption status?

0



6. What is the source location of product PRODTM-OO?

7. Is the source location visible on the Locations and Dates/Times tab in the Source screen area? Why not?

8. Has a freight unit been created? If yes, note the freight unit number.

9. What freight unit building rule is used to create the freight unit?

10. What freight unit type has been used for the freight unit?

11. What is the requested time window of the freight unit at the destination location (CUSTOO-25)?

12. How many stages have been created in the freight unit?

13. Are there any successor documents to the freight unit?



14. Is any block status defined for the freight unit?

15. What are the planned and actual quantities for product PRODTM-OO in this freight unit?



Unit 7 Solution 15 Examine a Freight Unit

Business Example

As a manufacturer, you require a planning tool that supports your diverse requirements in relation to shipping various products. You need to investigate how SAP TM builds and plans freight units, as well as learn about the necessary tools to support planning. 1. Create a sales order for 50 pieces of product PRODTM-OO, for customer CUSTOO-25, with reference PO number TM200_00. Use the following organizational data: Field

Value

Order Type

ZTOO

Sales Org

3000


10

Division

00

a) In SAP ERP, enter transaction code v a o i . b) Enter the data from the table and choose Enter. c) On the screen, enter the following data: Field

Value

Sold-To Party

CUSTOO-25

PO Number

TM200_00

Material

PRODTM-OO

Quantity

50

d) Save your data. 2. Take note of the sales order number.



3. Review the order based transportation requirement in SAP TM. What is the OTR-number that corresponds to your sales order? Which document type has been used for your OTR? Write down the document number of your OTR.

a) In NWBC, choose ERP Logistics Integration —> Worklist —*■ Overview Transportation Requirements. b) Choose the Order-based Transportaton Requirements (All) query. c) Identify your OTR by searching in the Original Order column for your sales order number. d) You can find the document type in the Document Type column. The document type of your OTR is OTRX. You can find the OTR number in the Document column. The document number varies. 4. Navigate into the OTR and review the information. What is the lifecycle status? The lifecycle status is ‘in planning’,________________________________________________ a) Choose your document number to navigate into your OTR, b) The lifecycle status is displayed on the General Data tab in the Statuses screen area. 5. What is the consumption status? The consumption status is ‘not consumed'._________________________________________ a) The consumption status is displayed on the General Data tab in the Statuses screen area. 6. What is the source location of product PRODTM-OO? The source location is SP3100 (Shipping Point Chicago).______________________________ a) In the Items screen area, select the row for PRODTM-OO. b) Select the Locations and Dates/ Times tab in the Items screen area to view the source location. 7. Is the source location visible on the Locations and Dates/Times tab in the Source screen area? Why not? The source location information is not filled here, because different items of the OTR may have different source locations. Thus, at header level, this information is not unique and therefore not displayed._________________________________________________________



a) Select the Locations and Dates/Times tab of the OTR to view the required information in the Source screen area. 8. Has a freight unit been created? If yes, note the freight unit number. Freight unit number varies.______________________________________________________ a) Select the Document Flow tab. You find a successor business document for your OTR. This is the freight unit. 9. What freight unit building rule is used to create the freight unit? Freight unit building rule FUBR_TM200 is used.______________________________________ a) Navigate into the freight unit by selecting the document number in the Document Flow tab of the order based transportation requirement. b) The freight unit building rule that is used is displayed on the General Data tab in the Additional Data screen area of the freight unit. 10. What freight unit type has been used for the freight unit? Freight unit type FUX2 is used.___________________________________________________ a) You find the freight unit type that has been used on the General Data tab in the Additional Data screen area of the freight unit. 11. What is the requested time window of the freight unit at the destination location (CUST00-25)? The requested start time of the delivery window is one day prior to the requested delivery date from your sales order. The requested end time of the delivery window is one day after the requested delivery date from your sales order.______________________________________ a) You find the information about the requested time window on the General Data tab of the freight unit. 12. How many stages have been created in the freight unit? Only one stage from SP3100 to CUST00-25 has been created in the freight unit, a) To view the stages, choose the Stages tab.



13. Are there any successor documents to the freight unit? There are no successor business documents to the freight unit._________________________ a) Choose the Document Flow tab to view the required information. 14. Is any block status defined for the freight unit? The planning and execution block statuses are both green. There is no block status defined. a) Choose the Statuses tab to view the required information. 15. What are the planned and actual quantities for product PRODTM-OO in this freight unit? The planned quantities are: Quantity: 50 CRT; Gross Weight: 5,000 lb; Gross Volume: 1,765, 740 FT3; Net Weight: 4,750 lb. The actual quantities are empty because execution has not started. a) In the Items screen area, highlight the row for PRODTM-OO. b) Choose the Quantities tab in the Items screen area to view the planned quantities.




•




Unit 7 Lesson 3 Creating Freight Orders for Shipping

LESSON OVERVIEW This lesson examines freight order creation. You learn about manual (interactive) freight order creation, and automatic freight order creation using the Vehicle Scheduling and Routing (VSR) optimizer. Freight orders are a result of planning and can have different properties depending on their freight order type. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Freight Orders In his role as an SAP transportation consultant, John is asked to explain the benefits of freight orders and how they are created using optimization criteria. John must describe the principles of vehicle scheduling and routing (VSR) optimization used in SAP TM as well as explain the differences between freight units, transportation units and freight orders.

0



SAP ERP Sales Order / Purchase Order Order-based Transportation Requirement

Forwarding Quotation Delivery-based Transportation Requirement

L ■e r r

Forwarding Order

1


Capacities Execution / Subcontr.

Transportation Network Agreement


Calculation Sheet



Rate Table

Figure 107: SAP TM Document Flow

Freight orders represent a single shipment or load departing from one of your facilities (outbound scenario) or arriving in one of your facilities (inbound scenario). The freight order can be created manually or automatically, for example, by using the vehicle scheduling and route optimizer. Freight orders are the basis for carrier selection, tendering or freight settlement processes. These topics are covered in separate units. SAP TM Document Flow

You can use the freight order management component in SAP TM to create and edit freight orders and freight bookings. You use freight orders for road and rail transportation and you use freight bookings for sea and air transportation. You can use the business documents in freight order management to enter all the information required for transportation planning and execution, such as source and destination locations, dates and times, product information, and resources used. You can create freight orders directly or in transportation planning. For example, you can assign freight units to the freight orders and have the system calculate the transportation charges. You can then perform carrier selection, assign the freight orders directly to a carrier as a suborder or perform tendering.



Freight Orders in Transportation Planning

FU 1

Freight Order FU 1

Freight Order

FU 2

FU 3

Figure 108: Creating Freight Orders

In a freight order, freight units from different transportation requests (OTR/DTR/FWO) can be consolidated. The planning engine aims to find the lowest cost solution based on the freight units to be planned, the transportation network (as defined in master data) and, for example, the costs defined in the relevant planning profile. If freight orders are created during planning and have the respective settings in the planning profile, the system determines the freight order type according to the Customizing settings. Transportation Units

The transportation unit (TU) is somewhere in between the freight unit and the freight order. Several use cases for TUs are possible as a consolidation option.



Freight Unit

Transportation Unit

Freight Order

Represents demand

+

+

-

Default route to define stages

+

+

-

Provides capacity

-

+

+

Different quantities per stage

-

+

+

Cargo management

-

+

+

Subcontracting

-

-

+

| Feature

| Figure 109: Transportation Unit, Freight Unit, Freight Order - Comparison

Freight Order Types The freight order type determines how a freight order is processed in SAP TM. There are some basic settings allowing for flexible customization options. Freight order settings allow the planner to carry out the following tasks:

Define number range intervals Define subcontracting relevance Define how consignee and shipper are determined Define whether the freight order is to be fixed during saving Define whether the freight order can be deleted or only canceled Define sequence of stops Change controller settings Run checks on creation, save and deletion Freight order settings allow the planner to make the following settings:

Execution tracking Event management Output options Number ranges and strategies for house bills of lading (HB)



Freight Oder Types Fraght Older Type ™>o TM1C0 Instrcto FOT v Defatit Type Default Type for ERP Shpment Integration Base Settngs

Number Range Settngs

Freight Order Can Be Subcontracted Sh^cer/Consignee Determination

Relevant for Subcontracting Determnatxn Based on Predecessor Docu_ -

Time for Drawing

Draw Number When Savng Do . ~


05

~‘Fb< Document When Saving •/ Freight Order Can Be Deleted Sequence Type of Stops

Defined and Unear

~

Change Contrder Settngs Default Change Strategy Change Strategy Determnation Cond. Quantity Toterance Conckton

Additional Strategies

QUAHT_T0L_01

Creabon Strategy Save Strategy Detetnn Strategy

Date Tolerance Condition

Execution Settngs Execution Track. Relev. Check Condtion "Ready for Exec* [ Immedate Processing

Service Level Determination Execution Tracking vtfth External Event Man. *

•

1

Event Management Settngs Apcfcation object Type Last Exp. Event

Default Service Level Service Level Cond.

0DT20_TO POD

Default MTr for Type Condition for Def MTr

--- 1 ________ 1

Figure 110: Freight Order Type


261





Unit 7 Exercise 16 Create a Freight Order

Business Example As a transportation planner, you need to understand the principles of VSR optimization, and how to create a freight order based on outbound or inbound transportation requirements.

Note: Required: This exercise is dependent on the completion of the exercise Examine a Freight Unit.

1. Enter the transportation cockpit with planing profile TM200_PLAN for the order based transportation requirement created in the previous exercise. Create an optimal transportation plan using the optimizer considering all available resources. 2. How many freight orders have been created?

3. What is the maximum utilization of the truck?

4. How long does it take to load and unload the truck at each location? Do you know why?

5. Which freight order type is used? Do you know why?

0



Unit 7 Solution 16 Create a Freight Order

Business Example As a transportation planner, you need to understand the principles of VSR optimization, and how to create a freight order based on outbound or inbound transportation requirements.

Note: Required: This exercise is dependent on the completion of the exercise Examine a Freight Unit.

1. Enter the transportation cockpit with planing profile TM200_PLAN for the order based transportation requirement created in the previous exercise. Create an optimal transportation plan using the optimizer considering all available resources. a) In NWBC, choose ERP Logistics Integration —► Worklist —► Overview Transportation Requirements. b) Select the row with your order-based transportation requirement from the previous exercise. c) Choose Start Transportation Cockpit. d) In the Transportation Cockpit: Profile and Layout Sets choose New. (If the profile and layout screen does not open, choose Change Profile Selection —>Profile Selection Screen e) In the Planning Profile column, enter tm200_plan . f) Save your data and continue. g) Select the freight unit to customer CUST00-25. Choose Optimizer Planning —>Selected Entries with All Resources. h) When the optimizer is complete, choose Accept. i) Choose Save. 2. How many freight orders have been created? One freight order has been created.



3. What is the maximum utilization of the truck? 11%. Highlight the freight order in the Freight Orders/Freight Bookings view. In the detail view underneath (Overview tab), you can see that the maximum utilization of the truck is 11%. (If you are not sure which FO corresponds to your freight unit, in the Freight Units Stages screen area you can scroll to the Execution Document column to identify your FO number).________ 4. How long does it take to load and unload the truck at each location? Do you know why? Highlight the freight order in the Freight Orders/Freight Bookings view. In the detail view (Overview tab), you can see that each loading and unloading activity takes 10 minutes. Hint: Scroll to the right to compare the start and end times of the activities. In planning profile TM200_PLAN, it has been defined that the loading and unloading times are independent of freight unit and means of transport, and that they take ten minutes. To view this, choose Application Administration —>Planning —>Planning Profiles —>Display Planning Profile._______ 5. Which freight order type is used? Do you know why? Choose the freight order ID to open your freight order. In the General Data tab, you can see the document type is TM00. This is because the "Default type for road (FO)" has been defined as TM00 in your planning profile._________________________________________________







Unit 7

Learning Assessment

1. Planning is carried out on the freight unit - which must first be created. Place a tick beside each of the options below which can trigger the creation of a freight unit. Choose the correct answers. | A Freight Order B Purchase Order | C Forwarding Order D Sales Order 2. Which of the following planning constraints can be considered in SAP Transportation Management? Choose the correct answers. | A Vehicle resource capacities B Compartment capacities | C Depot locations D Driver qualifications 3. In relation to freight unit building in SAP TM and based on what you have learned in this lesson, place a tick beside each of the statements below which are true. Choose the correct answers. | A Freight units can be created manually or automatically. B FUBRs can be used to specify rules in relation to how freight units are consoildated or split. | C A freight unit can be described as a collection of goods that are transported together across the entire transportation chain. D There is just a single predecessor document that can lead to the creation of a freight unit: the sales order.

0



4. How many freight units are created for an order-based transportation requirement with three items if a freight unit building rule that does not allow item splitting is selected? Choose the correct answer. | A Always exactly 1 B Always exactly 3 C 1 or more



Unit 7


1. Planning is carried out on the freight unit - which must first be created. Place a tick beside each of the options below which can trigger the creation of a freight unit. Choose the correct answers. | A Freight Order [x ] B Purchase Order [x ] C Forwarding Order

|~x]

D Sales Order

Correct. All of the options except the freight order can trigger the creation of a freight unit. The freight order is a successor document to the freight unit. 2. Which of the following planning constraints can be considered in SAP Transportation Management? Choose the correct answers. |~X~| A Vehicle resource capacities [x ] B Compartment capacities [x ] C Depot locations D Driver qualifications That is correct. Capacities for vehicles resources and compartments as well as depot locations are planning constraints considered in SAP Transportation Management.

0



3. In relation to freight unit building in SAP TM and based on what you have learned in this lesson, place a tick beside each of the statements below which are true. Choose the correct answers.

|~xj

A Freight units can be created manually or automatically.

|~xj

B FUBRs can be used to specify rules in relation to how freight units are consoildated or split.

\x \ C A freight unit can be described as a collection of goods that are transported together across the entire transportation chain. D There is just a single predecessor document that can lead to the creation of a freight unit: the sales order. Correct. Only one of the statements is not true. Freight units can be generated not only from sales orders but out of any FWO, DTR or OTR. 4. How many freight units are created for an order-based transportation requirement with three items if a freight unit building rule that does not allow item splitting is selected? Choose the correct answer. | A Always exactly 1 B Always exactly 3

|~xj C 1or more That is correct. At least one freight unit is created. Depending on the quantities and split value, more than one freight unit may be created.



UNIT 8

SAP Transportation Management Transportation Network

Lesson 1 Integrating SAP ERP Master Data with SAP TM Exercise 17: Generate and Activate an Integration Model

273 281

Lesson 2 Evaluating Location Masters Exercise 18: Examine Location Masters

290 299

Lesson 3 Creating Transportation Zones Exercise 19: Define Transportation Zones

305 313

Lesson 4 Defining Methods of Transportation Exercise 20: Create a Means of Transport

319 329

Lesson 5 Defining Transportation Lanes Exercise 21: Create Transportation Lanes Exercise 22: Calculate Durations and Distances using Transportation Lanes

333 335 347

Lesson 6 Creating Carrier Profiles Exercise 23: Create Carrier Profiles

350 357

Lesson 7 Examining Resources in SAP TM Exercise 24: Define Capacity Limits with Vehicle Resources

0

360 365



UNIT OBJECTIVES

•

Examine the transfer of master data from the Core Interface to SAP TM

•

Integrate customer master data

•

Examine locations in SAP TM

•

Examine customers in SAP TM

•

Examine vendors in SAP TM

•

Examine business partners in SAP TM

•

Evaluate shipping points in SAP TM

•

Evaluate geocoding locations in SAP TM

•

Create transportation zones

•

Create transportation zone hierarchies

•

Define transportation modes

•

Define means of transport

•

Create a transportation lane

•

Examine transportation lane application during transportation planning

•

Examine the purpose of carrier profiles

•

Examine product and transportation groups

•

Examine equipment groups and equipment types

•

Create carrier profiles

•

Apply calendar resources

•

Apply handling resources

•

Apply vehicle resources



Unit 8 Lesson 1 Integrating SAP ERP Master Data with SAP TM

LESSON OVERVIEW This lesson examines the integration process between SAP ERP and SAP TM. You learn about the SAP ERP master data that is relevant for integration with SAP TM. and examine how the Core Interface (CIF) supports the process of integration.

At the end of the lesson you can generate and activate an integration model. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


S A PTM Integration Scenarios

Master Data is integrated from SAP ERP to SAP TM via the CIF (core interface). Transactional Data is integrated between SAP ERP and SAP TM either directly via web services or indirectly using SAP PI (process integration).

0



CIF provides the following central functions: •

Determine source and target systems within complex system environments

•

Initial transfer of master data from the ERP system

•

Tools for administering the data transfer

Master data changes can be transferred via the following: •

Transfer of data changes using Application Linking and Embedding (ALE) change pointers

•

Online transfer using business transfer events (BTEs)

The Integration Process When implementing TM, consider if your business is integrating to SAP ERP, or implementing TM as a stand-alone product. Depending on which scenario applies to your business, the integration options differ. In the case of a shipper using a back end SAP ERP system, the business requires automated integration when implementing TM. When using SAP ERP, integration is delivered in two formats. The first is used to support the integration of master data. This is referred to as the Core Interface (CIF). This uses a queued remote call function (qRFC) process to create and synchronize the data as frequently as required. The second integration format is for transactional data and is discussed in a later unit.



Step 1: Select the Relevant ERP data models using transaction CFM1

Figure 113: CIF Master Data Models

Integration Between SAP ERP and SAP TM

The integration between SAP ERP and TM is a two-step process. The first step is to determine what data from your ERP system needs to be replicated in TM. This is activated by a scheduled batch job using a program variant. For example, as you create new customer master records you may need to transfer these to TM on a daily basis; these can be considered in the nightly TM planning run. Once the data is selected, the transfer process is prompted from ERP. Using RFC calls, the data is created in TM. Similar to the selection process, this is prompted by a scheduled job using program variants. This two-step process is managed by a business analyst or a member of the IT group.

Integration Model Generation The CIF uses an object called an integration model to manage the data transfer and synchronization process between SAP ERP and the SAP New Dimension products.



TM is used to support only the transportation aspect of logistics; not all items in the integration model will integrate. Generate integration model. Name ^

^

Determine name and SAP TM target system. Select master data.

Target system Application

Plant Material master

Activate integration model. Integration model is active.

4

®

Start

Master data will be transferred.

Figure 115: Generate Integration Model/Activate Integration Model

The Integration Model The transfer of master data and transaction data is controlled in the CIF by an integration model. You create, generate, and activate this integration model in the ERP system. Integration models do not exist in TM. In the integration model, select the dataset (master or transaction data) you want to transfer. Specify the following in the integration model: •

The SAP TM target system for the data transfer

•

The data objects you want to transfer

Define the integration model that controls the transfer of master and transaction data in the ERP system. You can find the menu option Core Interface Advanced Planner and Optimizer (the CIF menu) under Logistics —*• Central Functions —> Supply Chain Planning Interface. The integration model distinguishes between master data and transaction data. When integrating with TM, you transfer master data via the integration models. We recommend that you select different types of data in separate integration models and then transfer them separately, for example, shipping points, customers, or vendors.

Note: Your ERP system may use integration models to communicate with an APO instance and an instance of EWM. All use integration models and transfer similar data, but the target systems are different. You can deactivate and then delete the integration models that you no longer need.



Generate the Integration Model

A unique definition of the integration model is given by its name and application. The master data transferred from the ERP system to the SAP TM system in the initial transfer is defined in an integration model. The ERP system generates this integration model (transaction CFM1). Elements in an Integration Model In the ERP system, a unique integration model consists of five elements:

1. Model Name 2. Logical System 3. APO Application 4. Date 5. Time We recommend that you have one integration model per object. To integrate a master data object, identify the model name, logical system, and APO application. Select the object that you want to transfer to TM. Assuming you do not want to transfer every material in the ERP database, restrict the metadata you want to transfer. Transfer only the active materials.

Note: Although the field is labeled APO application, the field is still applicable to TM. You may want to use the model name field to represent the business division and the application (TM/APO/EWM) that the integration model is going to be used to support. The APO application can be used to identify objects in the integration model, such as materials, customers, or vendors.



It is useful to create several integration models with the same name, but as different applications. Ensure that your integration model data pools are not too large. This enables you to handle errors more easily. Integration Model Generation The target or logical system that you specify in the integration model determines the new dimension (TM) system to which the master data is transferred. The target system is a logical (TM) system that must have an RFC connection. This is defined by the basis team. Specify the model, logical system, APO application, the object, and metadata. Save this as a program variant. This schedules the generating integration models program on a nightly basis. It calls out the program variants you created. Once the program variant is created, generate an integration model by executing the model. The ERP system then reviews your database and identifies what items are transferred and created in TM. You may do this interactively the first time you generate an integration model. Subsequently, the program is scheduled as a background job. Integration Model Activation

Integration model Name Target system Application "Activate" PUMPS

PUMPSI APQCLNT800 MATERIALS

£?

I

r

Material master B Material master A ________ _________ r

Active/lnactive

APOCLNT800

MATERIALS

10:00 AM

Figure 117: Activating an Integration Model for Initial Data Transfer

To transfer data to TM, you must activate the integration model generated. You activate an integration model with transaction

c f m 2.

Choose ERP —► Logistics —> Central Functions —*■ Supply Chain Planning Interface —> Core Interface Advanced Planner and Optimizer —> Integration Model —*• Activate Choose the Start function to trigger the data transfer to TM. The master data, or the equivalent of the ERP master data then exists in the TM system. The initial data transfer runs in a particular order: the objects are selected successively, transferred to TM and processed there in this sequence. For improved system performance, it is also possible to execute a parallel initial data transfer. Several integration models can be



activated at the same time. During parallel processing, you can set whether to run the selection in RPC, the processing in TM, or both at the same time. Parallel processing takes place within an object type. The different object types are still transferred in sequence. Integration Model Regeneration

ER N ew

Name Target system Appl.

PUMPS APOCLNT800

E x is tin g in teg ratio n m o d el

MATERIALS

K 4 Material master

X

"Activate"

MRP type

xo

PUMPS

APOCLNT800

MATERIALS

11:00 AM

PUMPS

APOCLNT800

MATERIALS

10:00 AM

s? Active/lnactive I ■

1

D iffe re n c e is tra n s fe rre d

Figure 118: Repeat Generation and Activation

You can regenerate and activate an existing active integration model with the same or changed selection criteria, under the same name at any time. The existing model is regenerated (and the new master data is selected). There are then two models with the same name. The only difference between them is the date and time. This option is suitable for transferring new or changed TM-relevant master data. If you activate a regenerated model, only the difference in the objects not contained in the runtime version is transferred, including any change pointers that may exist. The system compares the existing, active integration models with the new model for each object and determines which new master data needs to be created in TM (delta transfer). Data Transfer After the data is transferred, the old integration model is deactivated and the new integration model is activated. For example, you activate model 1 with the material masters A and B, and activate model 2 in the second step with the material masters B and C. Thus, when you activate model 2, only material C will be transferred. When you deactivate model 1, the integration for materials B and C remains.



Periodic Regeneration of an Existing Integration Model

Report RIMODGEN Name

G e n e ra te in teg ra tio n m o d el

w

PUMPS

Target system APOCLNT800 Application

MATERIALS

Report RIMODAC2

Variant PUMP MAT

JOB 1 Execute ____+ ____ O Save

cD

O

Step 1

A ctiv a te in teg ra tio n m o d el

Name

PUMPS

Target system

APOCLNT800

Application

MATERIALS

JOB_2 Âctive/lnactive

+

Step 1

Start

Figure 119: Periodic Regeneration of an Existing Model

To ensure that the system transfers all the TM-relevant master data, it is possible to regenerate periodically and activate the existing integration models. Because any existing change pointers are also processed in this procedure, a separate transfer of data changes is no longer necessary. Integration models can be regenerated and activated in regular intervals. You can do this automatically through the definition of jobs. Report RIMODGEN generates an integration model. You schedule this report by entering a variant that you define as a job. Report RIMODAC2 activates an integration model. You need a variant for this report to enable you to schedule it in a job. You can retransfer all the data objects with report RIMODINI. You need a variant for this report to schedule it in a job. The entire data record is transferred. If, for example, you change just one field in a material master, the entire material master is retransferred with the data change transfer.



Unit 8 Exercise 17 Generate and Activate an Integration Model

Business Example

ABC Corporation wants to implement SAP TM to support truck-load (TL) and less-than-truckload (LTL) planning scenarios. The SAP consultant needs to create appropriate CIF models to transfer master data from SAP ERP to SAP TM. Set Up Data Transfer from SAP ERP to SAP TM Your business wants to integrate your customers, carriers, and materials from SAP ERP to SAP TM. Create the necessary integration models to support this activity and ensure that you can generate new integration models if necessary.

1. In SAP ERP, create a CIF model to transfer customers from SAP ERP to SAP TM. Save your data, and name and describe the variant. Use the following data: Field

Value

Model

TM_GR##

Logical System

ZMTCLNT800

APO Application

Customers

Variant

GR## Cust

Description



Customer

Customer from

CUST##-01

Customer to

CUST##-30

Create Loc./BP field

2

2. Generate an integration model. 3. In SAP ERP, create a CIF model to transfer carrier master data. Save your data, and name and describe the variant. Use the following data:

0

Field

Value

Model

TM_GR##

Logical System

ZMTCLNT800

APO Application

Carriers


Vendor



Field

Value

Vendors from

CAR##-01

Vendors to

CAR##-04


1

Variant

GR## Carrier

Description


4. Generate an integration model. 5. In SAP ERP, create a CIF model to transfer material master data. Save your data, and name and describe the variant. Use the following data: Field

Value

Model

TM_GR##

Logical System

ZMTCLNT800

APO Application

Products

Variant

GR## Prod

Description

GR## Product Integration

Material Dependent Objects screen area

Material

Materials from

PRDTM-##

6. Generate an integration model. Transfer Data from SAP ERP to SAP TM You have now selected the master data to transfer and integrate with SAP TM. You now need to initiate the transfer process. Trigger the activation of your new integration models.


Value

Model Name

TM_GR##

Logical System

ZMTCLNT800.


20

2. In SAP ERP, transfer customer master data to TM. Drill down on your logical system ZMTCLNT800 and your model TM_GR## to transfer the customer data. 3. In SAP ERP, transfer carrier master data to SAP TM. Drill down on your logical system ZMTCLNT800 and your model TM_GR## to transfer the carrier data.



4. In SAP ERP, transfer material master data to SAP TM. Drill down on your logical system ZMTCLNT800 and your model TM_GR##, to transfer the material data.



Unit 8 Solution 17 Generate and Activate an Integration Model

Business Example

ABC Corporation wants to implement SAP TM to support truck-load (TL) and less-than-truckload (LTL) planning scenarios. The SAP consultant needs to create appropriate CIF models to transfer master data from SAP ERP to SAP TM. Set Up Data Transfer from SAP ERP to SAP TM Your business wants to integrate your customers, carriers, and materials from SAP ERP to SAP TM. Create the necessary integration models to support this activity and ensure that you can generate new integration models if necessary.

1. In SAP ERP, create a CIF model to transfer customers from SAP ERP to SAP TM. Save your data, and name and describe the variant. Use the following data: Field

Value

Model

TM_GR##

Logical System

ZMTCLNT800

APO Application

Customers

Variant

GR## Cust

Description



Customer

Customer from

CUST##-01

Customer to

CUST##-30


2

a) In SAP ERP, on the SAP Easy Access screen, choose Logistics —> Central Functions —> Supply Chain Planning Interface —► Core Interface Advanced Planner and Optimizer —► Integration Model —> Create. b) Enter the data from the table for the model, logical system and APO application. c) Select the Customers checkbox and choose

Special Restrictions.

d) Create your customers CUST##-01 to CUST##-30. e) Enter the Create Loc./BP field value from the table.



f) Save your data. g) Name and describe the variant. h) Save your data. 2. Generate an integration model. a) Choose


b) Choose

Generate IM to generate the integration model.

c) Choose

Continue on the information message.

d) Exit the screen. 3. In SAP ERP, create a CIF model to transfer carrier master data. Save your data, and name and describe the variant. Use the following data:________________________________________ Field

Value

Model

APO Application

TM_GR## ZMTCLNT800 Carriers


Vendor

Vendors from

CAR##-01 CAR##-04 1 GR## Carrier Group ## Carriers/FWD Agents

Logical System

Vendors to Create Loc./BP field Variant Description

a) In SAP ERP, on the SAP Easy Access screen, choose Logistics —> Central Functions —> Supply Chain Planning Interface —> Core Interface Advanced Planner and Optimizer —► Integration Model —> Create. b) Enter the data from the table. c) Manually enter the APO Application:

Carriers

d) Select the Vendor checkbox and choose £> e) Create your vendors CAR##-01 to CAR##-04. f) Enter 1 in the Create Loc./BP field. g) Choose Go to —► Variants —*• Save as Variants h) Name and describe the variant. i) Save your data.



4. Generate an integration model. a) Choose


b) Choose

Generate IM to generate the integration model.

c) Choose ^

Continue on the information message.

d) Exit the screen. 5. In SAP ERP, create a CIF model to transfer material master data. Save your data, and name and describe the variant. Use the following data: Field

Value

Model

TM_GR## ZMTCLNT800 Products GR## Prod GR## Product Integration Material PRDTM-##

Logical System APO Application Variant Description Material Dependent Objects screen area Materials from

a) On the SAP Easy Access screen, choose Logistics —*■ Central Functions —> Supply Chain Planning Interface —>Core Interface Advanced Planner and Optimizer —► Integration Model —> Create. b) Enter the data from the table. c) Select the Materials checkbox. d) In the Material Independent Objects screen area, select the Materials checkbox and choose £>. Enter the materials data from the table. e) Choose Go to —> Variant —> Save as Variant. f) Name and describe the variant. g) Save your data. 6. Generate an integration model. a) Choose Execute to process the selection. b) Choose Generate IM to generate an integration message. c) Choose Continue on the information message. d) Exit this screen.



T ransfer Data from SAP ERP to SAP TM

You have now selected the master data to transfer and integrate with SAP TM. You now need to initiate the transfer process. Trigger the activation of your new integration models. 1. In SAP ERP, configure the parameters for transfer of master data to SAP TM. Select the Parallelize Selection in ERP System checkbox. Use the following data: Field

Value

Model Name

TM_GR## ZMTCLNT800. 20

Logical System Absolute Max No. of Processes

a) In SAP ERP, on the SAP Easy Access screen, choose Logistics —> Central Functions —> Supply Chain Planning Interface —> Core Interface Advanced Planning and Optimizer —► Integration Model —*■ Activate . b) Enter the data from the table. c) Choose (Ê xecute. 2. In SAP ERP, transfer customer master data to TM. Drill down on your logical system ZMTCLNT800 and your model TM_GR## to transfer the customer data. a) Select Customers to show model details. b) Select the top line and choose c) Select the line again and choose

Active/lnactive. Start to initiate the transfer.

If you receive a pop-up message telling you that the queue is blocked, choose Ignore. d) Answer NO to branching to application logs and choose ^ message.


e) Stay in the transaction. 3. In SAP ERP, transfer carrier master data to SAP TM. Drill down on your logical system ZMTCLNT800 and your model TM_GR## to transfer the carrier data. a) Select Carrier to show model details. b) Select the top line and choose c) Select the line again and choose

Active/lnactive. Start to initiate the transfer.

If you receive a pop-up message telling you that the queue is blocked, choose Ignore. d) Answer NO to branching to application logs and choose ^ message.


4. In SAP ERP, transfer material master data to SAP TM. Drill down on your logical system ZMTCLNT800 and your model TM_GR##, to transfer the material data. a) Choose Products to show model details.



b) Select the top line and choose Active/lnactive. c) Select the line again and choose Start to initiate the transfer. If you receive a pop-up message telling you that the queue is blocked, choose Ignore. d) Answer No to branching to application logs and choose Continue on the information message.



LESSON SU M M AR Y

You should now be able to: •


•




Unit 8 Lesson 2 Evaluating Location Masters

LESSON OVERVIEW

In this lesson, we examine SAP ERP and SAP TM location types. We consider the roles of the customer, vendor, and business partner in transportation planning. At the end of this lesson, you will be able to determine the shipping point and geocode locations used in SAP TM. LESSON OBJECTIVES



•


•


•


•


•


Location Types in SAP TM A location is a logical or physical place in which resources are managed on a quantity basis. This business object is used as the basis for the transportation processes in which you name a source location, a destination location, and any transshipment locations necessary to complete it. Purpose of Locations

The following are a number of the purposes of locations: •

Freight is moved between locations in SAP TM

•

A freight unit always has both a source location and a destination location

•

A freight unit may travel through a number of locations



Define a Location Type

Location type Description

1001 1002 1003 1010 1011 1030 1100 1110 1120 1130 1140 1150 1160 1170 1180

Production plant Distribution center Shipping point Customer Vendor Terminal Port Airport Railway station Container Freight Station Hub Gateway Container Yard Warehouse Carrier Warehouse

Figure 120: Location Types

To define a location in TM, specify its name and type. ERP and TM Location Types

ERP

SAP TM

Figure 121: ERP and TM Location Types

Different customizing entries and master data elements from ERP are displayed in SAP TM as locations with different location types. ERP plants, customers, vendors, and shipping points are integrated with SAP TM and become the following types of location: Plants-1001 (production



plant) or 1002 (distribution center), Customers-1010 (customer), Vendors-1011 (vendor), and Shipping Points-1003 (shipping point). The location type is automatically determined based on the object being transferred from ERP when location data is created via the CIF. Customers in SAP TM SAP ERP defines the customer as a business partner with whom a business relationship involving the issue of goods or services exists. SAP TM considers how these customers relate to planning. The customer is relevant to planning during transportation planning in TM. Sales orders are generated in SAP ERP and transferred to SAP TM as requirements for planning in the context of shipping.

Data transfer from the customer (ERP) M a s te r d a ta : C u s to m e r

Custom er ôoo;

Name

Becker

Street cfccalvinstr. 36 City <0 3 4 6 7 Berlin CountryC^DE Region Q11

CgtmtnrfD E

Germany

Language

Berlin Language— f Germa7i~ M aster data: Transportation Zone

Tr.Zone

D10000

Berlin region

Figure 122: Customer Location Type

Transferring Customers from ERP SAP TM plans shipments to one or more customers. TM works with the SAP ERP delivery processing. This functionality requires information about customers and their geographic locations to calculate distances and durations during an optimization planning run. Customers are transferred from ERP as locations with type 1010. TM customers represent a destination location in the case of a sales order, or a source location in the case of a returns order. Because these are objects created by the CIF, the system also copies basic settings for the customer such as description, address data, and time zone. TM locations contain additional planning parameters that have no equivalents in SAP ERP. You must maintain these parameters in TM. The system cannot transfer them from ERP without further activities.



Vendors in SAP TM SAP ERP defines the vendor as a business partner from whom materials or services are procured. The vendor master is master data, whether it is created for a one time purchase or as a partner with whom your organization engages continuously.

Vendor M aster Records

When vendor master records are transferred to SAP TM they prompt the creation of location master records of location type 1011. If you are modeling an inbound scenario, transfer the materials supplier as a location. This is the shipping location. When transferring vendors from ERP, create both the location master and the business partner. Both customer and vendor master data exist in the SAP SCM location master data. If customer and vendor masters in the SAP ERP system have the same number ranges, any vendor master having the same account number as a customer master must be renamed. A user-exit exists for this purpose; during the transfer of SAP ERP master data any vendor account number that is a duplicate of a customer master can be renamed automatically. Carrier locations are normally not needed in TM. Carriers that provide services that we order and pay for are created as business partners. Business Partners Different business partners with various relationships to one another exist in the marketplace. Examples of business partners are: •

Customer

•

Vendor



•

Employee

•

Contact person

•

Driver

Examples of business relationships are: •

Vendor-customer: The vendor acts as the forwarding agent for the customer.

•

Contact person - customer: The contact person is employed at the customer's company.

•

Contact person - customer: The contact person is the customer's consultant but does not work in the same company.

•

Customer-customer: Sold-to party and ship-to party are not the same.

•

Employee - contact person: Contact person is looked after individually.

•

Employee - customer: Customer manager

Partner Types The business partners that exist in the marketplace are represented in the SAP system by a partner type. Partner types AP. KU, LI, and PE are defined in partner processing for the sales and distribution application module. These are defined as follows: Acronym

Definition

AP

Contact Person

KU

Customer

LI

Vendor

PE

Personnel

P artner Functions

Figure 124: Slide 1



Partner types allow us to distinguish between different business partners. Partner functions represent the roles they play within the business transaction. For example, different customer partners can assume certain roles in a business transaction. The customer who places the order is not necessarily the same customer who receives the goods or is responsible for paying the invoice Assigning Partner Functions Assigning partner functions in the SAP system determines the functions of particular partners in the sales process. One partner may have several functions. For example, when all the partner functions within the customer partner type are assigned to one business partner, the same customer is the sold-to party, ship-to party, payer and bill-to party. You can enter contact persons for a customer directly in the customer master so that they are automatically assigned to that customer. The contact person can also be assigned to another customer, in, for example, a consultant role. The forwarding agent is an example of a vendor. Employees in your company are managed in the employee master records. They can assume partner functions of partner type Personnel, such as the partner function ER: Employee Responsible. Integrating Business Partners

C u sto m e r

CIF

C>

a

Customer - 1010

SP Sold-to party SH Ship-to party J

BP Bill-to party

CIF

business [ par tn e r Rol

PY Payer

kv

if

VE V endor Vendor - 1011 S u p p lie r

CIF

£ ©

Figure 125: Business Partner Integration

In business transaction documents such as a forwarding order, the BP master data object appears as a participating party in transportation processes. The party assumes roles, such as consignee, shipper, or ordering party. The CIF models involved in customers and vendors require more than plant and material data. This is to ensure that when the customers and vendors are transferred, the business partner and locations are created. When the CIF model is constructed, input a setting for customers and vendors.



Business Partners and Locations

In the Create Loc./BP there are three settings: 1. Blank-Only create a location 2. 1-Only create a business partner 3. 2- Create business partner and location 2- Create business partner and location is relevant for SAP TM 8.0. Shipping point location type 1003 does not have this setting, but must have a defined business partner. The business partner for the shipping point is created manually in SAP TM and assigned to the shipping point location. During the transfer of a location, it is created with the corresponding type and if selected in the CIF, the business partner is created automatically in SAP TM and assigned to the location. Shipping Points in TM In the SAP ERP system, each inventory-relevant location can be assigned one or more shipping points. A shipping point is an independent organizational unit at a fixed location that processes and monitors inbound and outbound deliveries.

'

m

Plant (1001)

Truck Warehouse

Rail Loading Station

Shippinq Point (1003)


Figure 126: Shipping Point Integration

In ERP, the shipping point can have the following information assigned to it: •

Address



•

Transportation Zone

•

Factory Calendar

•

Working Times

•

Loading time

•

Pick/Pack Time

Shipping Point Integration As a result of CIF integration, a shipping point in SAP ERP creates a location master with a location type 1003 (shipping point). The location will have the address information from SAP ERP because of integration. No other data assigned to the shipping point in ERP transfers to TM because the parameters are maintained differently to support more robust planning functionality. If the shipping point has the same name as the plant, a Business Add-In (BAdl) is applied to SAP ERP before the shipping point can be transferred. The BAdl adds an extension to the shipping point name so that it is different from the plant. Geocoding Locations Locations are critical elements of your transportation network, because they identify source and destination points. Based on where these two points are located, SAP TM can use distance and duration to calculate the best means of transporting a product. As a result of integration with SAP ERP, most locations that are transferred via the CIF have an address. Unfortunately, this address information is not useful for planners or TM. We must translate how that appears on a map. To see geographic information related to location master data, from the SAP TM main menu choose Master Data —> Transportation Network —> Define Location Geographical Information Geographical information plays an important role in TM. Almost all business processes relate to it. High quality geodata improves these processes. The SAP TM Transportation Network is the foundation of a transportation planning process. Its basic elements are locations. These represent spots where business takes place, actions occur, and activities are executed. Locations can be connected via transportation lanes which express the opportunity to transport goods.



Locations Street Address Street/House number

W est Chester Pike

Postal Code/City

19073

3999

Newtown Square

US

Country

|

PA

Region

Geographical Data

Longitude Latitude

Sign

Degrees

+

39

11

18

-

75

46

15

Precision

Minutes

Seconds

900

Figure 127: Geocoding for Locations

A location is a specific point on the earth's surface that is defined by the geographical coordinates of longitude, latitude, and altitude. These coordinates are determined from the address data of a location. An address can contain a country, region, postal code, city, district, street, and house number, as well as additional fields. Determining geographical coordinates from address data is called geo-coding. A geographical information system can be used to get precise geographical coordinates. Geo-coordinates In SAP TM, the location master data object describes the geographical setup of the transportation network underlying business processes. Location can store an address and the geographical coordinates that define its position. The accuracy of the geo-coordinates depends on the address data provided and which service is used to determine them. Standard SAP SCM applications automatically determine a geo-coordinate at region level when creating or changing the location address data. This is sufficient for processes not working with static information or depending on distances, times, or map display. Because geo-coordinates are the basis for distance and duration determination and map display, they must be high quality in case those functions are required. Geo-coordinates are displayed in degrees, minutes, and seconds in the Geographical Data area of the Location user interface and can be overwritten manually by the user. The precision field indicates the granularity of the geo-coding result. A geocoder determines the geographical coordinates (longitude and latitude) from a given address. Two levels of geocoding are possible in SAP TM: 1. Standard (SAPO) (included in SAP TM software license) 2. Full addresses (depending on capabilities of geocoding software)



Unit 8 Exercise 18 Examine Location Masters

Business Example You want to verify that master data has been successfully transferred from SAP ERP. For this reason you check the location and business partner master data that you have transferred in the previous exercise. You also want to verify that geocoding information has been added to the location master data. Review some of the details of the integration process.

Note: Required: This exercise is dependent on the completion of the exercise Generate and Activate an Integration Model.

1. In NWBC, view location master data for CUST##-16. What is the address?

2. What are the geo-coordinates of this customer location?

3. Are the loading and unloading hours defined for this customer?

4. What business partner is created?

0



5. View location master data for CUST##-17. What is the address?

6. What business partner is created?

7. Review business partner CUST##-16 that was created in SAP TM as a result of CIF integration. 8. What business partner roles are created?

9. What account group is customer CUST##-16 assigned to?

10. Review business partner CAR##-01 that was created in SAP TM as a result of CIF integration. 11. What business partner roles are created?

12. What account group is carrier CAR##-01 assigned to?

13. What payment terms have been defined for carrier CAR##-01?

0



Unit 8 Solution 18 Examine Location Masters

Business Example You want to verify that master data has been successfully transferred from SAP ERP. For this reason you check the location and business partner master data that you have transferred in the previous exercise. You also want to verify that geocoding information has been added to the location master data. Review some of the details of the integration process.


1. In NWBC, view location master data for CUST##-16. What is the address? The address is 800 Independence Avenue, Evansville, IN 47713, USA.__________________ a) Open the Master Data folder. b) Choose Transportation Network —► Locations —> Define Location. c) In the Location field, enter c u s t # # - 16 and choose Display.

d) Select the Address tab. 2. What are the geo-coordinates of this customer location? The geo-coordinates are: Longitude: 86 Deg. 15 Minutes 0 Seconds, Latitude: 40 Deg. 0 Minutes 0 Seconds. (The geocodes may vary based on the GIS currently integrated with the TM system).__________________________________________________________________ a) Select the General Data tab to view the required information.

0



3. Are the loading and unloading hours defined for this customer? By choosing the Resources tab, you can assign resources to your locations to support loading and unloading details. Because this is TM data and this item was transferred from ERP, it may not have been maintained._______________________________________________________ a) Select the Resources tab to view the required information. 4. What business partner is created? Business partner CUST##-16 is created and assigned to your customer location.__________ a) Select the General tab to view the required information. 5. View location master data for CUST##-17. What is the address? The address is 599 Northwestern, Louisville, KY 40212 USA.___________________________ a) Open the Master Data folder. b) Choose Transportation Network —>Location —>Define Location. c) Enter c u s t ##-17 in the Location field, and choose Display. d) Select the Address tab. 6. What business partner is created? Business partner CUST##-17 is created and assigned to your customer location.___________ a) Select the General tab to view the required information. 7. Review business partner CUST##-16 that was created in SAP TM as a result of CIF integration. a) In NWBC, open the Master Data folder. b) Choose General —*■ Define Business Partner. c) Enter business partner c u s t # # -1 6 in the Business Partner field. 8. What business partner roles are created? Four roles are created for this partner: Business Partner (Gen.), Financial Services BP, Ship-to Party, and Sold-to Party.________________________________________________________ a) Open the Display in BP Role dropdown menu to view the partner roles.



9. What account group is customer CUST##-16 assigned to? CUST##-16 is assigned to account group KUNA._____________________________________ a) In the Display in BP role dropdown menu, change the party role to Sold-to-party. b) Select the Customer Data tab to view the required information. 10. Review business partner CAR##-01 that was created in SAP TM as a result of CIF integration. a) In NWBC, open the Master Data folder. b) Choose General —► Define Business Partner. c) Choose 0," Open BP. d) Enter business partner car##-01 . 11. What business partner roles are created? Three roles are created for this partner: Business Partner (Gen.), Carrier, and Financial Services BP.__________________________________________________________________ a) Open the Display in BP Role dropdown menu to view the partner roles. 12. What account group is carrier CAR##-01 assigned to? The account group is 0005 — Forwarding Agent._____________________________________ a) In the Display in BP role dropdown menu, change the party role to Carrier. b) Select the Vendor Data tab to view the required information. 13. What payment terms have been defined for carrier CAR##-01? The payment terms defined are 0001 — Pay immediately w /o deduction._________________ a) In the Display in BP role dropdown menu, change the party role to Carrier. b) Select the Vendor Company Org. Data tab to view the required information.




•


•


•


•


•


•




Unit 8 Lesson 3 Creating Transportation Zones

LESSON OVERVIEW The transportation network can be a huge entity with significant amounts of master data to be maintained. In this lesson, you will examine how the use of transportation zones can reduce the amount of network master data that needs to be maintained. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Transportation Zone Usage

A source location and a destination location are required for transportation planning. In the outbound shipper scenario, the source location is the plant or shipping point and the destination location is the customer. Master data is needed to determine the difference between the customer’s delivery date and the source location’s shipping date. The Purpose of Transportation Zones

Transportation zones are used by SAP TM for two purposes:

0



1. In sales order scheduling, the system can use the duration between the shipping location and the receiving location to determine the material availability date. 2. In the planning run, TM looks for opportunities to combine shipments into optimal loads for vehicle resources for orders going to the same geographical area. Transportation zones are used to group individual locations. For example, ship-to-locations can be grouped depending on your organization’s internal and external transportation network. In the example above, all locations in the US state of Illinois have been grouped in a zone. Transportation zones are typically used as the origin and destination points for transportation lanes. Transportation Zones in Planning

Transportation zones are typically used as the origin and destination points for transportation lanes. Transportation zones reduce the effort needed to model the geographic network in planning. Grouping locations into transportation zones reduces the volume of master data in the TM system. Transportation zones can group locations and other zones and can include one-time locations. Transportation zones can include zones within their locations and sub-zones. For example, all locations that are supplied by the same warehouse (individual locations and transportation zones) are grouped into a transportation zone. If SAP ERP integration through the CIF is used, transportation zones are automatically created from the address of the location. The location is automatically assigned to the transportation zone. Types of Transportation Zones

Transportation zones in SAP TM are mixed zones. This means that the assignment of locations to transportation zones can be static (in the case of a direct assignment) or dynamic (in the case of an assignment done by region or postal code).

0



The Assignment of Locations to Transportation Zones can be: Direct Based on Region Based on Postal Code -3 Assignment based on region/postal code is relevant for one-time locations Mixed Assignment methods are allowed for each transportation zone Figure 130: Assignment of Locations to Transportation Zones

Transportation Zones: Region or Country

M aintain Zone

2 9iow -

r|

Rhd

t____________1 -

a .

SEZJlfclffll

i i Mo... Zone S r u s - a.

a

a

TransportationZoneNa * us- il

(j/

| Open;

fill*

Descrpoon linos

longitude

Mn

87

38

Zone - Location -

A

frfc

Sec

♦

latitude

Mn

41

32

32 O

Zone - Postal Code

Sec

♦

Proasxn Type

3N

R

Zone - Reger

ini ftHBW; ^

M

s

a

r * . : -

Couitrv Key Country Name US USA

t a y i-3 ,

Region

Region Name

H

Oncn

Figure 131: Regional Zones

In a regional zone, locations are specified by a country or region. For example, the state of Illinois can be defined as its own zone. In the figure, the zone US-lllinois is created and only Illinois is assigned to it.



Assignment Based on Region

The figure shows a detailed view of zone assignment based on region in SAP TM. Transportation Zones: Postal Codes

Transportation zones can be defined by the use of postal codes. Companies can use zip/postal code or zip/postal code ranges to define these geographical areas.



Most major U.S. truck-load and less-than-truck-load carriers publish their rate structures and transit time tables based on origin and destination three-digit zip code lanes rather than city or state level lanes. In these documents, carriers use ranges of three-digit zip codes, such as 170-173. To define a postal code zone, you create entries on the tab page labeled Postal Code. Transportation Zones: Direct

In a direct assignment, locations are assigned directly to a zone. For example, a particular customer might be in a zone that has low volumes. By including them in a zone with a larger geography, you might improve the optimization results. Transportation Zones: Mixed You can use any combination of these types of transportation zones when defining a zone. This is a called a mixed zone. Calculating Transportation Zone Coordinates

Longitude 88

Mn 32

Sec + 34 0

Latitude 41

Mn 57

Sec ♦ 37 N

Precision Type C M

Figure 135: Calculating Tzone Coordinates



Transportation zones are not physical locations and therefore do not have an address. Transportation zones can also be assigned geographical coordinates. SAP TM offers two options for calculating these coordinates. After defining the locations, regions or postal codes, the system can calculate the coordinates. This estimates the center point of the zone based on the coordinates of all locations included in the zone. Alternatively, identify the geographical coordinates and manually enter them in TM. Transportation Zone Hierarchies The definition of a transportation zone is different for each user or company. For example, consumer products companies that plan their own transportation may have thousands of customers and ship-tos. The volume of master data is still significant, even with transportation zones.

Continent

Location

Country

5 Digit Zip

Region

3 Digit Zip

State

City

Figure 136: Transportation Zones Hierarchy

Transportation Zone Hierarchy Creation

Transportation zones can be created by integration via CIF or manually in TM. The functionality to maintain transportation zones in TM is more sophisticated than the functionality in SAP ERP. In TM your company can define different levels of transportation zones. These zones may form a natural hierarchy. Unlike SAP ERP, TM uses this natural hierarchy to create a transportation zone hierarchy to improve master data maintenance. The figure. Transportation Zone Hierarchy, shows that the Midwest and Southeast customers do not need to be directly assigned to zone USA. All Midwest and Southeast customers are part of zone USA through inheritance from lower-level zone assignment. Locations can be assigned to zones at any level.



Transportation Zone Hierarchy Organization

Organizing transportation zones into transportation zone hierarchies allows you to transfer the properties of the higher level transportation zone to the locations on lower levels of the hierarchy. Transportation zone hierarchies reduce the amount of master data to be maintained in TM: •

A zone can be assigned to any number of higher-level zones

•

Locations can be assigned to any number of zones

•

A zone cannot be assigned to a location

You cannot assign a transportation zone to itself or to a zone already assigned to the same zone. Transportation Zone Hierarchy Definition

The SAP TM-relevant transportation zone hierarchy can be defined in customizing. Choose the menu path Transportation Management —> Transportation Network —> Define Transportation Zone Hierarchy. Transportation zone hierarchies can include locations and transportation zones.



N o rth A m e ric a

Continent

—>

Central America South America Canada

Country

Mexico

U n ite d S ta te s

Region

North Northeast Northwest

State

South Southeast Southwest Iowa Illin o is

Indiana Hierarchy - Change Objects ^ D lsp la v

a Herarchy -

a*

CtJCopy

eft Model

i ^ W i tfsi.oa

Transportati... RELH ZONE NA c3 • CD CA MX • CD - C3 US C D US MIDWEST t_J US-MOUNTAIN C D US-NORTHEAST C D US-SOUTH C D US-SOUTHEAST C D US-WEST

2 2

City

M id w e s t

Michigan Minnesota North Dakota C h ic a g o

Nebraska Ohio South Dakota Wisconsin

Rockford Quad Cities

!

Zone Description Umladehier archie North America Canada Mexico US Zone Midwestern US S tates Mountain US states Northeast US states Southern US states S outheast US states W estern US states

3 Digit Zip

60600 - 60699

5 Digit Zip -=► |

60601- 1000 ■ 60601 -1500

Location CUST00-16

Figure 138: Transportation Zone Hierarchy (2)

Transportation Zone Hierarchy Maintenance

The assignment of transportation zones to other transportation zones is maintained in SAP TM. Choose Master Data —► Transportation Network —*• Define Transportation Zone Hierarchy.



Unit 8 Exercise 19 Define Transportation Zones

Business Example

As locations are created via the CIF integration and others are created in TM, design transportation zones to support planning for both inbound and outbound scenarios. To minimize master data maintenance, create a master data relationship that allows transportation rules at a high level to cascade down to regional levels by defining transportation zone hierarchies. 1. Create transportation zone US-MIDWEST-##, with a description Grp # # Midwest Zone, which includes the states IL - Illinois, IN - Indiana, and ND- North Dakota. 2. To identify the center of your new region, calculate the longitude and latitude for this new location, US-MIDWEST-##. 3. Create transportation zone US-MOUNTAIN-##, with a description Grp## Mountain Zone, which includes the states AZ-Arizona, CO-Colorado, UT-Utah. 4. To identify the center of your new region, calculate the longitude and latitude for this new location, US-Mountain-##. 5. Create transportation zone US-WEST-##, with a description Grp # # West Zone, which includes the states CA-California, and WA-Washington. 6. To identify the center of your new region, calculate the longitude and latitude for this new location, US-WEST-##. 7. Create transportation zone US-SOUTH-##, with a description Grp # # South Zone, which includes the states LA-Louisiana, and TX-Texas. 8. To identify the center of your new region, calculate the longitude and latitude for this new location, US-South -##. 9. Create transportation zone US-SouthEast-##, with a description Grp # # SouthEast Zone, which includes the states FL-Florida, GA, Georgia, KY-Kentucky, and TN-Tennessee. 10. To identify the center of your new region, calculate the longitude and latitude for this new location, US-SouthEast -##. 11. Create transportation zone US-##, with a description Grp # # US Zone, to represent a zone for the United States. 12. To ship products domestically, there are certain resources at your company's disposal, regardless of origin and destination. To make the master data maintenance easier, create a zone hierarchy called US-##, with a description of GRP # # US Zone. In this hierarchy, attach the following zones that you created previously: US-MIDWEST-##, US-WEST-##, USSOUTH-##, US-SOUTHEAST-##, and US-WEST-##. When defining a means of transport, this allows these regions to inherit the master data maintained at a country level.

0



Unit 8 Solution 19 Define Transportation Zones

Business Example

As locations are created via the CIF integration and others are created in TM, design transportation zones to support planning for both inbound and outbound scenarios. To minimize master data maintenance, create a master data relationship that allows transportation rules at a high level to cascade down to regional levels by defining transportation zone hierarchies. 1. Create transportation zone US-MIDWEST-##, with a description Grp # # Midwest Zone, which includes the states IL - Illinois, IN - Indiana, and ND- North Dakota. a) In NWBC choose Master Data —*• Transportation Network —► Transportation Zones —>Define Transportation Zone. b) Choose Create. c) Enter the zone us-MiDWEST-##, with a description Grp ## Midwest Zone. d) Select Continue. e) Select the Zone-Region tab and choose Create. f) In the Country field, enter u s . g) In the Region field, enter i l and choose Enter to accept. h) Continue through any warnings. i) In the Zone- Region tab, choose Create, and enter the remaining regions/states (IN, ND). j) Select Save when all regions and states are added. 2. To identify the center of your new region, calculate the longitude and latitude for this new location, US-MIDWEST-##. a) Select the new zone US-Midwest-##, and choose Calculate Coordinates. b) Choose Save. 3. Create transportation zone US-MOUNTAIN-##, with a description Grp## Mountain Zone, which includes the states AZ-Arizona, CO-Colorado, UT-Utah. a) Choose Create. b) Enter US-MOUNTAIN-##, with a description Grp## Mountain Zone. c) Choose Continue. d) Select the Zone-Region tab and choose Create.



e) In the Country field, enter us and in the Region field enter a z . f) Continue through any warnings. g) Choose Create, and enter the remaining regions and states. h) Choose Save when all regions and states are added. 4. To identify the center of your new region, calculate the longitude and latitude for this new location, US-Mountain-##. a) Select the new zone US-Mountain-##, and choose Calculate Coordinates. b) Choose Save. 5. Create transportation zone US-WEST-##, with a description Grp # # West Zone, which includes the states CA-California, and WA-Washington. a) Choose Create. b) Enter US-west -##, with a description Grp ## West Zone . c) Choose Continue. d) Select the Zone-Region tab and choose Create. e) In the Country field, enter us and in the Region field enter ca. f) Continue through any warnings. g) Choose Create, and enter the remaining regions and states (WA). h) Choose Save when all regions and states are added. 6. To identify the center of your new region, calculate the longitude and latitude for this new location, US-WEST-##. a) Select the new zone US-WEST-##, and choose Calculate Coordinates. b) Choose Save. 7. Create transportation zone US-SOUTH-##, with a description Grp # # South Zone, which includes the states LA-Louisiana, and TX-Texas. a) Choose Create. b) Enter US-South-##, with a description Grp ## South Zone. c) Choose Continue. d) Select the Zone-Region tab and choose Create. e) In the Country field, enter us and in the Region field enter la . f) Continue through any warnings g) Choose Create, and enter the remaining regions and states (TX). h) Choose Save when all regions and states are added.



8. To identify the center of your new region, calculate the longitude and latitude for this new location, US-South -##. a) Select the new zone US-South-##, and choose Calculate Coordinates. b) Choose Save. 9. Create transportation zone US-SouthEast-##, with a description Grp # # SouthEast Zone, which includes the states FL-Florida, GA, Georgia, KY-Kentucky, and TN-Tennessee. a) Choose Create. b) Enter US-SOUTHEAST-##, with a description

Grp ## SouthEast Zone

c) Choose Continue. d) Select the Zone-Region tab and choose Create. e) In the Country field, enter us and in the Region field enter f l . f) Continue through any warnings. g) Choose Create, and enter the remaining regions and states (GA, KY, TN). h) Choose Save when all regions and states are added. 10. To identify the center of your new region, calculate the longitude and latitude for this new location, US-SouthEast -##. a) Select the new zone US-SouthEast-##, and choose Calculate Coordinates. b) Choose Save. 11. Create transportation zone US-##, with a description Grp # # US Zone, to represent a zone for the United States. a) Choose Create. b) Enter us-##, with a description

Grp ##

us Zone.

c) Choose Continue. d) Choose Save. 12. To ship products domestically, there are certain resources at your company’s disposal, regardless of origin and destination. To make the master data maintenance easier, create a zone hierarchy called US-##, with a description of GRP # # US Zone. In this hierarchy, attach the following zones that you created previously: US-MIDWEST-##, US-WEST-##, USSOUTH-##, US-SOUTHEAST-##, and US-WEST-##. When defining a means of transport, this allows these regions to inherit the master data maintained at a country level. a) In NWBC, choose Master Data —*• Transportation Network —► Transportation Zones —>Define Transportation Zone Hierarchy. b) In the Hierarchy Name field, enter relh _ zone and choose Change. c) In the hierarchy displayed on the lower half of the screen, choose the RELH_ZONE node to display the child nodes in the upper half of the screen.



d) In the Transportation Zone list, enter transportation zone US-##, and choose save to adopt the US Transportation Zone node. e) When asked to adopt and update the tree, choose Yes. f) In the hierarchy, US-## is displayed. Choose the US-## node. g) In the Hierarchy Fast Entry screen area, enter the following zone names: us -midwest ##,US-WEST-##, US-MOUNTAIN-##, US-SOUTHEAST-##, and US-SOUTH-##. h) Choose Transfer to insert zones into the hierarchy. i) Save your data.



LESSON SU M M AR Y



•




Unit 8 Lesson 4 Defining Methods of Transportation

LESSON OVERVIEW When you define a transportation network, your company must identify all the different locations that ship and receive products. To support planning, you must determine the distance, duration, and cost of transporting products between these locations.

In this lesson, you identify how modes and means of transport can help your organization frame its transportation network in more detail. At the end of this lesson, you will have a detailed understanding of the means of transport hierarchy. You will be able to define the means and modes of transport in SAP TM. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Transportation Mode When all shipping and receiving locations are defined, frame how you intend to ship products between these locations. The complexity of your shipping scenarios influences how much detail you need to maintain. For example, consider whether products are shipped over road, rail, or waterways. Transportation Modes

0



The first configuration step in the transportation process is to identify the transportation modes that can be used to move products. The transportation mode describes the highest-level transport grouping, for example, road, rail, inland waterway, sea, or air. The SAP ERP mode of transport corresponds to the SAP TM transportation mode. Each method of transport is assigned a single transportation mode. Transportation Mode Categories

SAP has defined the four following transportation mode categories: road, rail, sea, or air. In addition to the transportation mode category, companies can assign a dangerous goods transport category. This signals that you may have to ship certain chemicals under pressure and only certain ways of transporting the product are suitable. This category is also defined in Customizing for SAP TM. These categories define the type of transport to be used. Category 99 (all modes) is used in the U.S. according to dangerous goods regulation 49 CFR. Customers can use categories 30 - 89 for their own definition. The Main Carriage The transportation mode can be set as the Main Carriage. The reference to the main carriage indicates that this segment of transportation is the primary segment. When dealing with export scenarios, you may have the pre-carriage, main carriage, and on-carriage. In a multi-modal or multi-stage shipment, the main carriage stage contains all of the shipment documents. It also allows pre- and on-carriage stages to be linked to it. These transportation modes can be used at a high level to determine incompatibilities.



Means of Transport

Figure 140: Means of Transport

When you define the various transportation modes, your company can further define the transportation process by creating and assigning different means of transport. The means of transport describes the characteristics of specific vehicle types or classifications that transport goods, such as a non-refrigerated truck, a refrigerated truck, a 60-foot rail boxcar, or a bulk container. Assigning Vehicle Resources to a Means of Transport The network can be expanded by defining vehicle resources and assigning them to a means of transport. Vehicle resources in a means of transport have a common set of physical characteristics that are taken into account during the planning process. These physical characteristics include the mode of transportation (air, rail, surface, or sea), vehicle capacity, speed, cost structure, geographic availability, and temperature control. Whether a companyowned fleet can be used to group vehicles in a means of transport is also a consideration. Means of transport also allow a company to describe the cost structure and geographical availability of a class of vehicle. Means of Transport Settings

There are a number of means of transport settings: •

Transportation mode

•

Multi-resource

•

Scheduled means of transport

•

Own means of transport

•

GIS quality



Means of Transport Definition

You can define the means of transport in Customizing for SAP TM. Choose SAP Transportation Management —*• Transportation Management —> Master data —*■ Resources —> Define Means of Transport. Transportation Mode Assignment

Within the means of transport you can assign a transportation mode. This specifies how a product is transported, for example, by road, rail, sea, or air. You use the means of transport to select the vehicle resources that are to execute the transportation. The standard code assigned to means of transport represents the official representation of type of transport. The UN/EDIFACT standard uses the following codes: •

006 - Aircraft

•

O il-S h ip

•

031-Truck

•

038 - Car

The relevant settings are: •

Scheduled means of transport: This defines if a resource is traveling based on a fixed schedule such as a sailing or rail schedule.

•

Own means of transport: This determines if a resource is part of your own fleet or that of an external provider.

Multi-Resource

4 8 ft T ractor Trailer

10,20 or unlimited /\

Figure 141: Multi Resource

Instead of creating individual resources for a means of transport, you can select the MultiResource checkbox for the means of transport. During planning, the system assumes the



availability of the number of resources you define. If you do not specify a number in this field, the system assumes that an unlimited number of resources are available. During vehicle scheduling and pre-processing, the number of resources that you define in this field indicates the maximum number of parallel freight orders that the system is allowed to create for each resource. Duration Interstate Highway

Fast - 70 Mph

Medium - 55 Mph

Slow - 4 0 Mph

Figure 142: Speeds

Duration is one of the key elements to consider when dealing with different means of transport. This can be influenced by the type of transport as well as the quality or type of transportation infrastructure used. Selecting the G/S Quality checkbox means your organization is integrating with a third party geographical information system. This integration is specific about which routes (interstate highways or county road) are used. Anticipated speeds for the different types of highways or roads that may be used can be defined.



Distance and Speed

Figure 143: Distance Factor and Average Speed

If you choose not to integrate with a GIS, you still differentiate duration for different means of transport. Within each means of transport you can specify an average speed. The speed is then used, along with the distance from the transportation lane, to calculate transit duration. The distance factor establishes the difference between the linear distance between two locations and the actual distance covered by the vehicle. Based on the linear distance, you can use this factor to estimate the actual travel distance for a vehicle between two locations. Together with the average speed, you can estimate the transportation time. Schedule

Due to the size or limitation of loading and unloading facilities, certain means of transport may not be as readily available as others. Acquiring trucking resources is not as complex as scheduling an export shipment that travels internationally. When dealing with ocean freight, there



are specific departure times for a vessel due to limited port facilities or the cost of using those limited facilities. By selecting the Schedule Means of Transport checkbox, you are indicating that other master data called a schedule is used. This schedule identifies a validity period, a means of transport, a start stop, and a destination stop. Periodic departures can be maintained in the schedule. This would typically be used with ocean, air freight, or specific types of rail movements. Passive Means of Transport

Figure 145: Passive

In scenarios where resources are limited, you may need to separate equipment and define them as two separate means of transport. For example, a tractor can haul 48 and 53 foot trailers, in addition to 20 and 40 foot containers. While the trailers and tractors may be readily available, the containers may have limited availability. You can define the containers as a separate means of transport. However, by defining the container means of transport as Passive, you are indicating to TM that you cannot move the container without assigning a tractor means of transport.



No Capacity, No Load

In the previous scenario where you modeled the tractor and containers as separate means of transport, the focus was on the container not being able to move by itself. During planning, you model the container resources as having a limited capacity. In the case of the tractor, there is no associated capacity, volume, or mass. However, during VSR planning it is necessary to determine if you have enough tractors to pull all the trailers or containers. When modeling this situation, you identify that the tractor has No Capacity in the means of transport. This indicates that during VSR optimization, the number of tractors, and not capacity, is relevant. No Direct Load Direct Load

Figure 147: No Direct Load



A vehicle resource representing both a tractor and a trailer is called direct loading. This is a third scenario when multiple means of transport are required to move a single load. If a means of transport is defined as road, you are not limited by the number of tractors but only by the number of loads that can be executed in a day. During VSR planning, the system sees it as one resource rather than two (direct loading). When dealing with two means of transport, you want the VSR optimizer to first assign the container and then assign the tractor during planning. When you select No Direct Load in the means of transportation, you are indicating that the VSR optimizer does not take into account the resources that are assigned to this means of transport. In this case, you might not want to consider the tractor as a constraint. Means of Transport Hierarchy

Figure 148: Relationships between Transportation Mode, Means of Transport, and Vehicle: An Example

TM allows flexibility in an organization's definition of transportation constraints. As outlined in the figure Relationships between Transportation Mode, Means of Transport, and Vehicle: An Example, for cost purposes there is a need to define three different means of transport. There may be a cost difference between these different methods, and a difference in duration. Additional Considerations Choosing to transport by road may require the consideration of additional factors. For example, produce may need to go in a refrigerated trailer. The distance is the same as in a 53 foot truck, but the cost is different due to the need to keep the trailer at a certain temperature. You may not be able to ship other products this way: their packaging may not be protected against moisture and could be damaged if shipped on this method. When dealing with dry goods, there may be little if any cost difference between a 53 foot and a 48 foot trailer. However, there is a difference in the capacity or amount of product that can be shipped. There may also be a difference in the width of one 53 foot trailer versus another. If you are shipping light weight products, then the capacity dimension mass may not be as important as volume.



Means of Transport and Geography

Once defined, the means of transport are assigned to transportation lanes. As your company creates vehicle resources, they are also assigned to a means of transport. This links resource availability to the geography of the supply network. Means of transport costs are also defined in the transportation lane that aids the VSR optimizer in planning. Where applicable, carriers that can handle vehicles for the means of transport are assigned to the transportation lane. How carrier selection is performed for this means of transport is also defined in the transportation lane.



Create a Means of Transport

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure appropriate customizing settings required for transportation planning. During planning it is imperative to identify if your organization has different options to choose from when shipping products between locations. These options impact the transportation costs and delivery dates based on different transit times. In Customizing, create the means of transport to distinguish different ways of moving product through your network. 1. In Customizing for SAP TM, view all the means of transportation defined in the system. 2. Create a new means of transport FTL-##. This new means of transport has multiple resources and should use GIS quality. Use the following data: Field

Value

Means of Transport

FTL-##

MTr Description

FTL-##

Standard Code

031

Transp. Mode

Road

Average Speed

80

Distance Factor

1,00

3. Create a new means of transport LTL-##. This new means of transport has multiple resources and should also use GIS quality. Use the following data:

0

Field

Value

Means of Transport

LTL-##

MTr Description

LTL-##

Standard Code

031

Transp. Mode

Road

Average Speed

65

Distance Factor

1,00



Create a Means of Transport

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure appropriate customizing settings required for transportation planning. During planning it is imperative to identify if your organization has different options to choose from when shipping products between locations. These options impact the transportation costs and delivery dates based on different transit times. In Customizing, create the means of transport to distinguish different ways of moving product through your network. 1. In Customizing for SAP TM, view all the means of transportation defined in the system. a) In Customizing for SAP TM, choose SAP Transportation Management —> Transportation Management —> Master Data —> Resources —► Define Means of Transport. b) View all available means of transportation codes in the system. Familiarize yourself with the information required to maintain a means of transport. 2. Create a new means of transport FTL-##. This new means of transport has multiple resources and should use GIS quality. Use the following data: Field

Value

Means of Transport

FTL-##

MTr Description

FTL-##

Standard Code

031

Transp. Mode

Road

Average Speed

80

Distance Factor

1,00

a) In Customizing for SAP TM, choose SAP Transportation Management —> Transportation Management —*• Master Data —> Resources —> Define Means of Transport. b) To create a new means of transport, choose New Entries. c) Enter the data from the table. d) Select the Multiresource checkbox. e) Select the GIS quality checkbox.



f) Save your data. g) Continue through any warning messages. 3. Create a new means of transport LTL-##. This new means of transport has multiple resources and should also use GIS quality. Use the following data: Field

Value

Means of Transport

LTL-##

MTr Description

LTL-##

Standard Code

031

Transp. Mode

Road

Average Speed

65

Distance Factor

1,00

a) In Customizing for SAP TM, choose SAP Transportation Management —> Transportation Management —> Master Data —*■ Resources —► Define Means of Transport. b) Choose New Entries to create a new means of transport. c) Enter the data from the table. d) Select the Multiresource checkbox. e) Select the GIS quality checkbox. f) Save your data. g) Continue through any warning messages. Your data will be recorded in a transport means to be promoted to other environments.




•


•




Unit 8 Lesson 5 Defining Transportation Lanes

LESSON OVERVIEW In this lesson we examine how the modeling of a transportation lane is a critical component of your transportation network.

At the end of this lesson, you will be able to identify the data that needs to be defined to create and maintain a transportation lane. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Transportation Lane Usage To model the enterprise supply chain network, it is important to understand how the various sources and destinations of material flows are connected to form the network. The object used to make these connections in the supply chain network is the transportation lane. The transportation lane controls how goods can be transported from one location to another. Transportation lanes play a key role in SAP TM. They control: ■

Which location can forward goods to another location Which means of transport can be used to do so Which carrier can supply a vehicle for the means of transport

Transportation Lane w

Figure 149: Transportation Lane

A transportation lane in SAP TM represents a direct route between two locations. It is used to source and transport products between them. Each lane is defined by its source and target locations, depending on the direction of traffic. A transportation lane has to exist between the two locations to transfer products in the supply chain. Transportation lanes are created in SAP TM for this reason.

0 For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]


Transportation Lane Details •

Transportation Lane

•

Means of Transport

•

Carrier

From ■♦T o - ♦ Validity - ♦ Distance - ♦ Duration Carrier Selection Relevance - ♦ Carrier Selection Settings Priority - ♦ Internal Cost " ♦ Tendering Settings

Figure 150: Transportation Lane Details

In the SAP ERP sales and distribution and logistics execution applications there is an organizational element, the route. It represents an itinerary connecting a shipping point and a customer ship-to address. Although the route definition in the SAP ERP system contains some delivery and shipment planning data, the transfer of route-related information is not performed for SAP TM. The SAP TM transportation lane master data is more precise and flexible for use in the VSR optimizer.



Create Transportation Lanes

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create the transportation lanes required for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercises Examine Location Masters, Define Transportation Zones, and Create a Means of Transport.

1. Create an intra-zone transportation lane for your zone US-## that will represent your default means of transport for all domestic road means of transport for your transportation network. This will include the means of transport FTL-## to which you will assign a cost of 1.25 per KM. 2. Assign the business partners CAR##-01 and CAR##-02 to your means of transport FTL-## to represent which carriers can service your full truckload needs for the entire USA. For carrier CAR##-01 assign a cost of .45 per KM , and a priority of 1 for carrier selection. For CAR##-02, assign a cost of .55 per KM , and a priority of 2 for carrier selection. 3. The origin of your LTL shipments will be shipping point SP3100. Create a location to zone transportation lane for your location SP3100 to US-Southeast-##. This lane will consist of means of transport LTL-##, to which you will assign a transportation cost of .01 per LB. 4. To determine how long this means of transport might take, update your transportation lane by calculating the distance and duration between the locations. 5. What was the distance and duration?

6. Traveling LTL from SP3100 (Chicago area) to the southeast region will take longer than the 13 hours and 34 minutes that was calculated, because this method will not be shipping directly. Because it is likely to go through one or more consolidation and deconsolidation locations, you must add a more realistic time. Overwrite the duration with a fixed duration of 120 hours, assuming the longest possible distance (Florida). 7. Assign the business partners CAR##-03 and CAR##-04 to your means of transport LTL-## to represent the carriers that can service your less than truckload needs. Assign a cost of 0,18 per KG for carrier CAR##-03, and a priority of 1 for carrier selection. Assign a cost of 0,22 per


335



KG for CAR##-04, and a priority of 2 for carrier selection. Consider both for Peer-to-Peer with priority 1 and 2 respectively. 8. Create more lanes between your shipping zone and the other destination zones. Create lanes from your shipping point 3100 to the following zones: US-South-##, US-Midwest-## USMountain-##, and US-West-##, using the mass create function and using the transportation lane between SP3100 and US-SOUTHEAST-## as a template. 9. Because the new lanes are modeling the LTL-## means of transport, you must update the new lanes with a more appropriate duration. Using the mass maintenance feature, update your four new lanes with the following durations: •

SP3100 to US-Midwest-## = 48 hours

•

SP3100 to US-Mountain-## = 96 hours

.

SP3100 to US-South-## = 72 hours

.

SP3100 to US-West-## = 144 hours



Create Transportation Lanes

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create the transportation lanes required for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercises Examine Location Masters, Define Transportation Zones, and Create a Means of Transport.

1. Create an intra-zone transportation lane for your zone US-## that will represent your default means of transport for all domestic road means of transport for your transportation network. This will include the means of transport FTL-## to which you will assign a cost of 1.25 per KM. a) In NWBC, choose Master Data —*• Transportation Network —> Transportation Lanes —> Define Transportation Lane. b) Choose the Intra Zone Lane tab c) In the Loc /Transport. Loc field, enter US-##. d) To create a new lane, choose Create. e) In the Panel for Means of Transport, choose Create. f) Enter the MOT data as follows: .

Means of Transport: FTL-##

.

Validity Start Date: Beginning of current year

.

Validity End Date: 31.12.9999

.

Mns of Trsp. Costs: 1,25

g) Select the Relevant to Carrier Selection checkbox. h) From the Priority/Costs dropdown menu, choose Costs. i) From the Cost Origin dropdown menu, choose Internal Cost. j) Choose Copy and Close. k) Save your data.


0

337



2. Assign the business partners CAR##-01 and CAR##-02 to your means of transport FTL-## to represent which carriers can service your full truckload needs for the entire USA. For carrier CAR##-01 assign a cost of .45 per KM , and a priority of 1 for carrier selection. For CAR##-02, assign a cost of .55 per KM , and a priority of 2 for carrier selection. a) Highlight the means of transport FTL-##. b) In the Carrier screen area, choose Create. c) Assign business partner CAR##-01. d) Enter a cost of 0,45 per KM. e) Enter a priority of 1. f) Select the Consider Carrier for P2P Tendering checkbox.. g) In the Carrier Priority for P2P Tendering field, enter a priority of 1. h) Choose Create and Copy. i) Highlight your means of transport FTL-##. j) In the Carrier screen area choose Create. k) Assign business partner CAR##-02. l)

Enter a Transportation Cost of 0,55 per KM

m) Enter a priority of 2 n) Select the Consider Carrier for P2P Tendering checkbox.. o) Choose Create and Copy. p) Choose Save. 3. The origin of your LTL shipments will be shipping point SP3100. Create a location to zone transportation lane for your location SP3100 to US-Southeast-##. This lane will consist of means of transport LTL-##, to which you will assign a transportation cost of .01 per LB. a) NWBC path Master Data —*■ Transportation Network —*• Transportation Lanes —> Define Transportation Lane. b) In the Tr. Lane tab, in the Start Location/Zone field, enter S P 3100. c) In the Dest. Loc/Zone field, enter US-SouthEast-##. d) To create a new lane, choose Create. e) In the panel for Means of Transport, choose Create. f) Enter the MOT data as follows: .

Means of Transport: LTL-##

•

Validity Start Date: Beginning of current year



.

Validity End Date: 31.12.9999

.

Transportation Cost: 0,10 per LB

•

Select the Relevant to Carrier Selection checkbox.

.

From the Priority / Costs dropdown menu, choose Costs.

.

From the Cost Origin dropdown menu, choose Internal Cost.

•

Choose Copy and Close

.

Choose Save

4. To determine how long this means of transport might take, update your transportation lane by calculating the distance and duration between the locations. a) Choose Generate Proposal. 5. What was the distance and duration? The distance was approximately 882 kilometers, with a duration of 13.34,_________________ 6. Traveling LTL from SP3100 (Chicago area) to the southeast region will take longer than the 13 hours and 34 minutes that was calculated, because this method will not be shipping directly. Because it is likely to go through one or more consolidation and deconsolidation locations, you must add a more realistic time. Overwrite the duration with a fixed duration of 120 hours, assuming the longest possible distance (Florida). a) In the Trsp. Duration field, overwrite the calculated value with 120:00. b) In the Control Indicator screen area, select both the checkboxes for Fix Transportation Duration and Fix Trsp. Distance c) Choose Copy and Close. d) Choose Save. 7. Assign the business partners CAR##-03 and CAR##-04 to your means of transport LTL-## to represent the carriers that can service your less than truckload needs. Assign a cost of 0,18 per KG for carrier CAR##-03, and a priority of 1 for carrier selection. Assign a cost of 0,22 per KG for CAR##-04, and a priority of 2 for carrier selection. Consider both for Peer-to-Peer with priority 1 and 2 respectively. a) Highlight your means of transport LTL-##, and in the Carrier screen area choose Create. b) Assign business partner CAR##-03 c) Enter a cost of 0,18 per KG d) Enter a priority of 1 e) Select the Consider Carrier for P2P Tendering checkbox. f) Enter a priority of 1 g) Choose Create and Copy



h) Highlight your means of transport LTL-##, and in the carrier screen area choose Create. i) Assign business partner CAR##-04 j) Enter a cost of 0,22 per KG k) Enter a priority of 2 l)

Choose Create and Copy

m) Choose Save. 8. Create more lanes between your shipping zone and the other destination zones. Create lanes from your shipping point 3100 to the following zones: US-South-##, US-Midwest-## USMountain-##, and US-West-##, using the mass create function and using the transportation lane between SP3100 and US-SOUTHEAST-## as a template. a) Open the Master Data folder. b) Choose Transportation Network —► Transportation Lanes —> Define Transportation Lane. c) Choose the Mass Maint. (Create) tab. d) In the Copy From screen area enter the Start Location/Zone SP3100 and Destination Location/Zone US-Southeast-##. e) In the Transportation Lanes Between Location screen area, enter Start Location/Zone

SP3100 f) In the Destination Location/Zone field, enter US-South-##. g) Choose multiple selection and enter US-MOUNTAIN-##, US-Midwest-##, and US-West## h) Select the Existing Transportation Lanes are Overwritten radio button. i) Select the Calculate Transport Durations and Distances radio button. j) Choose Create. k) Answer Yes to create the Four transportation lanes 9. Because the new lanes are modeling the LTL-## means of transport, you must update the new lanes with a more appropriate duration. Using the mass maintenance feature, update your four new lanes with the following durations: •


•


.


.


a) Go to the Mass Maint. (Display/Change) tab.

b) In the Start Location/Zone field, enter SP3100.



c) In the Destination Location/zone field, enter US-*-##. d) Choose Change. e) Update the MTr for your LTL-## for each lane. f) Select the Fix Transportation Duration and Fix Trsp. Distance check boxes. g) Update the lanes with the following durations: •


•


.


.


h) Save your data.



Distance Duration Determination (DDD) Vehicle-supported business processes such as transportation planning must deliver services rapidly and cost-effectively. Reliable routing information supports transportation planning by providing the shortest driving distance between a start and destination location. Hard constraints such as height or weight restrictions of the vehicle used are taken into account. Duration information may also be required for scheduling. It can be calculated based on distance and speed parameters of the deployed means of transport. The Transportation Lane In SAP TM, the transportation lane master data object links two locations. The transportation lane stores distance and duration information for each means of transport assignment. This information can be determined by calculating a straight-line distance, taking into account the spherical shape of the earth, and a deviation factor specific to the means of transport. The actual area in between is ignored. If this does not fulfill business process requirements regarding accuracy, it is possible to determine distances and durations using an external provider or GIS.

W ith GIS

By connecting the GIS, distance and duration time can be calculated for each means of transport within a transportation lane using exact road details. Figure 151: Distance Duration Calculation

Distances and Durations between two SCM Locations

Distances and durations between two SCM locations are calculated when the transportation lane is created. The user can trigger a re-determination manually or overwrite the values. The values of external determinations are buffered for each location pair. SAP TM retrieves distances at the time of planning either from the buffer table or based on the defined strategy. Corresponding transportation lanes are generated between all locations assigned to the transportation zones. Cost information is taken from the transportation lanes maintained. Distance and duration are calculated according to the settings; they can also be taken from the maintained transportation lane. The maintained distance in the master transportation lane includes a factor for street map variability that is obtained from the means of transport. This factor establishes the proportion



between the linear distance between two locations and the actual distance covered by the vehicle transporting goods between them. GIS System Included in the means of transport is the average speed of the transport method. The runtime distance is divided by the average speed to calculate the estimated duration. If an external geographical information system is used to calculate distances, they are stored in a separate buffer table and are not calculated at runtime. You can flag if this means of transport is calculated by a GIS system. If the flag is not set, the aerial distance is used. If the GIS flag is set, the low, medium, or high speed is used. GIS systems typically categorize streets as slow, medium, or fast. Buffering Distances and Durations Based on Coordinates

In SAP TM 8.0, the distance between two locations was determined based on the most accurate geo-coordinates, even if this accuracy was not required. This concept leads to a high number of determinations when running mass processes. To support large-scale scenarios, it is possible with EHP1 to configure optionally the DDD to use coordinates based on geo-coding levels to balance accuracy and performance. To support this new concept, distances and durations are now buffered based on coordinates. It is possible to connect to different GIS providers for geo-coding using the process controller framework.



Transportation Lane Master Data

The transportation lane can be maintained as master data. From the SAP TM main menu, choose Master Data->Transportation Network->Define Transportation Lane. For each means of transportation, distances and durations can be calculated in a batch job using the GIS server or manually in lane maintenance. On completion of the batch jobs, the durations and distances are stored in a buffer table. If a location is added or modified, this background job is executed again to update the GIS information. Process Controller

As part of enhancement package one (EHP 1) for SAP SCM 7.0, geo-routing has been enhanced with the following features: •

Usage of Process Controller

•

Process specific Distance and Duration Determination

•

Performance improvements for Distance and Duration Determination (DDD)

You can create different Process Controller Routing strategies that link to different GIS vendor products: this enables flexible connections. Distance and Duration Determination is handled separately and with its own strategies. The created Process Controller strategies for DDD can be used to fulfill different requirements of business processes. For example, if a particular means of transport requires a different DDD, this can be defined in customizing.



Geocoding Level 10: Region

Figure 154: Distance and Duration Determination Using Geocoding Level 10: Region

The geo-coordinates for the start and destination locations are stored at region level. Geocoding Level 20: Postal Code

Figure 155: Distance and Duration Determination Using Geocoding Level 20: Postal Code

The geo-coordinates for the start and destination locations are stored at postal code level.



Geocoding Level 30: House Number

Figure 156: Distance and Duration Determination Using Geocoding Level 30: House Number

The geo-coordinates for start and destination locations are stored at house number level. The system determines the distance and duration for all transportation lanes individually because the geo-coordinates of all destination locations are unique. The system therefore needs to call the DDD service four times.



Unit 8 Exercise 22 Calculate Durations and Distances using Transportation Lanes

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to calculate durations and distances using transportation lanes required for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Create Transportation Lanes.

1. Which levels can be used for geocoding, if no external GIS system is connected to SAP TM?

2. Why are distances buffered?

3. Can you use different strategies to obtain distances?

4. Why would you use different strategies to obtain distances based on the straight-line distance itself?

0



Unit 8 Solution 22 Calculate Durations and Distances using Transportation Lanes

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to calculate durations and distances using transportation lanes required for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Create Transportation Lanes.

1. Which levels can be used for geocoding, if no external GIS system is connected to SAP TM? SAPO offers geocoding based on country level and region level taken from the address. 2. Why are distances buffered? Distances are buffered because it is too time-consuming to retrieve distances from the external GIS system each time they are required.____________________________________ 3. Can you use different strategies to obtain distances? Yes. You can define different process controller strategies to define distances. Which strategy is called is determined in the customizing.__________________________________________ 4. Why would you use different strategies to obtain distances based on the straight-line distance itself? Based on the straight line distance, it may be sufficient to plan on different levels of granularity. For distribution within the city, you require the exact distances and duration. For transport between the east and west coast, distances determined based on zip codes may be sufficient.




•


•




Unit 8 Lesson 6 Creating Carrier Profiles

LESSON OVERVIEW In this lesson, we examine the carrier profiles that must be maintained for successful automatic planning. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


•


•


Carrier Profiles Third-party logistics providers (3PLs) include freight forwarders, courier companies, and companies integrating and offering subcontracted logistics and transportation services. Among the services 3PLs provide are: transportation, warehousing, cross-docking, inventory management, packaging, and freight forwarding. Business Partners

Create business partner ’

■____ ________________________ ■

'

Assign partner role: Carrier '

' Create carrier profile

Figure 157: Transportation Service Provider: Required Settings

A business partner is a person, organization, group of persons, or group of organizations in which a company has a business interest. You can create and manage centrally your business partners (BPs) and the roles they assume for your company.



For this purpose, define the general data of the business partner once and assign BP roles to the business partner. Specific data is stored for each business partner role. Redundant data is not stored because the general data is independent of a business partner's function or of applicationspecific extensions. When you first create a business partner in the system, the BP role General Business Partner is automatically assigned to the business partner. Carrier Integration

ERP master data ■ Vendor (carrier)

✓\

Figure 158: Transportation Service Provider: Integration ERP to TM

In an integrated SAP ERP and SAP TM system landscape, the ERP system is frequently the leading master data system. In this case, the customer and supplier master data is maintained in the ERP system. It is transferred from there to SAP TM using the SAP CIF as locations and business partners. For carriers, (vendors with a specific account group), business partner data can be created in SAP TM through CIF. The CIF integration model must be set up to create business partners. In business transaction documents, the BP master data object appears as a party that takes part in transportation processes. The party assumes party roles, such as consignee, shipper, or ordering party. Business partners can also be created manually in SAP TM by choosing Transportation Management —> Master Data —► Maintain Business Partner The Carrier Profile The carrier profile allows you to see:

Transportation lane assignment Freight code set assignment Product freight assignment Transportation group assignment



•

Equipment group assignment

•

Fixed transportation costs

•

Dimension costs

The carrier profile is maintained in SAP TM from the main menu: Master Data —► Transportation Network —> Define Carrier Profile Carriers are business partners to whom you have assigned the business partner role carrier. The carrier profile allows you to see the assigned lanes from the carrier's perspective. You can also remove existing assignments and add new assignments. Mass Maintenance of Lanes and Costs Carriers can be assigned to a specific geography in the transportation lane or the transportation lane can be assigned to the carrier in the carrier profile. Carrier selection can be based on TCM cost or based on internal cost. These internal costs can be maintained on the transportation lane or in the carrier profile. The mass maintenance of lanes and costs involves the assignment of carriers to transportation lanes. The cost basis for carrier selection if internal cost are used consists of the following transportation lane specific components: •

Distant dependent (per means of transport and carrier)

•

Quantity dependent (per means of transport and carrier)

The cost basis for carrier selection if internal cost are used consists of the following carrier profile specific components: •

Transportation lane costs

•

Fixed costs (per means of transport)

•

Distant dependent (per means of transport)

•

Duration dependent (per means of transport)

•

Quantity dependent (per means of transport)

The Carrier Profile

•

Transportation lane assignment

•

Fixed transportation costs

•

Dimension costs

You can store the following information in a carrier profile: Fixed transportation costs Instead of maintaining fixed transportation costs for each transportation lane if a fixed cost is to be allocated, storing the information in a carrier profile allows a central location for data maintenance.



Dimension costs Dimension costs are used to assign costs per carrier per means of transport based on a specific cost dimension such as duration, distance, or quantity. These costs could be used to determine which carriers are selected during planning to transport a load. Product and Transportation Groups Freight codes are used with freight code sets of freight forwarders and rail carriers to classify the goods that are to be transported. Freight codes are used for communication with freight forwarders and are specified in the shipping papers. Some freight codes are issued by freight forwarders and rail carriers and are used specifically for transportation by rail or road because these are means of transport-specific. The Carrier Profile

•

Freight code set assignment

•

Product freight assignment

•

Transportation group assignment

•

Equipment group assignment

You can store the following information in a carrier profile: Freight code sets These codes classify goods that are to be transported and support communication between the shipper and the freight forwarder. Transportation lane and carrier-specific parameters A carrier may be assigned to multiple transportation lanes, but the carrier profile allows a centralized view of their responsibilities. Product freight groups Product freight groups are used to determine the freight codes and freight classes for a freight code set. You use these to communicate with service providers. Transportation groups Transportation groups are used to group products together that have the same requirements for transportation. For example, you have a company that produces food. If you want to transport food that is perishable and must be kept cool during transport, you create a transportation group for products that need to be shipped together in a refrigerated vehicle. The determination of the freight codes involves the following steps: 1. From the carrier profile, determine the freight code set based on the carrier, forwarding country, and means of transport. 2. In Customizing, determine the freight code set based on the freight code set and product freight group.



Equipment Groups and Equipment Types

Equipment types form the most integral part of the entire shipping industry. These shipping containers are the structures that store the various different products that need to be shipped from one part of the world to another. Depending on the type of products being shipped or the special services needed for them, equipment types may vary in dimension, structure, materials, construction and so on. Various types of shipping containers are being used to meet the diverse requirements of the cargo shipping world. Some of the most common types of shipping containers in use today are as follows:

Dry Storage Containers Flat Rack Containers Open-top Containers Tunnel Containers Open-side Containers Double-door Containers Refrigerated Containers Insulated/Thermal Containers In SAP TM, a resource can be linked to a piece of equipment. Equipment types determine the type of truck or equipment that is requested to show up to carry out the shipping.



Equipment Groups

Figure"160: Equipment Groups

When your business requires that specific types of containers or equipment are needed, you may want to tie this fact into your business process. With SAP TM, you can define equipment groups and specify different types of shipping containers. For example, in the air industry, the term Universal Loading Device (ULD) is used to describe the type of container that is applicable depending upon the type of plane being used. In the ocean and road industry it would be the type of container or trailer that may be required based on the weight or dimension of the items being shipped. In SAP TM you can define equipment groups as well as equipment types. Within an equipment group you define different types of equipment that have various limitations based on weight, volume, or temperature. Equipment groups are specific to a transportation mode. Depending on the assigned transportation mode, you can enter values for ocean-specific or land-specific containers, or for air-specific unit load devices (ULDs). Equipment Type and Resource Integration




Carrier Profile

Figure 161: Applying Equipment Types

Equipment types can be used when creating freight units, forwarding orders, or forwarding quotation items. You use equipment groups to group equipment types into categories. Equipment types can be used in the following contexts: •

Carrier profiles: When you define carrier profiles, you can use equipment types to describe the kind of equipment that is owned by a specific carrier.

•

Container: You can use equipment groups and types, for example, when creating forwarding orders or forwarding quotation items of the container category. Data in relation to the physical properties of the container is then available in the forwarding order and subsequent business documents as information for the planner. In addition, after you have entered the equipment group, the equipment type, and the number of containers in the forwarding order, the system calculates the tare weight and the capacity of the container in TEU based on settings applied in Customizing.

•

Freight Unit Building: When you create freight units, you can take equipment types and their physical properties into account instead of the planning-relevant quantities.

Note that you can link equipment types to a means of transport. This indirectly links it to a resource.



Unit 8 Exercise 23 Create Carrier Profiles

Business Example

When doing business with new carriers or when business relationships with existing carriers change, these changes need to be reflected in the transportation network. For this purpose, you need to maintain carrier profiles.


1. In NWBC, create a carrier profile for CAR##-01. Check the assignment of transportation lanes to your carrier. 2. Which transportation lanes are assigned to CAR##-01?

3. Is CAR##-01 eligible for continuous moves? Maintain carrier CAR##-01 for continuous moves.

4. Create similar carrier profiles for CAR##-02, CAR##-03, and CAR##-04.


0

357



Unit 8 Solution 23 Create Carrier Profiles

Business Example When doing business with new carriers or when business relationships with existing carriers change, these changes need to be reflected in the transportation network. For this purpose, you need to maintain carrier profiles.


1. In NWBC, create a carrier profile for CAR##-01. Check the assignment of transportation lanes to your carrier. a) In NWBC, choose Master Data —► General —► Define Carrier Profile. b) On the Maintain Carrier Profile screen, choose Q Create. c) Enter car ##-01 in the Business Partner field. d) Choose ^C o n tin u e to start creating profile data. e) Save your data. 2. Which transportation lanes are assigned to CAR##-01? On the Transportation tab, you can see that the carrier is assigned to transportation lane US# # to US-## for means of transport FTL-##.________________________________________ 3. Is CAR##-01 eligible for continuous moves? Maintain carrier CAR##-01 for continuous moves. In the upper table, scroll to the right. The continuous move flag is not selected, so the carrier is not eligible for continuous moves._______________________________________________ a) Select the Continuous Moves checkbox. b) Save your data. 4. Create similar carrier profiles for CAR##-02, CAR##-03, and CAR##-04. a) Repeat Steps 1-3 for each carrier.



LESSON SU M M AR Y



•


•


•




Unit 8 Lesson 7 Examining Resources in SAP TM

LESSON OVERVIEW

To generate feasible shipments during transportation planning, you must consider shipping constraints. This lesson examines how you define vehicle resources that restrict how much produce can be managed in a single transport. At the end of this lesson, you will be able to identify the calendar and handling resources that manage the loading and unloading capabilities of locations. LESSON OBJECTIVES



•


•


Business P artner Operating Hours

■—

m—

■

09:00 17:00

09:00 17:00

09:00 17:00

09:00 17:00

09:00 17:00

09:00 17:00

Figure 162: Business Partner Operating Hours

Business partner operating hours need to be considered in transportation planning processes. Operating hours are represented as resources (calendar or handling) in SAP TM. Calendar resources represent operating hours without capacity constraints, whereas handling resources limit the number of parallel activities (loading and unloading) that can be scheduled in parallel. Calendar Resources



Calendar resources determine the operating hours of locations. Loading and unloading activities can only take place during operating hours. Calendar resources are defined as resources and can be assigned to multiple locations as: •

Inbound operating hours

•

Outbound operating hours

•

Means-of-transport specific operating hours (inbound)

•

Means-of-transport specific operating hours (outbound)

Availability times can be maintained by defining capacity variants and shift sequences. Handling Resources

Availability times can be maintained by defining capacity variants and shift sequences. Consumed capacity per loading and unloading operation is maintained in the location master data with the assignment of the (means of transport-specific) handling resource. The available capacity is maintained in the resource master data record. Vehicle Resources

A vehicle resource represents a separate resource type and is used only in TM. Each vehicle resource defined in SAP TM represents a unit load, for example, one trailer of a certain capacity, one container of a certain capacity, or one rail car of a certain capacity. In VSR planning, a specific vehicle resource is assigned to each freight order by the optimizer. The vehicle resource commits to that freight order for the duration of the shipment process and cannot be assigned to another freight order during this period. Ensure that enough vehicle resources are created and available for VSR planning for the projected number of freight orders that might be created over a period of time. A mass creation function exists.

Vehicle Resources: Passive and Active A vehicle resource is a specific type of vehicle. There are two types of vehicle resources: passive and active. Active vehicle resources can travel by themselves. Passive vehicle resources cannot travel by themselves. A truck that has a motor and can travel by itself is an active resource. An empty trailer with no tractor is a passive resource.



Vehicle resources are designated as public or private resources. This is configured in the means of transport. If you do not set the own flag, the system will interpret the resource as public (subcontracted). Vehicle Resource M aster Data C reation

The vehicle resource is a multi-dimensional resource. It can have up to 8 dimensions. For example, the capacity of a trailer can be specified as 40,000 LBS or 2200 cu. ft. or 24 pallets. However, the available capacity for this resource type cannot be maintained on a time-dependent basis. To maintain limited availability, you can do so through shift sequences. Vehicle Resource M aster Data C reation

When creating a vehicle resource it is recommended that the following information is input: -

A resource name A calendar and time zone A capacity

Vehicle Resource M aster Data

Transportation between locations is executed by the means of transport. The vehicle resource uses the characteristics of the means of transport, for example, truck, ship, or aircraft. Each vehicle is assigned to a single means of transport. Vehicle Resource Master Data: Required Fields The Time Zone field is required. This refers to the time zone in which the resource resides. Factory Calender is a required field and is used in planning. Continuous Dim is a required field. Continuous dim stands for the dimension of the resource. It specifies in which dimension the resource is scheduled. Capacity defines the capacity of the resource. If the multiple dimensions are maintained, the system will consider all of the dimensions in planning. During optimization, the solve will fail if either of the dimensions (weight, volume, or mass) are exceeded. Unit refers to the unit of measure of the capacity. Unit uses the alternate unit of measure that is common in SAP. Capacity, continuous dim, and unit of measure work together to determine the capacity and volume. Enterprise Asset M anagem ent Integration for Vehicle Resources

You can use the following types from ERP: •

Equipment

•

Functional location

CIF was extended to allow the transfer of equipment and functional locations (there is no evaluation of equipment or functional location hierarchy). Not all TM relevant information is available in ERP, so this needs to be created via TM customizing (for example, resource type and resource class). For resources created via CIF, ERP is the leading system, that is, ERP overwrites changes done manually in TM.



The last resource types in SAP TM are transportation unit resources. A transportation unit resource is an instance of a particular transportation unit, such as a container, that you can use to map the capacity and availability that you want to use for transportation. The equipment type and equipment group specify attributes such as the physical properties of a certain kind of transportation unit resource. Drivers are not modelled as resources in SAP TM. A driver is any person who can operate vehicles and perform transportation-related tasks as a result of certain qualifications. You can specify a driver as a party in SAP TM business documents. P aram eters fo r Drivers

You can define the following parameters for drivers: •

Availability

•

Absences

•

Qualifications

•

Supply Chain Unit (represents the driver's home location)





Unit 8 Exercise 24 Define Capacity Limits with Vehicle Resources

Business Example

ABC Corporation wants to implement SAP TM to support a truck-load (TL) and less-than-truckload (LTL) planning scenario. Sue, the SAP consultant, needs to configure the appropriate resources needed for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Create a Means of Transport.

1. In NWBC, create a vehicle resource using the following data: Field

Value

Resource

FTL-##

Resource Class

Truck

Means of Transport

FTL-##

Time Zone

CST

Continuous Dimension

Mass

Factory Calendar

US

Capacity

45000

Unit

LB

2. Create a vehicle resource using the following data:

0

Field

Value

Resource

LTL-##

Resource Class

Truck

Means of Transport

LTL-##

Time Zone

CST

Continuous Dimension

Mass

Factory Calendar

US



Field

Value

Capacity

25000 LB

Unit

3. Create opening hours for customer CUST##-25. The customer should be able to receive goods from Monday to Friday, from 9.00am to 5.00pm. Create a calendar resource for this purpose and assign it to your customer master record. Field

Value

Resource

CUST##-25 CST US

Time Zone Factory Calendar

4. Define a shift using the data in the following table:: Field

Value

Shift

GR## 31.12.9999 09:00:00 17:00:00

Valid to Start Time End Time

5. Create a shift sequence using the Shift Sequences tab and the following data: Field

Value

Shift Sequence

GR##-MF 1 31.12.9999 Can start or finish on a non-work day GR##

Day Number Valid To Non Work Days Shift 1

The shifts should repeat every seven days, but shifts should only be available on days 1 to 5. 6. Maintain a capacity variant. From the Resource screen, enter the resource and choose Capacity Variants. Assign an active variant of 01. Use the following data: Field

Value

Resource

CUST##-25 01

Capacity Variant



Field

Value

From

Beginning of current year

To

End of next year

Shift Sequence

GR##-MF

First Day

Choose First Day depending on the weekday of the date maintained in the FROM field. For example, 1= Monday, 2= Tuesday, and so on.

Workdays

Workday according to Factory Cal

7. Assign your calendar resource to the customer location. Use the following data: Field

Value

Location

CUST##-25 CUST##-25 CUST##-25

Inbound Operating Times Outbound Operating Times



Unit 8 Solution 24 Define Capacity Limits with Vehicle Resources

Business Example ABC Corporation wants to implement SAP TM to support a truck-load (TL) and less-than-truckload (LTL) planning scenario. Sue, the SAP consultant, needs to configure the appropriate resources needed for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Create a Means of Transport.

1. In NWBC, create a vehicle resource using the following data: Field

Value

Resource

FTL-## Truck FTL-## CST Mass US 45000 LB

Resource Class Means of Transport Time Zone Continuous Dimension Factory Calendar Capacity Unit

a) Open the Master Data folder and choose Resources —>Define Resource. b) Enter the resource and choose Q Create. c) Enter the data from the table. d) Save your data. 2. Create a vehicle resource using the following data: Field

Value

Resource

LTL-## Truck

Resource Class



Field

Value

Means of Transport

LTL-##

Time Zone

Capacity

CST Mass US 25000

Unit

LB

Continuous Dimension Factory Calendar

a) Repeat Step 1 using the data from the table. 3. Create opening hours for customer CUST##-25. The customer should be able to receive goods from Monday to Friday, from 9.00am to 5.00pm. Create a calendar resource for this purpose and assign it to your customer master record. Field

Value

Resource

CUST##-25 CST US

Time Zone Factory Calendar

a) Open the Master Data folder and choose Resources —► Define Resource. b) Enter the resource from the table and choose Q Create. c) Choose the Calendar tab and enter the data from the table. 4. Define a shift using the data in the following table::____________________ Field

Value

Shift

GR## 31.12.9999 09:00:00 17:00:00

Valid to Start Time End Time

a) Choose Definitions and select the Shifts tab. b) Enter the data from the table. 5. Create a shift sequence using the Shift Sequences tab and the following data: Field

Value

Shift Sequence

GR##-MF

Day Number

1



Field

Value

Valid To

31.12.9999 Can start or finish on a non-work day GR##

Non Work Days Shift 1

The shifts should repeat every seven days, but shifts should only be available on days 1 to 5. a) Select the Shift Sequences tab to create daily windows and enter the data from the table. b) Create similar entries for days 2-7. Highlight your shift sequence and day. You can also choose Copy. Ensure the day is sequential to the previous entry. Remove the shift entry GR## from days 6 and 7. c) Save your shift sequence. d) Go back to the Create Resources: Header Data screen. 6. Maintain a capacity variant. From the Resource screen, enter the resource and choose Capacity Variants. Assign an active variant of 01. Use the following data: Field

Value

Resource

CUST##-25 01 Beginning of current year End of next year GR##-MF

Capacity Variant From To Shift Sequence First Day

Choose First Day depending on the weekday of the date maintained in the FROM field. For example, 1= Monday, 2= Tuesday, and so on.

Workdays

Workday according to Factory Cal

a) Choose Capacity Variants —>Interval to create new capacity variants. b) Enter the data from the table. c) Choose Continue to accept the data. d) Save the capacity variant. e) Go back to the Resource Maintenance screen. f) In the General Data tab, in the Available Capacity screen area, enter the active variant 01. g) Save your data. 7. Assign your calendar resource to the customer location. Use the following data:



Field

Value

Location

C U S T # # -2 5

Inbound Operating Times

C U S T # # -2 5

Outbound Operating Times

C U S T # # -2 5

a) Open the Master Data folder and choose Transportation Network —> Locations —> Define Location b) Enter the location. c) Choose Change to modify the location data. d) Choose the Resources tab to assign a calendar. e) Select the Operating Times radio button f) Enter the Inbound Operating Times and Outbound Operating Times. g) Save your data.





•


•




Unit 8

Learning Assessment

1. Which of the following are aspects of integration that the CIF supports? Choose the correct answers.

□ □ □ □

A The initial integration of an object. B The initial creation in TM. C The activation of the existing integration models. D The transfer of changes to data records.

2. Assigning partner functions in the SAP system determines the functions of particular partners in the sales process. Each partner can have only one function. Determine whether this statement is true or false.

□ □

True False

3. When you create transportation zones, it reduces the amount of master data in the system by grouping locations together. Which of the following are examples of transportation zones? Choose the correct answers. I A Regional Zones B Postal Code Zones | C Country Zones D City Zones E Island Zones

0



4. You cannot assign a transportation zone to itself or to a zone already assigned to the same zone. Determine whether this statement is true or false. | True False 5. When defining the means of transport, you may want to limit how many resources are available when planning. When you select the Multi-Resource checkbox, you can define how many of these types of transport are available. Determine whether this statement is true or false. | True False 6. The transportation lane stores distance and duration information for each means of transport assignment. Determine whether this statement is true or false. | True False 7. When can loading and unloading activities take place? Choose the correct answer. | A Loading and unloading activities can take place outside operating hour when planned in advance. B Loading and unloading activities can only take place during operating hours. C Loading and unloading activities can take place only before 08.00 hours. D Loading and unloading activities can take place regardless of the operating hours defined by calendar resources.



8. Which of the following vehicle resource attributes are considered for planning? Choose the correct answers.

□ □ □ □

C Time zone

□

A Capacity

E Fuel type

B Means of transport

D Fuel economy




1. Which of the following are aspects of integration that the CIF supports? Choose the correct answers.

|~xj A The initial integration of an object. |~xj

B The initial creation in TM.

|~xj C |~xj

The activation of the existing integration models.

D The transfer of changes to data records.

Correct. The CIF supports all these aspects of integration: the initial integration of an object, for example, a specific customer master, and the initial creation in TM. Over time the master data may be updated in SAP ERP to keep ERP and TM in sync. Integration models are regenerated and activated periodically. 2. Assigning partner functions in the SAP system determines the functions of particular partners in the sales process. Each partner can have only one function. Determine whether this statement is true or false. | True \x \ False Correct. One partner may have several functions.



3. When you create transportation zones, it reduces the amount of master data in the system by grouping locations together. Which of the following are examples of transportation zones? Choose the correct answers. [x ] A Regional Zones [x~| B Postal Code Zones

[~xj

C Country Zones D City Zones E Island Zones

Correct. Regional, postal code, and country zones are all types of transportation zones used inTM. 4. You cannot assign a transportation zone to itself or to a zone already assigned to the same zone. Determine whether this statement is true or false. [x ] True False Correct. No recursive assignments are allowed. 5. When defining the means of transport, you may want to limit how many resources are available when planning. When you select the Multi-Resource checkbox, you can define how many of these types of transport are available. Determine whether this statement is true or false. [x ] True False Correct. In Customizing for TM, by selecting the Multi-Resource checkbox you define how many types of transport are available in planning.



6. The transportation lane stores distance and duration information for each means of transport assignment. Determine whether this statement is true or false. 0

True False

Correct. In SAP TM, the transportation lane master data object links two locations. The transportation lane does store distance and duration information for each means of transport assignment. 7. When can loading and unloading activities take place? Choose the correct answer. | A Loading and unloading activities can take place outside operating hour when planned in advance.

|~xj

B Loading and unloading activities can only take place during operating hours. C Loading and unloading activities can take place only before 08.00 hours. D Loading and unloading activities can take place regardless of the operating hours defined by calendar resources.

Correct. Calendar resources define the operating hours of locations, and as a result, loading and unloading activities can only take place during operating hours. 8. Which of the following vehicle resource attributes are considered for planning? Choose the correct answers.

|~xj

A Capacity

|~xj

B Means of transport

\x \ C Ti me zone D Fuel economy E Fuel type Correct. Capacity, location, means of transport, time zone, and continuous dimension are attributes that are considered for planning.



UNIT 9

Conditions and Incompatibilities

Lesson 1 Defining Conditions in SAP TM

380

Lesson 2 Identifying Incompatibilities Exercise 25: Create Incompatibility for Transportation Groups

383 387

UNIT OBJECTIVES

0

•

Examine conditions

•

Identify the purpose of incompatibilities

•

Create incompatibility definitions

•

Create incompatibility settings



Unit 9 Lesson 1 Defining Conditions in SAP TM

LESSON OVERVIEW In this lesson, we examine how conditions are used in SAP TM. Conditions are used throughout SAP TM to adapt the software to user processes. Different condition types are used in different areas, from ERP Logistics Integration, planning, execution to charge calculation and settlement.

Conditions can have different origins. They can be as simple as direct business object access conditions that simply read a value from a predefined field, or as complex as business rules framework plus (BRF+) decision tables or expressions. At the end of this lesson, you will be able to identify condition types used in SAP TM and know how to create conditions. LESSON OBJECTIVES After completing this lesson, you will be able to:

•

Examine conditions

Condition Usage Conditions are tests performed against various objects, such as transportation requirements or freight units, to determine whether a situation is true or false. For example, to decide if products on a single transportation requirement can be shipped together, each item on the OTR is checked for certain parameters. If a certain parameter is found, rules are built to determine where consolidation can take place. If an incompatibility exists, more than one shipment is necessary. Condition Types

Over fifty predefined condition types are used in the following: Incompatibilities Document type determination Organizational unit determination Printing Approvals Change controller: tolerances Loading and unloading durations Transportation charge management Customer-specific rules



Dependent Values

Use conditions to determine dependent values in the following areas: •

Filtering freight units

•

Determining freight unit building rules (FUB rules)

•

Incompatibilities

•

Determining the sales organization

•

Determining transportation charge rate tables and agreements with a charge calculation rule

•

Change controller

Condition Definition This concept examines the origin of the condition, and input and output values. Origin of Condition

•

Direct Business Object Access

•

BRF+Decision Table

•

BRF+ Expression

•

Input Value There are various input values and they are determined by the following factors:

•

-


-

Data Crawler

-

Determination Class

Output Values -

Depending on Condition Type (field or structure)

Input and Output Values Define input values for each condition by defining business object fields including user-specific fields, or values determined in external determination classes. The available input values depend on the condition type chosen. The condition type defines the area in which the system is to take the condition into account. SAP delivers a number of condition types in the standard system. The output values are determined by the condition type. For example, the FUB rule is a result of FUB rule determination. The system generates a Business Rule Framework plus (BRFplus) decision table from input and output values. The system processes this table from top to bottom during determination. When the system finds a row in the BRFplus decision table whose input values match the current input values, it copies the corresponding output values and processes them in the area that made the call. SAP delivers the following in the standard system:



•

Condition types

•

Customer condition types

•

Data access definitions

•

Assignment of data access definitions to condition types (including specification of which data access definitions are used by default for a condition type)

Condition Type Definition

If you need additional fields for the condition types to be delivered as standard, or if you want to use customer condition types, create new data access definitions and extend the assignments in Customizing. You can also change or add to the data access definitions used by default. The condition type must be identified when defining a condition in SAP TM. A condition type is a configurable object that is based on field contents stored in various business object nodes. Each condition type is assigned to a business object (structure) and the node name (at the header or item level). When defining a condition type, you can identify when a result is found, if it is stored in a structure, and if one or more conditions may exist for this condition type. Condition types are then assigned to data access definitions. These objects specify what fields and in what sequence users can define specific condition records. Conditions are used throughout SAP TM in planning and execution. Specify the condition type, the fields against which you are testing, and how you want to store the test results when creating a condition. This is referred to as the origin of the condition. The Origin of the Condition

In SAP TM, there are three different origins: •


•

Condition Based on BRFplus Decision Table

•

Condition Based on BRFplus Expression

The Direct Business Object Access condition returns directly the value determined by the data access definition. There is no evaluation of the data. The BRFplus Decision Table condition takes the input of the data access definition and evaluates it in a table. This condition table can be maintained from the condition user interface. The BRFplus Expression can be maintained in the form of nested if/then statements. LESSON SUMMARY You should now be able to:

•

Examine conditions



Unit 9 Lesson 2 Identifying Incompatibilities

LESSON OVERVIEW As part of the planning process, a company defines various rules and guidelines regarding the items that can and cannot be shipped together. These scenarios are referred to as compatibilities or incompatibilities.

In this lesson, you will examine how conditions are created to support incompatibility rules that are used in planning. At the end of this lesson, you will be able to create an incompatibility for transportation groups. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


•


Incompatibilities During transportation planning, companies prepare a set of guidelines regarding shipping. For example, if a shipper has products that need to be transported via a refrigerated container, they cannot ship those products with frozen freight units. While planning transportation shipments, companies define rules regarding how they consolidate loads into a single freight order. There are many factors other than capacity that impact how freight orders are built. In SAP TM, these rules are called incompatibilities. This data defines the relevant parameters controlling when it is and is not appropriate to consolidate loads.

0



Consolidation

C h ille d

F ro z e n

Figure 164: Conditions and Incompatibilities

In the figure, a company has a variety of products to ship. The temperature at which items must be stored during transit is the attribute that signals if items can be consolidated. A test is executed to decide the temperature in which each product is shipped. A rule states that items classified as chilled cannot be shipped with items classified as frozen. This could lead to damage or spoilage if a product is shipped at the wrong temperature. Incompatibilities and Conditions Incompatibilities are used in combination with conditions to influence the results in SAP TM during freight unit building, transportation planning, transportation proposals, and carrier selection. Incompatibilities are important when defining requirements for load building. For example, freight units with different incoterms must not be transported together. Refrigerated goods need to be transported in appropriate means of transport. Certain means of transport cannot be loaded at a specific location because the location does not have a suitable loading ramp. Incom patibility Application

Incompatibilities are defined in SAP TM. Choose Application Administration —> Planning —► General Settings —> Incompatibility Definitions —> Create Incompatibility. Incompatibilities can be defined between two attributes of two business objects. This requires that two conditions are defined and relevant results are specified.Two business objects are then incompatible if the result of the conditions matches the relevant results. Setting the Identical Values Only checkbox in the incompatibility definition allows for an incompatibility to be defined between two instances of the same business object, for example, two freight units. In this case, a single condition is defined in the incompatibility definition. The two business object instances are then only incompatible if their values differ.



Incom patibility Definitions

When creating an incompatibility definition, one must specify a validity area. Validity areas are comprised of an incompatibility area and an incompatibility type. Incompatibility areas define where an incompatibility can be used. Four incompatibility areas exist in TM: •

Vehicle scheduling and routing planning

•

Freight unit building

•

Carrier selection

•

Delivery proposals

Incom patibility Types

Incompatibility types are delivered by SAP and define the objects that are the focus of the rule being enforced. The following list contains examples of incompatibility types: •

Freight unit - Freight unit

•

Freight unit - Vehicle

•

Freight unit - Transshipment location

•

Carrier - Transportation Order

In addition to the validity area, the incompatibility definition can determine how the rule is enforced in both manual and automatic planning by defining the reaction to a positive test. A user defines two conditions and their respective values at the core of the incompatibility.



Incom patibility Settings

Transportation planning profiles specify when the system allows incompatibilities to be violated during manual planning, in VSR optimization, or in background processing. Incompatibility settings are assigned within these profiles. The incompatibility settings group together several incompatibility definitions that may apply to a planning run. Only incompatibilities for the same incompatibility area can be combined. Incompatibility settings can be maintained in planning profiles, carrier selection settings, delivery profiles, and the freight unit building rule.



Unit 9 Exercise 25 Create Incompatibility for Transportation Groups

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create an incompatibility for transportation groups required for transportation planning. 1. In NWBC, create a condition based on the transportation group of the freight unit using the BRFplus Decision Table. Use the following data: Field

Value

Condition

INC_FU_TGRP-##

Description

Transportation Group for ##

Condition Type

/SCMTMS/INC_FU

Origin of Condition


Data Access Definition for Condition screen area

/SCMTMS/T0R_TRAN_GR

2. On the New Condition Definition screen, insert four new rows. Edit the rows in theTable Contents screen area using the dropdown menus. Use the direct value input to enter the following data:

0

Column

Field

Transportation Group

0003 Container

Eval. Result

YES

Column

Field


0002 In Liquid Form

Ev Result

YES

Column

Field


0001 On pallets



Column

Field

Ev Result

YES

Column

Field


*

Ev Result

NO

3. Create another condition selection based on the means of transport for the vehicle resource using a BRFplus Decision Table. Use the following data:______________________________ Field

Value

Condition

INC_VRES_MOT_TC##

Description

Vehicles ##

Condition Type

/SCMTMS/INC_VEHICLE

Origin of Condition



/SCMTMS/VEH_RES_MTR

4. On the New Condition Definition screen, insert two new rows. Edit the rows in the Table Contents screen area using the dropdown menus. Use the following data: Field

Value

Vehicle Resource Means Group

FTL-##

Ev Result

YES

Field

Value


LTL-##

Ev Result

NO

5. Create an incompatibility between the transportation group and the MOT. Use the following data: Field

Value

Incompatibility

INC##_TGRP_0001

Description

FU MOT Incompatibility for Group ##

Incompatibility area

01

Incompatibility type

04



Field

Value

First condition

INC_FU_TGRP-##

Relevant condition result

YES

Second condition

INC_VRES_MOT_TC##


NO

6. Create incompatibility settings for an incompatibility area with the new incompatibility. Do not change the Violation in Manual or Automatic planning. Use the following data:_____________ Field

Value

Incompatibility settings

GEN_INC_##

Description

GR## INC Settings


Complete to VSR (VSR Opt. and Man. Ping and T)

Incompatibility Selection screen area, Incom patibility column

INC##_TRGP_0001



Unit 9 Solution 25 Create Incompatibility for Transportation Groups

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create an incompatibility for transportation groups required for transportation planning. 1. In NWBC, create a condition based on the transportation group of the freight unit using the BRFplus Decision Table. Use the following data: Field

Value

Condition

INC_FU_TGRP-##

Description

Transportation Group for ##

Condition Type

/SCMTMS/INC_FU

Origin of Condition



/SCMTMS/T0R_TRAN_GR

a) Choose Application Administration —>General Settings —> Conditions —> Create Condition. b) Enter the data from the table and continue. c) Choose Data Access Definition, d) Choose Create. e) Enter the Data Access Definition for Condition using the input help. f) Go back to the New Condition Definition screen. 2. On the New Condition Definition screen, insert four new rows. Edit the rows in theTable Contents screen area using the dropdown menus. Use the direct value input to enter the following data: Column

Field


0003 Container

Eval. Result

YES



Column

Field


0002 In Liquid Form

Ev Result

YES

Column

Field


0001 On pallets

Ev Result

YES

Column

Field


*

Ev Result

NO

a) Choose [■ ^ Insert New Row b) Enter the data from the first table c) Repeat steps a-b to create four rows with the data from the tables. d) Save your data. 3. Create another condition selection based on the means of transport for the vehicle resource using a BRFplus Decision Table. Use the following data: Field

Value

Condition

INC_VRES_MOT_TC##

Description

V e h ic le s ##

Condition Type

/ SCMTMS/ INC_VEHICLE

Origin of Condition



/ SCMTMS/ VEH_RES_MTR

a) Choose Application Administration —>General Settings —*■ Conditions —*■ Create Condition. b) Enter the data from the table and continue. c) Choose Data Access Definition. d) Choose Create. e) Enter the Data Access Definition for Condition, using the input help. f) Go back to the Create Definition Condition screen.



4. On the New Condition Definition screen, insert two new rows. Edit the rows in the Table Contents screen area using the dropdown menus. Use the following data: Field

Value


FTL-##

Ev Result

YES

Field

Value


LTL-##

Ev Result

NO

a) Choose [^ /n s e rf New Row b) Enter the data from the first table. c) Repeat steps a-b to create another row with the data from the second table. d) Save your data. 5. Create an incompatibility between the transportation group and the MOT. Use the following data: Field

Value

Incompatibility

INC##_TGRP_0001

Description

FU MOT Incompatibility for Group ##


01

Incompatibility type

04

First condition

INC_FU_TGRP-##


YES

Second condition

INC_VRES_MOT_TC##


NO

a) Choose Application Administration —*■Planning —> General Settings —*■ Incompatibility Definitions —> Create Incompatibility. b) Enter the data from the table. c) Save your data. 6. Create incompatibility settings for an incompatibility area with the new incompatibility. Do not change the Violation in Manual or Automatic planning. Use the following data:



Field

Value

Incompatibility settings

GEN_INC_##

Description

GR## INC Settings


Complete to VSR (VSR Opt. and Man. Ping and T)

Incompatibility Selection screen area, Incom patibility column

INC##_TRGP_0001

a) Choose Application Administration —> Planning —> General Settings —> Incompatibility Settings —► Create Incompatibility Settings. b) Enter the data from the table and choose Insert. c) Save your data.





•


•




Unit 9

Learning Assessment

1. How are input values for a condition determined? Choose the correct answers. | A Using direct business object access B Using the data crawler | C Using a determination class D Using a process controller strategy 2. Where can incompatibilities be used in SAP Transportation Management? Choose the correct answers. | A Freight unit building B Delivery proposal creation C Organizational unit determination D Selection profiles 3. Only incompatibilities for the same incompatibility area can be combined. Determine whether this statement is true or false. | True False




1. How are input values for a condition determined? Choose the correct answers.

|~xj

A Using direct business object access

|~xj

B Using the data crawler

|~xj

C Using a determination class D Using a process controller strategy

That is correct. Input values for a condition are determined by data access definitions based on either direct business object access, the data crawler, or a determination class. 2. Where can incompatibilities be used in SAP Transportation Management? Choose the correct answers.

|~xj

A Freight unit building

|~xj

B Delivery proposal creation C Organizational unit determination D Selection profiles

That is correct. Incompatibilities can be used during freight unit building and delivery proposal creation. 3. Only incompatibilities for the same incompatibility area can be combined. Determine whether this statement is true or false. 0

True False

Correct. Only incompatibilities for the same incompatibility area can be combined.



UNIT 10

Transportation Planning Preparation

Lesson 1

Examining Optimizer Planning Exercise 26: Create Freight Order Types

399 403

Lesson 2

Defining Selection Profiles Exercise 27: Create Selection Profiles and Sub Profiles

411 417

Lesson 3

Creating Planning Profiles Exercise 28: Create a Planning Profile

424 429

Lesson 4

Creating Capacity Selection Settings Exercise 29: Create a Capacity Selection Profile

436 437

UNIT OBJECTIVES

•

Analyze the transportation planning process in SAP TM

•

Examine optimizer planning

•

Define selection profiles

•

Create a geographical selection profile

•

Create time selection profiles

•

Create additional selection profiles

•

Examine planning profiles

•

Examine planning strategies

•

Create a strategy



•

Create capacity selection settings



Unit 10 Lesson 1 Examining Optimizer Planning

LESSON OVERVIEW Your transportation network is now built and integration is configured. In this lesson, you will examine how planning is done in SAP with the optimizer. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


The Transportation Planning Process SAP ERP

i

Sales Order / Purchase Order r

J. Order-based Transportation Requirement

Delivery

Forwarding Quotation

— ------------ 1 ------------ 1 Delivery-based Transportation Requirement

Forwarding Order

Capacities Execution / Subcontr.

Transportation Network Agreement


Calculation Sheet Rate Table



Accounting Document SAP ERP

Figure 167: SAP TM Document Flow



The figure shows that the transportation planning process has several stages. You already designed your transportation network and integrated your ERP system. As a result of integration, order-based transportation requirements are created and freight units are generated. The next stage is to create the freight order that represents a single shipment or load departing from one of your facilities. The freight order can be created manually or using the vehicle scheduling and routing optimizer. Freight O rder Creation

The figure demonstrates the process of building freight orders via a planning process. Freight units are the input to the planning process and freight orders are its output. Several freight units can be consolidated in one freight order if the VSR optimizer evaluates it is cheaper to do so. Building Freight Orders Manually

Use the Freight Order Management component in SAP TM to create and edit freight orders and freight bookings. Freight orders are used for land transportation and freight bookings are used for sea and air transportation. The freight order's execution is planned by a carrier or the shipper. The freight order contains the following: •

Plan for the logistical processing: when and onto which vehicle freight units are to be loaded

•

Planned departure times for the vehicle

•

Execution data

You use freight orders for land transportation. You define the most important settings for the freight order in the freight order type. Freight Order Structure

Freight orders contain the following information: •

Planning information

•

Business partner

•

Locations and dates and times

•

The document flow



•

Transportation charges and cost distribution

•

Logistical dependencies

•

Cargo

•

Execution information, for example, actual departure times

•

Output management, for example, print documents

•

Customs-relevant information

•

Information about transportation stages, for example, durations and distances

•

Status information

•

Subcontracting information, for example, carriers and their prices as well as tendering information

Use the business documents in freight order management to enter all the information required for transportation planning and execution, such as source and destination locations, dates and times, product information, and resources. Freight Order Types

The freight order type determines how a freight order is processed in SAP TM and allows for various parameters to support this process: •

Define number range intervals

•

Define subcontracting relevance

•

Define how consignee and shipper are determined

•

Define if the freight order is to be fixed during saving

•

Define if the freight order can be deleted or only canceled

•

Define sequence type of stops

If freight orders are created during planning and have associated settings in the planning profile, the system determines the freight order type according to the Customizing settings.





Unit 10 Exercise 26 Create Freight Order Types

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure the transportation order (TOR) type needed for planning in SAP TM. 1. In Customizing for SAP TM, view the number range used in transportation order type (TO) definition. 2. In Customizing for SAP TM, create freight order (TOR) type TM ##. The freight order can be deleted, propagate execution info, use BW relevance, enable settlement, enable charge calculation, and track changes. Use the following data: Field

Value

Freight Order Type Description

TM## GR## Freight Order

Freight Order Can Be Subcontracted

Relevant for Subcontracting

Shipper/Consignee Determination

Determination Based on Predecessor Docu ments

Sequence Type of Stops

Defined and Linear

Time For Drawing

Draw Number When Saving Document


05

Weight

US Pound

Volume

Cubic Yard

Default FSD Type



DEF_CHACO

Execution Track. Relev

Execution Tracking with External Event Man ager

Application Object Type

ODT30_TO

Transportation Mode

01- Road

Output Profile Add. Output Profile

/SCMTMS/TOR /SCMTMS/TOR_PRINT_ROAD

Document Creation Relevance

Shipment Creation in SAP ERP



0

Field

Value

Purchasing Org

50000808

Purchasing Group

50000810



Unit 10 Solution 26 Create Freight Order Types

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to configure the transportation order (TOR) type needed for planning in SAP TM. 1. In Customizing for SAP TM, view the number range used in transportation order type (TO) definition. a) Choose SAP Transportation Management —► Transportation Management —> Freight Order Management —► Define Number Range Intervals for Freight Order Management b) Choose

Execute

c) To show the number range groups used, choose <^> Intervals. d) Note the available objects for assignment later to TOR type. e) Choose © Exit 2. In Customizing for SAP TM, create freight order (TOR) type TM ##. The freight order can be deleted, propagate execution info, use BW relevance, enable settlement, enable charge calculation, and track changes. Use the following data:

0

Field

Value

Freight Order Type

TM##

Description

GR## Freight Order

Freight Order Can Be Subcontracted

Relevant for Subcontracting

Shipper/Consignee Determination

Determination Based on Predecessor Docu ments

Sequence Type of Stops

Defined and Linear

Time For Drawing

Draw Number When Saving Document


05

Weight

US Pound

Volume

Cubic Yard

Default FSD Type



DEF_CHACO



Field

Value

Execution Track. Relev

Execution Tracking with External Event Man ager

Application Object Type

ODT30_TO

Transportation Mode

01- Road

Output Profile

/SCMTMS/TOR

Add. Output Profile

/SCMTMS/TOR_PRINT_ROAD

Document Creation Relevance

Shipment Creation in SAP ERP

Purchasing Org

50000808

Purchasing Group

50000810

a) Choose SAP Transportation Management —*■ Transportation Management —> Freight Order Management —*■ Freight Order —> Define Freight Order Types b) Choose

Execute

c) Choose New Entries d) Enter the data from the table. e) Select the required checkboxes. f) Save your data and exit the screen.

0



Optimizer Planning

The problem of the Traveling Sales Person: Detecting the shortest way that connects a number of locations.

The traveling sales person problem belongs to a group of computational problems that cannot be solved optimally in a reasonable time (NP-complete problems). The vehicle scheduling problem in TM is a generalization of the traveling sales person problem. An algorithm uses search strategies to find the best solution for a given runtime. Optimizer Planning Objectives Goal: Determine a transportation plan that minimizes total costs and satisfies all constraints. o

Decisions: o

per freight unit: transport or not?

o

per transported freight unit: select path through transportation network (stages)

o

per selected stage: select capacity / vehicle resource

o

per c a p a c ity /v e h ic le resource: o Select relative ordering of activities (= routing) o

o

Assign start time to each activity (= scheduling)

Total costs = sum of: o

Penalty costs (non-delivery, earliness, lateness), and

o

Capacity / vehicle costs (fixed, duration, stops, quantity, distance)

Figure 170: VSR Goals and Objectives

The goal of VSR optimization is to deliver freight units using vehicle resources while adhering to all constraints and minimizing cost. The VSR optimizer reaches its goal by consolidating orders into vehicles and so reducing the overall distance travelled. The VSR optimizer has the following capabilities:



•

Create multi-drop shipments

•

Create multi-pick shipments

•

Use transshipment locations

•

Use the most cost-effective mode and means of transport

•

Use combinations of mode and means of transport

•

Optimize resource utilization

•

Minimize distance

•

Minimize duration

Optimizer Planning Constraints Real-world constraints can be modeled in TM and considered during VSR optimization: •

A handling resource for loading or unloading that can have breaks

•

The transshipment time of an order at a special location can be restricted by a minimum and maximum duration

•

Some incompatibilities between orders, vehicles, transshipment locations, and combinations, may exist

•

You can restrict driving times of vehicles with the scheduling constraints. For example, you can specify that after eight hours of travel, a two hour break is required.

•

Non-delivery/execution penalty

•

Earliness and lateness penalty

•

Fixed cost (per vehicle)

•

Travel-dependent costs such as distance and duration (per vehicle)

•

Load-dependent costs (per vehicle)

•

Sustainability cost like C02 emission (only with BAdl)

Optimizer Performance The VSR optimizer solves the VSR problem using evolutionary local search. This is a populationbased meta-heuristic that borrows selection principles from evolutionary algorithms and relies on local optimization.

0



Costs

<

Phase 2: Non-Improvement Moves

First Solution

/" v

t Solution Runtime Figure 171: VSR Optimizer: Calculation Process

The optimizer tries to solve the problem of the assignment of freight units to vehicles and the determination of a delivery order for each vehicle so that total transportation costs are minimized. It considers several constraints and penalty costs as part of the total transportation cost. When the optimizer starts, the engine calls back to the application for the complete description of the scenario. In this period, the optimizer engine is running and searches for a solution to the optimization problem.



LESSON SU M M AR Y



•




Unit 10 Lesson 2 Defining Selection Profiles

LESSON OVERVIEW

In this lesson, we examine the features that are available for including or restricting transportation requirements and freight units during interactive or background planning. LESSON OBJECTIVES



•


•


•


Selection Profiles Selection profiles are used for various purposes in SAP TM. They can be used to select freight units, freight orders, freight bookings and transportation units.

The selection profile is a user-specific grouping of business documents that is considered during transportation planning. The system takes into account the selection profile you create during interactive planning, VSR optimization, and carrier selection. Selection Attributes



In the selection profile and in the assigned selection attributes, you define which business documents the system is to take into account, as well as the maximum number of documents. You can assign the following selection attributes to a selection profile: •

Time-related selection attributes in which you define the demand horizon

•

Geographical selection attributes in which you define source and destination locations

•

Additional selection attributes in which you define additional attributes for database queries

Geographical Selection Profiles The geographical profile distinguishes which source and destination locations are relevant for freight unit selection. Geographical Selection Profile

Source Locations

Source Zones

Destination Locations

Destination Zones

Figure 173: Geographical Selection Profiles

The geographical profile is split into four sections: •

Source Locations

•

Source Transportation Zones

•

Destination Locations

•

Destination Transportation Zones

Within each section, you define an inclusive or exclusive set of location values that determine which freight units are relevant for planning. Each section allows users to define specific values or ranges of values, using the logical greater than, less than, or not equal to, to provide precise selection for planning. Geographical Restrictions Within each section, you define an inclusive or exclusive set of location values that determine which freight units are relevant for planning. Each section allows users to define specific values or ranges of values, using the logical of greater than, less than, or not equal to, to provide precise selection for planning. Time Selection Profiles Freight units are selected based on the dates and times they were originally scheduled to be picked up (loading start) and delivered. Freight Unit Selection Freight unit selection can depend on pick-up windows, delivery windows or both. In the timerelated selection attributes, you define how pick-up and delivery time windows are combined.



Combination with AND A freight unit item is selected if at least one time element of the pick-up time window (for example, the start of the requested pick-up date) falls into the pick-up time window and at least one time element of the delivery time window (for example, the end of the acceptable delivery date) falls into the delivery time window. Combination with OR A freight unit item is selected if at least one time element of the pick-up time window (for example, the start of the requested pick-up date) falls into the pick-up time window or at least one time element of the delivery time window (for example, the end of the acceptable delivery date) falls into the delivery time window. Comb. Pick-Up Wind, with See Loc., Del. Wind, with Dst. Loc The Comb. Pick-Up Wind, with See Loc., Del. Wind, with Dst. Loc setting leads to a combination of the query settings for the time window and the geographical selection. A freight unit item is selected if the pick-up window lies within the planning horizon at one of the selected loading locations or if the delivery window lies within the planning horizon at one of the selected locations. Planning Horizon Restrictions When executing VSR optimization, the original dates can be used as a selection restriction. In addition to the dates defined in the freight units, conditions defined at OTR creation can influence windows of time that are related to pick-ups and delivery. Today

— ■ ►

/\

Delivery horizon

= Freight Unit = Material Availability Date = Requested Delivery Date

Figure 174: Planning Horizon

You define the demand horizon in the time-related selection attributes that you assign to your selection profile. You can define a demand horizon for pickup and a demand horizon for delivery. The system chooses all freight units and freight orders whose pickup date and time or delivery date and time lies within the relevant demand horizon.



Demand Horizon: Absolute or Relative

You can define the demand horizon as absolute or relative. With absolute time periods, you define the demand horizon precisely by defining a start and end date and a start and end time (calendar date). If using relative times, you do not define the demand horizon with precise dates and times, but specify instead a duration starting from the current date. The system automatically determines the start and end date and the start and end time. If the demand horizon is not to start on the current date, you can define an offset. The relative demand horizon is then defined as follows: •

Start of demand horizon = current date + defined offset. The offset is made up of the offset in days and the additional offset in hours and minutes.

•

End of demand horizon = start of demand horizon + defined duration of demand horizon. The duration of the demand horizon is made up of the duration in days and the additional duration in hours and minutes.

If you specify a factory calendar, the system considers non-working days when calculating the start of the horizon. In this situation, the planning horizon always begins on a working day. Combination with And Delivery horizon

r 1 Days

'----y--- V Offset

— □ ►

5 Days

7 Days

V

Pickup horizon

= Freight Unit R ................► = Material Availability Date = Requested Delivery Date

= Freight Units not in order Selection

Figure 175: Combination of Pick-Up and Delivery Windows (1)

When you define both a pick-up horizon and a delivery horizon, you specify how they can be used in combination: inclusion or exclusion. When the Combination with And method is chosen, a freight unit item is selected based on two conditions: 1. If at least one time element of the pick-up window, such as the start of the requested pick-up date, falls into the pick-up window.



2. If at least one time element of the delivery window, such as the end of the acceptable delivery date, falls into the delivery time window. Combination with Or Delivery horizon

r

/\

■

= Material Availability Date

*■

= Requested Delivery Date

Figure 176: Combination of Pick-Up and Delivery Windows (2) *•

When the Combination with Or method is chosen, a freight unit item is selected based on one of the following two conditions: 1. If at least one time element of the pick-up window, such as the start of the requested pick-up date, falls into the pick-up window. 2. If at least one time element of the delivery window, such as the end of the acceptable delivery date, falls into the delivery time window. Additional Selection Attributes You can restrict the selection by choosing Additional Criteria —► Additional Selection Attributes. Additional Selection Attribute Options

•

•

Option 1: Definition of Additional Attributes for Database Queries -

+ fast

-

- limited to the attributes of a business object

Option 2: Filtering on the Basis of Conditions -

+ flexible

-

- slower





Unit 10 Exercise 27 Create Selection Profiles and Sub Profiles

Business Example

Your business plans large volumes of transportation requirements. To reduce overlap between planners and restrict certain types of business requirements, create several selection profiles to filter requirements and master data for your planning runs. Create the necessary selection profiles and selection profile attributes to support planning in TM (from the transportation cockpit or in the background).

Note: Required: This exercise is dependent on the completion of all exercises in unit three of this course.

1. In NWBC, create a geographical selection attribute for your group. Select both locations. Use the following data: Field

Value

Geographical Sel. Attributes

GEO-## Geographical Attributes for Group

Description

## Source Locations tab: Sign

Inclusive

Source Locations tab: Opf/on

=

Source Locations tab .Lower Value

SP3100

Destination Locations tab: Sign

Inclusive

Destination Locations tab: Option

Within Range

Destination Locations tab: Lower Value

CUST##-11 CUST##-30

Destination Locations tab: Upper Value

2. Create a time-related selection attribute. Select the Round Horizon to Full Days checkbox. Use the following data: Field

Value

Time-Rel. Sel. Attributes

TIME-##

Description

Selection Horizon fo r Group ##



Field

Value

Absolute/Relative Horizon

Use Relative Horizon

Factory Cal. for Offs/Dur. Calc

US

Use Index Time for Selection

Use Index Time of Stop

Comb, of Pick-Up and Delivery Windows

Combination with OR

Pick-Up Days

180

Offset Direction

Future

Offset in Days

0

Delivery in Days

200

Offset Direction

Future

Offset in Days

0

3. Create an additional selection attribute. Use the profile to restrict those freight units whose status is not planned, partially planned, and planned. Field

Value

Additional Sel. Attributes Description

ASEL-## Freight Units ##

Planned Requirements

Include in Selection

Documents Blocked for Planning

Exclude in Selection

Selection Values tab '.Business Object Selection Values tab: Field Name

/SCMTMS/TO PLAN_STATUS_ROOT

Selection Values tab: Sign

Inclusive

Selection Values tab '.Option

Within Range

Selection Values tab:Lower Limit

01 03

Selection Values tab'.Upper Limit

4. Create a selection profile for your group. Use the following data: Field

Value

Selection Profile

SEL-## Selection Profile for ## 200 TIME-## GEO-##

Description Maximum number of selected objects Time-Related Sel. Attributes Geographical Sel. Attributes



Field

Value

Additional Sel. Attributes

ASEL-##



Unit 10 Solution 27 Create Selection Profiles and Sub Profiles

Business Example

Your business plans large volumes of transportation requirements. To reduce overlap between planners and restrict certain types of business requirements, create several selection profiles to filter requirements and master data for your planning runs. Create the necessary selection profiles and selection profile attributes to support planning in TM (from the transportation cockpit or in the background).


1. In NWBC, create a geographical selection attribute for your group. Select both locations. Use the following data: Field

Value

Geographical Set. Attributes

GEO-## Geographical Attributes for Group

Description

## Source Locations tab: Sign

Inclusive

Source Locations tab .Option

=

Source Locations tab:Lower Value

SP3100

Destination Locations tab: Sign

Inclusive

Destination Locations tab: Option

Within Range

Destination Locations tab: Lower Value

CUST##-11 CUST##-30

Destination Locations tab: Upper Value

a) Choose Application Administration —>Planning —> Selection Profile Attributes —> Geographical Selection Attributes —*■ Create Geographical Selection Attributes. b) Select the Both Locations checkbox. c) Enter the data in the Source Locations and Destination Locations tabs from the table. d) Save your data.



2. Create a time-related selection attribute. Select the Round Horizon to Full Days checkbox. Use the following data: Field

Value

Time-Rel. Set. Attributes Description

TIME-## Selection Horizon for Group ##

Absolute/Relative Horizon

Use Relative Horizon


US

Use Index Time for Selection

Use Index Time of Stop

Comb, of Pick-Up and Delivery Windows

Combination with OR

Pick-Up Days

180

Offset Direction

Future

Offset in Days

0

Delivery in Days

200

Offset Direction

Future

Offset in Days

0

a) Choose Application Administration —>Planning —► Selection Profile Attributes —> TimeRelated Selection Attributes —> Create Time-Related Selection Attributes. b) Enter the data from the table. c) Save your data. 3. Create an additional selection attribute. Use the profile to restrict those freight units whose status is not planned, partially planned, and planned. Field

Value


ASEL-##

Description

Freig ht Units ##

Planned Requirements

Include in Selection

Documents Blocked for Planning

Exclude in Selection

Selection Values tab:Sus/ness Object

/ SCMTMS/TO

Selection Values tab: Field Name

PLAN_STATUS_ROOT

Selection Values tab: Sign

Inclusive

Selection Values tab:Opf/on

Within Range

Selection Values tab -.Lower Limit

01



Field

Value

Selection Values tab'.Upper Limit

03

a) Choose Application Administration —>Planning —> Selection Profile Attributes —> Additional Selection Attributes —► Create Additional Selection Attributes. b) In the Selection Values tab, enter the data from the table. c) Save your data. 4. Create a selection profile for your group. Use the following data:_________________ Field

Value

Selection Profile

SEL-##

Description

Selection P ro file fo r ##

Maximum number of selected objects

200

Time-Related Sel. Attributes

TIME-##

Geographical Sel. Attributes

GEO-##


ASEL-##

a) Choose Application Administration —>Planning —> Selection Profiles —> Create Selection Profile. b) Enter the data from the table. c) Save your data.





•


•


•




Unit 10 Lesson 3 Creating Planning Profiles

LESSON OVERVIEW In this lesson, you examine the planning profiles that can be created and used to influence and control the outcome of the optimizer in both interactive and background planning. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


•

Create a strategy

Planning Profiles

When performing interactive or background VSR planning, users must specify a planning profile. During planning, the system considers the settings that you make in the various planning profiles.

Planning Profile

Capacity Selection Settings

Optimizer Settings

Planning Cost Settings

Incompatibility Settings

Carrier Selection Settings

Load Planning Settings

Steps for setup of the planning profile: 1. Create a planning profile. 2. Create capacity selection settings (optional when only using transactional capacity). 3. Create optimizer settings. 4. 5. 6. 7. 8. 9.

Create planning cost settings. Create incompatibility settings (optional). Create carrier selection settings (optional). Create load planning settings. Assign subprofiles to planning profile. Test settings in the transportation cockpit and planning.

Figure 177: Link between Planning Profile and Settings

Sub Profiles

Before optimizer planning, three sub profiles must be defined: •




•

Optimizer Settings

•

Planning Cost Settings

Strategies

The following strategies are defined in the planning profile: •

Manual planning (standard strategy v s r i _ d e f )

•

Scheduling (standard strategy v s s _ d e f )

•

Checks (standard strategy v s r _Ch e c k ).The system checks capacities, incompatibilities, and multiresources, and performs a dangerous goods check.

•

Planning (standard strategies v s r _ d e f and v s r _ i s t e p ).You define this strategy in the optimizer settings.

•

Planning for transportation proposals (standard strategies v s r _ d e f and v s r _1STEP). Y ou define this strategy in the optimizer settings.

Manual Planning Strategy A manual planning strategy is assigned to the planning profile. It controls which planning strategy is used when manual planning is carried out in the transportation cockpit. The following standard planning strategies are provided for manual planning: •

VSRI_1STEP: Interactive Planning and Carrier Selection

•

VSRI_CHK: Interactive Planning Strategy and check

•

VSRI_DEF: Default Interactive Planning Strategy

•

VSRI_SCH: Interactive Planning and Scheduling

Planning Horizons The planning horizon is the time horizon in which freight orders and freight bookings can be created in the transportation cockpit. You define the planning horizon in the planning profile. The planning horizon defines the possible period of time in which the system can schedule transportation activities such as loading and unloading, and transport.



Current Date

1—

End of Planning Horizon (Start of Planning Horizon + Duration)

Start of Planning Horizon (Current Date + Offset)

V'—

_'

Offset

—Y " -

Planning Horizon

H Transportation Activity Figure 178: Demand Horizons

The planning horizon is defined in the planning profile in days, hours, and minutes. The planning horizon starts at the current system time unless an offset is defined in the planning profile. The offset can be defined in both the past and the future. Business Document Determination Rule The business document determination rule defines which document types are used when freight orders and freight bookings are created during planning. The business document determination rule is defined for each planning profile and applies to documents created either manually or by the VSR optimizer. Business Document Type Determination

Freight order types and freight booking types can be determined in 3 ways. This is defined by the business document determination rule: -

The default type defined in customizing is used.

-

The type is defined in the planning profile directly, for example, vehicle resource, booking for air, booking for ocean, and passive vehicle.

-

The type is defined in a condition with condition type

/ scm tm s/ tor_ ty pe

Scheduling Strategy The schedule strategy defines the actions that are performed when scheduling is launched for a freight order or freight booking in the transportation cockpit. SAP delivers a standard schedule strategy: VSS_DEF. The schedule strategy is assigned to the planning profile. Here, we define if the system considers the dates in the freight unit as constraints and whether a backward or forward scheduling direction is used. The Check Strategy The check strategy defines the actions that are performed when a check is launched for a freight order or freight booking in the transportation cockpit.



SAP delivers a standard strategy: VSR_CHECK. This verifies capacities, incompatibilities, multi resource assignments and performs a dangerous goods check. The check strategy is assigned to the planning profile where we also define if the system should raise an error message, a warning message, or no message at all whenever a vehicle is overloaded. Times for Loading and Unloading This concept examines loading and unloading times. Activities Relevant to Scheduling

•

Loading / Pick-up

•

Transportation/Travel

•

Unloading /Delivery

•

Couple

•

Uncouple

Loading / Unloading Times

•

Defined in the planning profile

•

Constant

•

Condition based (FU and MOT dependent)





Unit 10 Exercise 28 Create a Planning Profile

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create a planning profile to be used during transportation planning. 1. In NWBC, create optimizer settings for your group using the following data: Field

Value

Optimizer Settings

OPT-##

Description

Optimizer Setting for Group ##

Planning Strategy

VSR_DEF

FO Building Rule

New Freight Order When Resource is Empty

Accept Transp. Prop

Save Route and Freight Documents

Planning Strategy for Transp. Prop

VSR_DEF

Max. No. of Parallel Processes

1

Maximum Run time (seconds)

30

Automatic Runtime Regulation

Not used

Consider Capacities During Optimization

Yes

Rough Planning

Do not use rough planning

Maximum No. of Transshipment Loc

6

2. Create a planning profile for your group. Select the Round Horizon To Full Days checkbox and use the following data: Field

Value

Planning Profile

PLAN-##

Description

Planning Profile for Group ##

Duration in Days

30


US

Time Zone for Rounding the Horizon

CST

Type Determination Rule

Defined per Category in Planning Profile



Field

Value

Default Type for Road FO

TM##

Manual Planning Strategy

VSRI_SCH

Consider Fixing Status

Warning When Changing Fixed Documents

Scheduling Strategy

VSS_DEF

Consider Freight Unit Dates


Scheduling Direction

Backward

Check Strategy

VSR_Check

Take Capacities into Account

Warning

Dependence


Loading/Unloading time

0 0 :10:00

Optimizer Settings

OPT-##



Unit 10 Solution 28 Create a Planning Profile

Business Example ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create a planning profile to be used during transportation planning. 1. In NWBC, create optimizer settings for your group using the following data: Field

Value

Optimizer Settings

OPT-##

Description

Optimizer Setting for Group ##

Planning Strategy

VSR_DEF

FO Building Rule

New Freight Order When Resource is Empty

Accept Transp. Prop

Save Route and Freight Documents

Planning Strategy for Transp. Prop

VSR_DEF

Max. No. of Parallel Processes

1

Maximum Run time (seconds)

30

Automatic Runtime Regulation

Not used

Consider Capacities During Optimization

Yes

Rough Planning

Do not use rough planning

Maximum No. of Transshipment Loc

6

a) Open the Application Administration folder and choose Planning —> Planning Profile Settings —*■ Optimizer Settings —*■ Create Optimizer Settings. b) Enter the data from the table. c) Save your data. 2. Create a planning profile for your group. Select the Round Horizon To Full Days checkbox and use the following data: Field

Value

Planning Profile

PLAN-##

Description

Planning Profile for Group ##



Field

Value

Duration in Days

30


US

Time Zone for Rounding the Horizon

CST

Type Determination Rule

Defined per Category in Planning Profile

Default Type for Road FO

TM##

Manual Planning Strategy

VSRI_SCH

Consider Fixing Status

Warning When Changing Fixed Documents

Scheduling Strategy

VSS_DEF



Scheduling Direction

Backward

Check Strategy

VSR_Check

Take Capacities into Account

Warning

Dependence


Loading/Unloading time

0 0 :10:00

Optimizer Settings

OPT-##

a) In NWBC, open the Application Administration folder and choose Planning —> Planning Profiles —> Create Planning Profile. b) Enter the data from the table. c) Accept the remaining default settings. d) Save your data.



Optimizer Planning Strategies Service (Task)

VSR Strategy (How)

VSR_DEF Methods (What)

-----

10 - Program 1

VSR_PRE

2 0 - Program 2

40 - Program 4

VSR_PRE_DG VSR_OPT VSR_POST

50 - Program 5

VSR DG CHK

3 0 -P ro g ram 3

Figure 179: Optimizer Planning Strategies*•

In SAP TM, many of the activities that make up transportation planning are managed by a tool called the Process Controller. Process Controller The process controller is a framework with which you can define your own strategies, methods, and how your planning process is executed. You can use strategies to define complete processes. By assigning a service, you define the area in which the process is to be used, for example, transportation charge management, freight unit building, or VSR optimization. SAP delivers a number of standard strategies. Methods define the individual process steps of a strategy. You assign a service to each method. Strategies in SAP TM

You use strategies in SAP Transportation Management in the following areas: •

Freight unit building

•

Carrier selection

•

VSR optimization

•

Manual planning

•

Change controller

•

Definition of customer-specific functions

You use planning strategies to define the planning steps that the system is to perform and the sequence in which it is to perform them. Each planning strategy comprises one or more methods that represent the individual planning steps.



The Transportation Plan

VSR optimization generates a transportation plan from the optimization data consisting of planned freight orders. It processes freight orders already available from a previous VSR optimization run or manual planning. VSR optimization inserts the freight units into the transportation plan and modifies these initial solutions by, for example, loading a freight unit on to another capacity or by changing the delivery sequence of a capacity. The optimizer tries to minimize the total costs while adhering to the constraints. At the end of the planning run, VSR optimization returns the best solution found. You can generate multiple alternative transportation proposals for each freight unit. You can then choose to use one of them. SAP delivers the planning strategies VSR_DEF and VSR_1STEP as standard for the optimization. You can use the planning strategy VSR_1STEP to control whether the system is to perform carrier selection immediately after VSR optimization. The results of the VSR optimization run are explained in the explanation tool.




•


•


•

Create a strategy



Unit 10 Lesson 4 Creating Capacity Selection Settings

LESSON OVERVIEW In this lesson you will learn about capacity selection settings and consider the impact of these on transportation planning. LESSON OBJECTIVES After completing this lesson, you will be able to:

•



*

Planning Profile


Optmcer Settings

Planning Costs Settings

I

G e n e ra l D ata Capecty Selection Settngs Description N/etMcle Resources

CAPA_3100_00 Capec«y 3100-00

Container Resources

Transportabcn Mode Description

Schedules

Atmoutes tor Vehcle Resource VEHKXERESJO

Inclusive

Pattern

US-CU-01

VtmCLERESJO

Inclusive

Pattern

US-FTL-01

Figure 180: Capacity Selection Settings

The capacity selection settings define which vehicle resources and schedules are selected for transportation planning. This setting involves selecting the resource capacity in the transportation cockpit. Many fields in the resource can be used for selection. Schedules are also selected based on the criteria defined in the capacity selection settings.



Unit 10 Exercise 29 Create a Capacity Selection Profile

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create a planning profile to be used during transportation planning.


1. In NWBC, create a capacity selection profile. Create two lines in the Vehicle Resources screen area. Use the following data: Field

Value


CAPA-##

Description

Capacity Selection Profile for Group ##

Attributes for Vehicle Resource Selection

MTRTCO062 I (use F4 to search for the selection)

Sign

Inclusive

Option

=

Lower Limit

FTL-##



Sign

Inclusive

Option

=

Lower Limit

LTL-##

2. Assign your capacity selection profile CAPA-## to your planning profile PLAN-##.

0



Unit 10 Solution 29 Create a Capacity Selection Profile

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to create a planning profile to be used during transportation planning.


1. In NWBC, create a capacity selection profile. Create two lines in the Vehicle Resources screen area. Use the following data: Field

Value


CAPA-##

Description

Capacity Selection Profile for Group ##



Sign

Inclusive

Option

=

Lower Limit

FTL-##



Sign

Inclusive

Option

=

Lower Limit

LTL-##

a) Open the Application Administration folder and choose Planning —>Planning Profile Settings —>Capacity Selection Settings —► Create Capacity Selection Settings. b) Use the data in the table to create your selection attributes. c) Save your data.



2. Assign your capacity selection profile CAPA-## to your planning profile PLAN-##. a) Open the Application Administration folder and choose the menu path Planning —► Planning Profiles —> Edit Planning Profile. b) Enter

pl a n

-# #

and choose Continue.

c) In the Profile Assignments screen area, in the Capacity Selection Settings field, enter C A P A -# # .

d) Save your data.




•




Unit 10

Learning Assessment

1. Which of the following do you assign to a selection profile? Choose the correct answers. | A Geographical selection attributes B Capacity selection settings | C Carrier selection settings D Additional selection attributes 2. In the time-related selection attributes, which of the following do you define? Choose the correct answer. | A Source and destination locations B Additional attributes for database queries | C The demand horizon 3. Which of the following do you assign to a planning profile? Choose the correct answers. | A Capacity selection attributes B Geographical selection attributes | C Additional selection attributes D Carrier selection attributes

0



4. In which of the following areas in SAP TM can you use strategies to define the planning steps that the system is to perform and the sequence in which it is to perform them? Choose the correct answers. | A Freight unit building B VSR optimization C Manual planning D Applying calendar resources 5. The capacity selection settings define which vehicle resources are selected for transportation planning. Determine whether this statement is true or false. | True False



Unit 10


1. Which of the following do you assign to a selection profile? Choose the correct answers. [x ] A Geographical selection attributes B Capacity selection settings | C Carrier selection settings [x ] D Additional selection attributes That is correct. You assign geographical selection attributes and additional selection attributes to a selection profile. 2. In the time-related selection attributes, which of the following do you define? Choose the correct answer. | A Source and destination locations B Additional attributes for database queries [x ] C The demand horizon That is correct. You can define the demand horizon in the time-related selection attributes. 3. Which of the following do you assign to a planning profile? Choose the correct answers. [x ] A Capacity selection attributes B Geographical selection attributes | C Additional selection attributes [x ] D Carrier selection attributes That is correct. You can assign capacity selection settings and carrier selection settings to a planning profile.

0



4. In which of the following areas in SAP TM can you use strategies to define the planning steps that the system is to perform and the sequence in which it is to perform them? Choose the correct answers.

|~xj

A Freight unit building

|~xj

B VSR optimization

|~xj

C Manual planning D Applying calendar resources

That is correct. You can use strategies in freight unit building, VSR optimization, manual planning, carrier selection, the definition of customer-specific functions, and in the change controller. 5. The capacity selection settings define which vehicle resources are selected for transportation planning. Determine whether this statement is true or false. [x ] True False That is correct. The capacity selection settings define which vehicle resources are selected for transportation planning.



UNIT 11

Interactive Planning with the Transportation Cockpit

Lesson 1 Customizing the Transportation Cockpit Layout Exercise 30: Create a Profile and Layout Set

446 446 453

Lesson 2 Customizing the Transportation Cockpit Exercise 31: Customize the Transportation Cockpit

458 459

Lesson 3 Performing Interactive Planning Exercise 32: Create Freight Orders Interactively

465 469

Lesson 4 Examining Freight Order Scheduling Exercise 33: Schedule a Freight Order

477 481

UNIT OBJECTIVES

•

Identify profile and layout set usage in the transportation cockpit

•

Create a profile and layout set

•

Identify the settings required to customize the transportation cockpit

•

Create freight orders using drag and drop

•

Create freight orders using the command line

•

Create freight orders using the interactive map

•

Perform interactive planning

•

Identify freight order scheduling options

•

Examine the optimizer planning log



Unit 11 Lesson 1 Customizing the Transportation Cockpit Layout

LESSON OVERVIEW Once your network is defined and integration is enabled, your business can begin transportation planning. In this lesson, you look at the tools that support planning in SAP TM. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Transportation Cockpit Menu bar

Freight Units

Freight Orders Freight Bookings

Vehicle Resources Schedules

Freight Order Details

Figure 181: Transportation Cockpit: Main Screen

Transportation planning, including freight order creation, is conducted in the transportation cockpit. The transportation cockpit is the main Ul for most planning activities. Transportation requirements, resources, and freight orders can all be seen in the transportation cockpit.



Profile and Layout Sets Profile and Layout Sets

»e

Start fKnwg Start PUmat}ai BactyotAd @ Q

J

ijj

Refrwr Stfj.rwrr’l

Dwoxeor Test ArBoetr; order T«tt BuwieaaShires Test Co*tedDfttmroich TMtCvtedtatnv-tfcflVv 2 Test Cr»CShow1 TeitUTScentra**! Test Hann Parrnj Test Mann awn* /OPRTires Test Pw'flj ‘Ccrtsfrirts Teni-r«h
/)>,tro.tPwachitaaofl

Re* Seteoto*Prate PUAFWO PUA.ttC.r PUA_ttC_0t PUA.ttC.09 PUA_fl£C_09_02 PUA.ttC.C7

Rtn*«$Prone PUA.TP

're^lOrae'Seiecsefl Prole (KA.FO

PUA_TP.1t PUA.TP.0t PUA.TP.09 PUA.TP.09 PUA.TP

(KA_ttQ.l1 (KA.ttQ.01 (KA.ttQ.09 (KA_*O_09_»2 (KA.FO.07

PUA.ttC.C6 PUA.ttC.C8

PUA.TP PUA.TP.06

(KA.FO.OI

PUA.CSS.91 PUA.CSS.09 PUA.CSS.99 PUA.CSS.97 PUA.CSS.C6 puA.css.ce

PUA.ttC.OS PUA.ttC.0l PUA.ttC.B2

PUA.TP.02 PUA.TP PUA.TP PUA.TP

(KA.FO (KA.FQ.0J

PUA.CSS.95 PUA.CSS.9A41 PUA.CS5.92 PUA.CSS.83

PUA_ttC_C3

The profiles allow control on a granular level: • Requirement selection • Capacity selection • Planning settings

CapaotySeteoto*Sears* PUA.CSS

rcarpUMy Searjs

T»»WliW CoctptUyout PUAUywl StandardUyeu: PUALayout PUAUyOUl PUALayout StandardUyeut StandardLay*** PUA9| tom StandardLayeut PUAUywl StandardUyau! StandardUyeu!

Typically, profiles are set up by planning scenario: • Plan main-leg for time-critical requirements from Europe to US • Plan all LTL from plant to Nordic countries • Plan on-carriage from distribution center to customers using own fleet

Figure 182: Transportation Cockpit Profiles

You use this function to define a profile that you use to enter a planning area. You can also define the layout of the corresponding user interface in this set. Profile and layout sets are used to distinguish between different planning areas or functions. One profile and layout set can be assigned as the default. In the transportation cockpit, you can change the set you want to use by choosing the Change Profile Selection button. Alternatively, go back to the profile selection screen. You use this function in carrier selection when calling the transportation cockpit, and in the creation of delivery proposals. Layout Sets

The following are examples of different layout sets: •

A set for a planner who plans the next day

•

A set for a dispatcher who makes the planning changes for today

•

A set for an air and ocean planner

•

A set for carrier selection

•

A set for each area planner per country or region



Transportation C ockpit Screen Areas

S\

Requirements Area Requirem ent Groups Area

Freight Units / Freight Unit Stages

•

Transportation Units Area

T ra ile r/ Railcar / Container Unit

• •

Orders Area Order Details Area

Freight Orders / Bookings (with detail)

Resources Area

Vehicle / TU resources / Schedules

Hierarchies Area

All Hierarchies

G antt Chart Area Map Area

Interactive / Visual Planning

Figure 184: Screen Areas for Transportation Cockpit

The different screen areas can be combined into different layouts, displaying the relevant information for the planner in different planning situations. Visual elements like maps and gantt charts help the user to grasp relevant information.



Transportation C ockpit M ap

UTAH 1. S t a r e AOitui

Find Resources Nearby

r m r iO fn o

Stow Otta-to Routt*

Distance UoM:

D tp a / LtgttO R tto v t M«t*srw>a Fr>o TratsconatOfl Dfar>4* Metre j

KM

la F t

Frj R tC v Cft S ta rt, *

O

X

50 000

•Distance

Stow S W f U M Routtt

-“ W

□

©

O tar Am k s s S t a r e

OK

P tra c tttf t

Cancel

FCWIiCXtCO

Context-based planning Search Address Cear Address Search ShowDeta ed Routes Show StragM-L ne Routes Dspay Legend Remove Hghfeghtmg Frd Trarsportator De-ands Nearby F rd Resources Nearby

Find Transportation D em ands Nearby •Ontanct

□

X

5 000 km

|

t c w io u c o

xnix |y t= v/Tuceoa _ 0 ___ L . l

Figure 185: Visual Planning: Map

The map can be displayed as one screen area in the transportation cockpit or in full screen. However, having the map displayed as one screen area enables the planner to directly see the selected freight units, freight orders or bookings, transportation units, and resources on the map. The map can show multiple objects at the same time. In order to display selected objects on the map, the map needs to be updated choosing Update Map —*• Selected Entries Only or All. As with all screen areas, the map area can be maximized to use it in full screen mode as well. The map can also be used to find objects, such as resources or transportation demands (i.e. freight units and transportation units). The planner can right click on a position on the map and choose either Find Transportation Demands Nearby or Find Resources Nearby from the context menu. In both cases the planner needs to specify a radius for the search. After confirming the popup, the results are displayed on the map.

Note: Please note that only resources are displayed that were selected with the capacity selection settings, or with search criteria, prior to entering the transportation cockpit. Resources that were not selected into the transportation cockpit are not displayed, even though they might be within the search radius. The same applies to the transportation demands. Only transportation units and freight units are displayed that were previously selected into the transportation cockpit.

G antt C hart

Table 4: Visual Planning: Gantt Chart Visibility

Interactivity



•

Usage of trucks and trailers

•

Load utilization of trucks and trailers

•

Downtimes and nonworking times

•

Execution status and reported times for freight orders, trailer units, and their activities

•

•

Assign and schedule trucks and trailers by drag and drop

•

Re-sequencing by drag and drop

•

Fix and unfix freight orders, trailer units, and their activities

•

Context menus and hyperlinks

Notifications for overload, empty movements, and time conflicts

Usability and Flexibility

Planning Scenarios

•

Time zoom in and out

•

•

Aggregated and detailed view

Truck planning (freight orders and truck resources)

•

Hierarchical views

•

Truck and trailer planning (trailer units and trailer resources)

•

Single and dual view (horizontal and verti cal)

•

Re-planning based on events from execu tion

G a n tt C h a rt: T ra n s p o rta tio n C o c k p it

When performing transportation planning, a planner usually considers two main aspects: availability of resources and utilization of the used resources. With the conventional use of the transportation cockpit, the sequential order of freight orders using a particular resource, and the availability of a resource for a certain timeframe, is not (graphically) shown. Using a Gantt chart, which is often used in project planning as well, helps to visualize the availability of resources and the sequential order of transports. The Gantt chart is fully integrated into the transportation cockpit. In the Gantt chart, freight orders and vehicle resources are displayed as a time bar and planners can manually plan transports by using drag and drop. The Gantt chart is a screen area in the transportation cockpit which can be enabled in a page layout for transportation cockpits. All standard functionalities, like positioning the Gantt chart anywhere on the transportation cockpit or maximizing the screen area to full screen, are available for the Gantt chart too. A zoom bar on top of the screen area can zoom in and out to see a more detailed view of a day or week, or a more general view of the year. An important factor for transportation planning is the utilization of a vehicle. The utilization of the vehicle can be displayed with the utilization view, which can be enabled when needed. The utilization view shows the utilization of the vehicle over time in a graph. The graph is displayed in a detail line below the actual resource or document. In this case, the single-view is chosen. This enables the user to see all of the execution information within one screen. Multiple loading acts are only displayed as one item in the Gantt chart. This keeps the chart clean and easy to understand.



Drag and Drop Functionalities

•

Change relative stop sequence of a freight order or transportation unit.

•

Reassign stop to a different vehicle, freight order, or transportation unit.

•

Reschedule a freight order or transportation unit.

•

Assign a freight order or transportation unit to a resource (truck or trailer).

Interactive planning can be performed in the Gantt chart using drag and drop. Unplanned freight orders can be assigned to resources. Likewise, resources can be assigned to freight orders. The freight order is dropped on the time bar of the resource. If the freight order is not dropped at the same date it was originally planned, the date where it was dropped is taken over into the freight order. Scheduling is only performed when requested using the Scheduling button on top of the Gantt chart. The dual-view can be selected to have the unplanned freight orders displayed on top and the available resources below. This enables the user to work with one window to plan freight orders. The dual-view can either be displayed horizontally or vertically. The size of each area can be changed by dragging with the mouse. The Gantt chart enables the panning of unplanned freight orders by dragging on vehicle resources, as well as the creation of transportation units. When dragging and dropping the loading activity of one freight order into the time bar of another freight order, both freight orders are combined. Overlap means the resource was planned multiple times and is therefore not executable. For example, if the trailer is already planned and newly planned in a later step, this would cause an overlap which the user gets displayed as a red line. Similar to the utilization view, an overlap view shows if several documents on a resource overlap. This overlap can be overcome by scheduling the resource. G antt C hart Appearance C ustom ization C ockpit

■

Configurability ♦ Colors schemes & patterns for activities and documents ♦

Fields and field lists

♦

Hierarchies

♦ Views ♦

Cockpit Layout | 1 0...1 Gantt Ch art Areal 1 Customizing 1 Gantt Chart Layout * *

Layouts * 1 _Views F-

* *. Hferarchies" J 1 ... 2 C

Figure 186: Customizing Gantt Chart Appearance

The Gantt chart displays planned and unplanned freight orders and resources in a time bar. The planner can configure which additional sets of information should be displayed next to the time bar. The time bar itself shows the activities planned for the document and resource.



Depending on the layout chosen the planner can use a single view, which only shows planned and unplanned freight orders or resources exclusively, or a dual view that displays two entities next to each other. Similar to the dual view in the transportation cockpit, the dual view in the Gantt chart can be configured vertically or horizontally. The scrollbars of both screen areas can be synchronized. SAP offers comprehensive customizing pre-settings. With these settings, the user can start immediately to work with the system, as he can use the default settings. In customizing, using the IMG path SAP Transportation Management —> Transportation Management —*■ Basic Functions —» Gantt Chart, the Gantt chart can be configured to the planner’s needs. The layout of a Gantt chart can consist of several views. A view describes firstly whether the Gantt chart is single or dual view, and secondly what the hierarchy looks like if a hierarchy is required. The Gantt chart layout can have several views or defined hierarchies assigned. The user can then switch between different views, but only between the views that were assigned to the layout used. The layout is assigned in the page layout of the transportation cockpit. When using hierarchies, information of different documents is displayed in the same table. When using standard columns for the different documents, many columns will be empty. Therefore, a field list can be defined in Customizing. The field list defines columns that should be displayed in the Gantt chart. For a field of the field list it can be defined, which data source should be displayed in this column, depending on the document used. The appearance of the Gantt chart can be customized as well. A color can be defined with its color code. It can then be used in a color scheme. Color schemes can be defined for documents, activities, and resources. Document types and statuses, as well as activity types and statuses, can then be assigned to a color scheme. Furthermore, color schemes can be assigned to the Gantt chart layout.



Create a Profile and Layout Set

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to explain the planning functionalities available in SAP TM to the client's transportation planner. 1. In NWBC, create your page layout (Layout-##) for the transportation cockpit. Select the Activate Command Line checkbox. Leave the Requirements Group Area as not visible. Use the following data: Requirements Area Field

Value

Position of Screen Area

Top Left

Width

100%

Orders Area Field

Value


Middle Right

Width

50%

Order Details Area Field

Value


Bottom Left

Width

100%

Resources Area Field

Value


Middle Left

Width

50%

2. Create a profile and layout set for your group. Use the following data and select the default checkbox:



Field

Value

Selection Profile for FU

SEL-##

Planning Profile

PLAN-##

Selection Profile for FO

SEL-##

Selection Profile (FBs)

SEL-##

Selection Profile (TUs)

SEL-##

Transportation Cockpit Layout

Layout-##

Layout for Planning Result Screen

Standard Layout

Description

C o c k p it La yout f o r Group ##



Create a Profile and Layout Set

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to explain the planning functionalities available in SAP TM to the client's transportation planner. 1. In NWBC, create your page layout (Layout-##) for the transportation cockpit. Select the Activate Command Line checkbox. Leave the Requirements Group Area as not visible. Use the following data: Requirements Area Field

Value


Top Left

Width

100%

Orders Area Field

Value


Middle Right

Width

50%

Order Details Area Field

Value


Bottom Left

Width

100%

Resources Area Field

Value


Middle Left

Width

50%

a) Application Administration —>Planning —> General Settings —> Page Layouts —> Page Layouts for Transportation Cockpit. b) Choose New.



c) Enter the following data: Field

Value

Page Layout

Layout-##

Validity

User

User

Activate Command Line

Select

d) Review the Visibility options. Do not deselect any of these checkboxes. e) Enter the data from the tables in the Requirements Area tab and do not make any other changes. f) Enter the data in the Orders Area tab and do not make any other changes. g) Enter the data in the Order Details Area tab and do not make any other changes. h) Enter the data in the Capacities Area tab and do not make any other changes. i) Save your new page layout. 2. Create a profile and layout set for your group. Use the following data and select the default checkbox: Field

Value

Selection Profile for FU

SEL-##

Planning Profile

PLAN-##

Selection Profile for FO

SEL-##


SEL-##


SEL-##

Transportation Cockpit Layout

Layout-##

Layout for Planning Result Screen

Standard Layout

Description

Cockpit Layout fo r Group ##

a) Open the Planning folder and choose Planning —> Transportation Cockpit. b) Choose Change Profile Selection —► Profile Selection Screen. This step is only required if you have entered and saved one selection before. c) Choose New. d) Enter the data from the table to create your profile and layout set. e) Save your data. f) Select your profile and layout set and choose Continue to go to the cockpit.




•


•




Unit 11 Lesson 2 Customizing the Transportation Cockpit

LESSON OVERVIEW To support your planning needs, you can change the layout of your transportation cockpit. In this lesson, we examine the settings available to customize the transportation cockpit in SAP TM. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


Customization Settings for the Transportation Cockpit The following changes can be made to the layout of the transportation cockpit: •

The time zone in which to present time-related information

•

Unit for distance

•

The position and width of the tabs on screen

•

The visibility of tabs

•

The sequence and number of rows and columns visible

You can change the layout to suit your requirements by choosing the Page Layout button. For example, you can change to a layout that displays the command line and so allows command line planning.



Customize the Transportation Cockpit

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, wants to personalize the transportation cockpit to suit her requirements for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Create a Profile and Layout Set.

1. In NWBC, enter the transportation cockpit with your selection profile for FOs, FBs, TUs and FUs and your planning profile. Use the following data: Field

Value

Selection Profile (FOs)

SEL-##


SEL-##

Selection Profile (FUs)

SEL-##


SEL-##

Planning Profile

PLAN-##

2. Personalize your transportation cockpit layout by changing the displayed distance unit from KM to Ml using the following data: Field

Value

Individual Unit radio button

Select

Individual Unit

MI

3. Personalize the Freight Unit Stages screen area. Add the Original Order, Original Delivery, and Index from the Available Columns to the Displayed Columns. Choose to Display this View on Open. Save as fu -## stages. 4. Personalize the Vehicles screen area. Add the Index from the Available Columns to the Displayed columns. Choose to Display this View on Open. Save as Vehicles-##.



5. Personalize the Freight Orders/Freight Bookings screen area. Add the Index and carrier description from the Available Columns to the Displayed Columns. Choose to Display this View on Open. Save as FreightOrders-##. 6. Rearrange the size of the screen elements to fit your screen. 7. Maximize the Vehicles screen area to review details about the selected vehicles. What is the maximum weight of vehicles resources FTL-## and LTL-##? Return to your cockpit layout.

8. Export the content of the vehicles area to a spreadsheet. 9. Show the large map in the transportation cockpit with all objects. Why does your vehicle resource appear in the Atlantic ocean to the south-west of Africa?



Customize the Transportation Cockpit

Business Example ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, wants to personalize the transportation cockpit to suit her requirements for transportation planning.

Note: Required: This exercise is dependent on the completion of the exercise Create a Profile and Layout Set.

1. In NWBC, enter the transportation cockpit with your selection profile for FOs, FBs, TUs and FUs and your planning profile. Use the following data: Field

Value

Selection Profile (FOs)

SEL-##


SEL-##

Selection Profile (FUs)

SEL-##


SEL-##

Planning Profile

PLAN-##

a) Choose Planning —>Planning —> Transportation Cockpit. b) Select the line with your selection profile for freights orders, freight bookings, transportation units and freight units SEL-##, and planning profile PLAN-## and continue. 2. Personalize your transportation cockpit layout by changing the displayed distance unit from KM to Ml using the following data: Field

Value

Individual Unit radio button

Select

Individual Unit

MI

a) In the Main screen area, choose £ * Settings to show the list of available settings.



b) Enter the data from the table. c) Choose OK. 3. Personalize the Freight Unit Stages screen area. Add the Original Order, Original Delivery, and Index from the Available Columns to the Displayed Columns. Choose to Display this View on Open. Save as fu-## stages. a) In the Freight Unit Stages screen area, choose 0 ^ Personalize to show the list of available settings. b) Move Original Order, Original Delivery, and Index from the Available Column to the Displayed Column using the arrows. c) Select the Display this View on Open checkbox. d) Save as fu-##

stages.

e) Save your data. 4. Personalize the Vehicles screen area. Add the Index from the Available Columns to the Displayed columns. Choose to Display this View on Open. Save as Vehicles-##. a) In the Vehicles screen area, choose Ojt, Personalize to show the list of available settings. b) Move Index from the Available Column to the Displayed Column using the arrows. c) Select the Display this View on Open checkbox. d) Save as Vehicles—##. e) Save your data. 5. Personalize the Freight Orders/ Freight Bookings screen area. Add the Index and carrier description from the Available Columns to the Displayed Columns. Choose to Display this View on Open. Save as FreightOrders-##. a) In the Freight Orders/Freight Bookings screen area, choose 0 ^ Personalize to show the list of available settings. b) Move Index and Carrier Description from the Available Column to the Displayed Column using the arrows. c) Select the Display this View on Open checkbox. d) Save a s FreightOrders—##. e) Save your data. 6. Rearrange the size of the screen elements to fit your screen. a) Adjust the screen area using the ellipses button in the center at the bottom of each screen area.



7. Maximize the Vehicles screen area to review details about the selected vehicles. What is the maximum weight of vehicles resources FTL-## and LTL-##? Return to your cockpit layout. The maximum weight of FTL-## is 45000 LB and the maximum weight of LTL-## is 25000 LET__________________________________________________________________________ a) In the Vehicles screen area, choose Maximize. b) Choose Restore. 8. Export the content of the vehicles area to a spreadsheet. a) In the Vehicles screen area, choose Jg] Export to Spreadsheet. b) Review the content of the spreadsheet. c) Close the spreadsheet and return to the transportation cockpit. 9. Show the large map in the transportation cockpit with all objects. Why does your vehicle resource appear in the Atlantic ocean to the south-west of Africa? Because you have not created any data yet, the only objects that are selected are your vehicle resources FTL-## and LTL##. The vehicle resources appear with geoocoordinates of longitude 0 and latitude 0, which is in the Atlantic ocean.______________________________




•




Unit 11 Lesson 3 Performing Interactive Planning

LESSON OVERVIEW In this lesson, you will learn about the interactive planning functions in the transportation cockpit. We will examine the use of drag-and-drop functionality in the creation of freight orders, and consider how the command line enables mouse-free planning of freight orders. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


•


•


Drag-and-Drop Freight O rder Creation

A freight order can be created using the drag-and-drop functionality. Dragging an unplanned freight unit stage to a resource or dragging a resource to an unplanned freight unit stage creates a freight order. Changes to existing documents can also be made using drag-and-drop. It is possible to drag additional freight unit stages to a freight order. With SAP 9.0, you can assign freight units from one freight document to another. Freight Order Creation in the Transportation Cockpit The transportation cockpit in SAP TM allows freight order creation in four different modes: •

Optimized planning in the foreground with or without a selection

•

Manual planning with drag and drop or with command line entries

•

Map-based manual planning

•

Transportation proposals for a limited number of multi-leg or multimodal transport demands

Optimized planning can also be scheduled with a background job. Choose Application Administration —>Background Reports-> Background Planning. Updates to Planning SAP TM offers updates to planning with: •

Rescheduling to postpone stages if the first stage is late.



•

Re-planning subsequent stages that did not yet trigger the execution of freight units.

•

Changes based on change controller actions. These actions are triggered based on weight, volume, time, reported execution information, and other changes.

•

Optimized re-planning to add additional transportation demands. You can make changes to a freight order and freight booking.

Command Line Freight Order Creation The command line enables mouse-free planning and is an alternative to drag-and-drop planning. Using the command line, the planner instructs the system to assign freight unit stages to vehicles via a single character string. To enable command line planning, an index is assigned to each resource and freight unit stage. The index acts as a unique identifier for every object in the transportation cockpit. Note that vehicle resources are assigned low numbers so that the planner can easily remember them. Planning with the Command Line

When planning with the command line, the planner first enters index numbers that represent the freight unit stages, followed by a dash (-) and a vehicle resource index. Press ENTER, and a freight order is created with the relevant stages and resource assigned. Multiple commands can be specified in one string by using a plus (+) sign to separate them. Example: Simple Planning of Freight Units on a Vehicle Resource

The freight units that you want to plan have the indexes 5, 6, and 7. The vehicle resource that you want to use to transport the freight units has an index of 2. To assign the freight units to the vehicle resource, you enter the following command in the command line:5 6 7 — 2. Prerequisites

The following are prerequisites for using command line planning: •

The display of the command line must be activated for the page layout for the transportation cockpit.

•

The index field should be displayed for the freight unit stages and vehicles in the transportation cockpit

The help field of the command line provides additional information. Choose More Field Help in the context menu for the field by clicking the right mouse button. Command Line Layout



Transportation Cockpit Menu bar Command line

Freight Units (incl. index numbers)

Vehicle Resources Schedules (incl. index numbers)

Freight Orders Freight Bookings (incl. index numbers)

Freight Order Details

Figure 187: Transportation Cockpit Command Line Layout

The figure shows the command line in the transportation cockpit. Interactive Map Freight Order Creation Freight orders can be created using the interactive map. Freight unit stages and vehicles are both displayed on the map. You can carry out your planning activities on the map. If you select Unplanned Freight Units and Start Planning from the context menu, for example, the system shows the possible assignments of the freight units to the resources. Select the assignments that you require. You can also assign unplanned freight units or multirelations that contain unplanned freight units to resources by using drag and drop. When you do so, you can either assign the freight units to the resource or the resource to the freight units. If you want to split a stage that is displayed on the map, you can assign an unplanned freight unit or multirelation to a location using drag and drop. Once you have selected the required planning option, the system adds the selected location to the freight unit stage and updates the map accordingly. This process also applies to freight orders. You can also display transshipment locations that are not part of your planning activities. You display these locations by choosing Show Related Transshipment Locations from the context menu. If a freight order does not have a vehicle assigned to it, you can also assign the vehicle using drag and drop. To do so, you assign the freight order to a single vehicle resource or a multispot that contains at least one vehicle resource or passive vehicle resource and then select the relevant planning option from the menu. The system displays all of your transportation planning activities on the map. When you leave the full display of the map, your planning activities are also displayed in the table view of the transportation cockpit.



Interactive Updates of Freight Orders Changes can also be made to existing freight orders interactively. Using drag-and-drop, you can drag additional freight unit stages to a freight order. The freight order is updated with the additional freight unit and a stage is added to include the additional stop-off, if required. From the interactive map, you can also drag a freight unit stage to an existing freight order.



Unit 11 Exercise 32 Create Freight Orders Interactively

Business Example

ABC Corporation wants to implement SAP TM to support truck-load and less-than-truck-load planning scenarios. Sue, the SAP consultant, needs to explain the planning functionalities available in SAP TM to the client's transportation planner.

Note: Required: This exercise is dependent on the completion of all exercises in units three and five of this course, and the exercise Customize the Transportation Cockpit.

1. Create several sales orders so that you have data for planning. Take note of the sales order numbers that you create. Use the following data: Field

Value

Order Type

ZT##

Sales Org

3000


10

Division

00

Sold-to Party

CUST##-16 CUST##-17 CUST##-18 CUST##-25 CUST##-26 CUST##-28

PO Number TM200_00

TM200_00 TM200_00

TM200_00 TM200_00

TM200_00

Material

PRODTM-OO PRODTM-OO PRODTM-OO PRODTM-OO PRODTM-OO PRODTM-OO

Quantity

50

50

50

50

50

50

Sales Order Number 2. Create freight units for the order-based transportation requirements created in step 1. 3. To enable map display, you must import a certificate. In SAP TM, enter transaction code WDR_ACF_WLIST. 4. Select the line containing the certificate VB200. 5. Choose Install Certificate and exit the transaction.



6. In NWBC, enter the transportation cockpit with your planning profile and selection profiles for freight units and freight orders. Use your transportation cockpit layout. Use the following data: Field

Value

Selection Profile for Freight Units

SEL-##

Planning Profile

PLAN-##

Selection Profiles for Freight Orders

SEL-##

Selection Profiles for Freight Bookings

SEL-##

Selection Profiles for Transportation Units

SEL-##

Layout

LAYOUT-##

7. Perform manual planning with FTL-## using drag and drop functionality on your freight unit to CUST##-17. 8. Confirm that a freight order with a temporary freight order number has been created in the order area. 9. Review the freight order in the Overview screen area. Can you explain the durations that have been calculated and that are shown?

10. Perform manual planning with FTL-## on your freight unit to CUST##-18 using the command line. Enter the index number of the freight unit to CUST##-18, the character - and the index number of FTL-##. For example, 5-1. 11. Confirm that a freight order has been created in the Freight Orders/ Freight Bookings screen area with a temporary freight order number. 12. Review the freight order in the Overview screen area. Can you explain the durations that have been calculated and that are shown?

13. To perform manual planning using the interactive map, select your freight unit to customer CUST##-16, one of the freight orders to CUST##-17 or CUST##-18 and the vehicles LTL-## and FTL-##. Assign the freight unit to the existing freight order. 14. Can you explain the planning results?



15. Switch to layout PB_LAYOUT and plan freight unit to CUST##-25 on vehicle FTL-## in the Gantt chart screen area after having maximized this area. 16. Remove any overlaps (if they exist for vehicle FTL-##) by dragging and dropping freight orders in the Gantt view. Why are overlaps allowed in this case?



Unit 11 Solution 32 Create Freight Orders Interactively

Business Example


Note: Required: This exercise is dependent on the completion of all exercises in units three and five of this course, and the exercise Customize the Transportation Cockpit.

1. Create several sales orders so that you have data for planning. Take note of the sales order numbers that you create. Use the following data: Field

Value

Order Type

ZT##

Sales Org

3000


10

Division

00

Sold-to Party

CUST##-16 CUST##-17 CUST##-18 CUST##-25 CUST##-26 CUST##-28

PO Number TM200_00

TM200_00 TM200_00

TM200_00 TM200_00

TM200_00

Material

PRODTM-OO PRODTM-OO PRODTM-OO PRODTM-OO PRODTM-OO PRODTM-OO

Quantity

50

50

50

50

50

50

Sales Order Number

a) In SAP ERP, enter transaction code v a o i . b) Enter the data from the first table and continue. c) Enter the data from the second table, saving each time you create a sales order. d) Note your sales order number each time.



2. Create freight units for the order-based transportation requirements created in step 1. a) Go to ERP Logistics Integration —> Worklists —> Overview Transportation Requirements. b) Highlight the rows with the sales orders that you created in step 1. c) Choose Create Freight Units. 3. To enable map display, you must import a certificate. In SAP TM, enter transaction code WDR_AC F_WL1ST. 4. Select the line containing the certificate VB200. 5. Choose Install Certificate and exit the transaction. 6. In NWBC, enter the transportation cockpit with your planning profile and selection profiles for freight units and freight orders. Use your transportation cockpit layout. Use the following data: Field

Value


SEL-##

Planning Profile

PLAN-##


SEL-##


SEL-##


SEL-##

Layout

LAYOUT-##

a) Open the Planning folder and choose Planning —* Transportation Cockpit b) Select your transportation cockpit using the data in the table. c) Choose Continue. 7. Perform manual planning with FTL-## using drag and drop functionality on your freight unit to CUST##-17. a) Select the freight unit to CUST##-17. b) Drag the freight unit to vehicle resource FTL-## and drop the freight unit on the resource. 8. Confirm that a freight order with a temporary freight order number has been created in the order area. a) A freight order with a temporary freight order number has been created on the resource.



9. Review the freight order in the Overview screen area. Can you explain the durations that have been calculated and that are shown? In the Freight Orders/ Freight Bookings screen area, select the temporary freight order. For example, approximately 7.5 hours (1 hour due to time zone CST vs. EST); 6.5 hours due to distance (328 mi) and speed (80km /h approx.. 50. Mph. The duration for loading/unloading is 10 minutes, and each is based on the settings that you have made in the planning profile PLAN-##____________________________________________________________________ 10. Perform manual planning with FTL-## on your freight unit to CUST##-18 using the command line. Enter the index number of the freight unit to CUST##-18, the character - and the index number of FTL-##. For example, 5-1. 11. Confirm that a freight order has been created in the Freight Orders/ Freight Bookings screen area with a temporary freight order number. a) A freight order with a temporary number has been created in the Freight Orders/ Freight Bookings screen area. 12. Review the freight order in the Overview screen area. Can you explain the durations that have been calculated and that are shown? For example, approximately 7.5 hours (1 hour due to time zone CST vs. EST); 6.5 hours due to distance (328 mi) and speed (80km /h approx., 50. Mph) The duration for loading/unloading is 10 minutes each based on the settings that you made in the planning profile PLAN-##.____ 13. To perform manual planning using the interactive map, select your freight unit to customer CUST##-16, one of the freight orders to CUST##-17 or CUST##-18 and the vehicles LTL-## and FTL-##. Assign the freight unit to the existing freight order. a) Select the freight unit to CUST##-16 in the Freight Unit Stages screen area. b) Select the freight order to CUST##-18 in the Freight Unit Stages screen area. c) Select vehicles LTL-## and FTL-## in the Vehicles screen area. d) Choose Show Map —► Selected Entries Only.. e) To show the geography of the selected items in more detail, drill into North America. f) Select the freight unit to CUST##-16 and right-click to display the context menu. g) Select Planning Options. h) Choose One Planning Option. i) Go back to the previous screen.



14. Can you explain the planning results? In the Overview screen area, you will notice that a freight order with two stages has been created. The first stage starts at shipping point SP3100. The stages end at the two customers that are being part of this freight order: CUST##16 and CUST##-18._____________________ a) In the Freight Orders/ Freight Bookings screen area, select your freight order. 15. Switch to layout PB_LAYOUT and plan freight unit to CUST##-25 on vehicle FTL-## in the Gantt chart screen area after having maximized this area. a) In Button Page Layout, select PB_LAYOUT. b) In the Gantt Chart area, choose the Maximize button. c) Select Freight Units and Resources in the Gantt area. d) Highlight freight unit to CUST##-25 and vehicle resources FTL-## and choose Plan Selected Items. 16. Remove any overlaps (if they exist for vehicle FTL-##) by dragging and dropping freight orders in the Gantt view. Why are overlaps allowed in this case? Overlaps are allowed, because FTL-## resources are defined as multi resources. a) In the Trucks and Trailers part of the screen, drag and drop freight orders so that they do not overlap.



LESSON SU M M AR Y



•


•


•




Unit 11 Lesson 4 Examining Freight Order Scheduling

LESSON OVERVIEW In this lesson, you will examine the various options available for freight order scheduling. You will learn about forward and backward scheduling, and explore the scheduling constraints and strategies that must be considered for freight order scheduling.

At the end of this lesson, you will be able to schedule a freight order. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


Scheduling Scheduling determines start and end times for a set of dates and times such as the departure and arrival of a freight order, the pick-up and delivery of the assigned freight units, or the coupling and uncoupling of trailers. In scheduling, the system considers multiple constraints like a predefined relative ordering among the activities of the freight order as well as the pick-up windows and the delivery windows of the assigned freight units. Freight Order Scheduling

The scheduling of freight orders can be initiated in the following ways: •

From the transportation cockpit using the Scheduling button

•

From the freight order user interface using the Scheduling button

•

Automatically, by entering the departure date of a freight order and choosing ENTER on your keyboard (if the user parameter /SCMTMS/SCH_FORCE is active)

Constraints

Scheduling considers the following constraints: •

Time windows for loading and unloading activities for your freight units

•

Appointments for the freight order to which your freight units are assigned

•

Loading and unloading durations of your freight units

•

Location sequence of your freight order

•

Existing freight orders on resources



•

Coupling and uncoupling durations

•

Calendar resources as well as the calendars and capacities for the loading and unloading activities of handling resources

•

Calendars of the involved vehicle resources for loading, unloading, transportation, coupling and uncoupling activities

Forward Scheduling In forward scheduling, the system first defines the start and end time of the first activity to be scheduled. Afterwards, the system assigns start and end times for all succeeding activities.

Freight Unit Freight Order Figure 188: Forward Scheduling

The following example illustrates the use of forward scheduling. Customer A orders 50 pallets of product X and asks for a delivery date in three weeks. Currently, the capacity of your depot is 100 m3. Product X takes up 95 m3 of your depot. Therefore, you decide to move the goods out of your depot as soon as possible in order to minimize your inventory. That is why you decide to use forward scheduling. Backward Scheduling In backward scheduling, the system first defines the start and end time of the last activity to be scheduled. Afterwards, the system assigns start and end times for all preceding activities.

Freight Unit Freight Order Figure 189: Backward Scheduling

Customer B orders 50 pallets of product Y and asks for a delivery date in three weeks. Currently, the capacity of your depot is 100 m3. Product Y takes up 5 m3 of your depot. Therefore, you decide to stick to the delivery time window as closely as possible. That is why you decide to use backward scheduling.



Scheduling Constraints

You can use the scheduling constraints function to consider constraints for scheduling during VSR optimization. This allows VSR optimization to, for example, extend the transportation plans for long trip durations so that a driver can take his required breaks. This function only applies to vehicle resources. For example, a truck requires two days for a trip from the east coast to the west coast of the United States. However, since the driver must take breaks along the way, a longer trip duration must be scheduled. Resource Availability This concept examines resource availability. Resource Availability

Resource availability is considered for the following resources: •

Vehicle resources

•

Calendar resources

•

Handling resources

Resource Availability Considerations

Resource availability considers the following: •

Factory calendar

•

Capacity variants

•

Downtimes

•

Existing activities assigned to the resource



Scheduling Strategies Scheduling strategies are assigned in the planning profile.



Unit 11 Exercise 33 Schedule a Freight Order

Business Example


Note: Required: This exercise is dependent on the completion of the exercise Create Freight Orders Interactively.

1. In NWBC, enter the transportation cockpit with your planning profile and selection profiles for freight units, freight bookings, transportation units and freight orders. Use your transportation cockpit layout. Use the following data: Field

Value


SEL-##

Planning Profile

PLAN-##


SEL-##


SEL-##


SEL-##

Layout

LAYOUT-##

2. Use backward scheduling and manually create a freight order for your freight unit to CUST##-25 with vehicle FTL-##. 3. What is the pick-up date and time (loading time) at SP3100 and what is the delivery date and time (unloading time) at CUST##-25?

4. Use forward scheduling and manually create a freight order for your freight unit to CUST##-25 with vehicle FTL-##.



5. What is the pick-up date and time (loading time) at SP3100 and what is the delivery date and time (unloading time) at CUST##-25? Wh

6. Assign scheduling constraints FLEET to your means of transport FTL-## and use backward scheduling to manually create a freight order for your freight unit to CUST##-25 with vehicle FTL-##. 7. What is the pick-up date and time (loading time) at SP3100 and what is the delivery date and time (unloading time) at CUST##-25? Why is it different now?

8. Can you explain the difference between the backward, forward, and backward with planning constraints planning scenarios?



Unit 11 Solution 33 Schedule a Freight Order

Business Example



1. In NWBC, enter the transportation cockpit with your planning profile and selection profiles for freight units, freight bookings, transportation units and freight orders. Use your transportation cockpit layout. Use the following data: Field

Value


SEL-##

Planning Profile

PLAN-##


SEL-##


SEL-##


SEL-##

Layout

LAYOUT-##

a) Open the Planning folder and choose Planning —> Transportation Cockpit. b) Select your transportation cockpit using the data in the table. c) Choose Continue. 2. Use backward scheduling and manually create a freight order for your freight unit to CUST##-25 with vehicle FTL-##. a) Select the freight unit to customer CUST##-25. b) Select the vehicle resource FTL-##/ c) Choose Plan Selected Items.

0



3. What is the pick-up date and time (loading time) at SP3100 and what is the delivery date and time (unloading time) at CUST##-25? Note your pick-up and delivery times. These will vary._________________________________ a) Highlight the freight order in the Freight Orders/ Freight Bookings screen area and review the exact scheduling in the Overview screen area. 4. Use forward scheduling and manually create a freight order for your freight unit to CUST##-25 with vehicle FTL-##. a) Choose Change Planning Settings. b) Change the scheduling direction from Backward to Forward. c) Choose OK. d) Select the freight unit to customer CUST##-25. e) Select the vehicle resource FTL-##/ f) Choose Plan Selected Items. 5. What is the pick-up date and time (loading time) at SP3100 and what is the delivery date and time (unloading time) at CUST##-25? Wh Note that the pick-up and delivery times vary. It is different now, because in the previous step the scheduling has been done backward from the delivery date and time, while it is done forward from the pick-up date and time in this step.__________________________________ a) Highlight the freight order in the Freight Orders/ Freight Bookings screen area and review the exact scheduling in the Overview screen area. 6. Assign scheduling constraints FLEET to your means of transport FTL-## and use backward scheduling to manually create a freight order for your freight unit to CUST##-25 with vehicle FTL-##. a) In Customizing for TM, choose SAP Transportation Management —>Transportation Management —>Planning —>General Settings —>Define Scheduling Constraints. b) Choose Means-of-Transport Constraints in the navigation pane. c) Choose New Entries. d) Enter the following values: Field

Value

Means of Transport

FTL-##

Constraint Set ID

FLEET



e) Save your data and return to the transportation cockpit. f) Choose £2 Refresh and choose OK in the dialog box. g) Select the freight unit to customer CUST##-25 and the vehicle FTL-## and choose Plan Selected Item. 7. What is the pick-up date and time (loading time) at SP3100 and what is the delivery date and time (unloading time) at CUST##-25? Why is it different now? It is different now because in the previous step the scheduling is forward from the delivery date and time, while in this step, it is backward and considers also scheduling constraints from the pick-up date and time.__________________________________________________ a) Select the freight order in the Freight Orders/ Freight Bookings screen area and review the exact scheduling in the Overview screen area. b) Make a note of the pick-up and delivery times. 8. Can you explain the difference between the backward, forward, and backward with planning constraints planning scenarios? Backward scheduling schedules from the delivery window into the past. Forward scheduling schedules from the pick-up window into the future. When scheduling constraints are considered, the duration for transportation activities is extended by the approximate break time that truck drivers must take.



Optimizer Planning Log You can obtain a detailed overview of the data that flows into the VSR optimization run and the results that are output. In this way, you can quickly and easily recognize how the VSR optimization optimizes the costs. Prerequisite

You set user parameter /SCMTMS/EXP to X to allow for the logging of the optimizer data for optimization runs that you start interactively. The explanation tool for VSR optimization displays the following information: •

Input for the VSR optimization run

•

Results of the VSR optimization run

•

Solution overview

Content of the Optimizer Planning Log / Explanation Protocol Input

•

Freight units

•

Transportation documents

•

Freight bookings

•

Resources

•

Transportation network

•

Incompatibilities

•

Conditions

•

Dimensions

•

Parameters

R esults

Freight units Transportation documents Freight bookings Solution details Resources




•


•






Unit 11

Learning Assessment

1. Detail four changes that can be made to the layout of the transportation cockpit.

2. In the layout of the transportation cockpit, you can change the time zone in which to present time-related information. Determine whether this statement is true or false. | True False 3. How can you create freight orders manually in the transportation cockpit? Choose the correct answers. | A Using drag-and-drop B Using freight unit building rules | C Using command line planning 4. Determine which of the following statements are true: Choose the correct answers. | A Several freight units can be assigned to a freight order. B One freight unit can be assigned to several freight orders. C One freight unit stage can be assigned to multiple freight orders.

0



Unit 11


1. Detail four changes that can be made to the layout of the transportation cockpit. There are five possible changes that can be made to the layout of the transportation cockpit. The time zone in which to present time-related information, the unit of distance, the position and width of the tabs on the screen, the visibility of tabs, and the sequence and number of rows and columns visible can all be changed to suit your requirements.___________________ 2. In the layout of the transportation cockpit, you can change the time zone in which to present time-related information. Determine whether this statement is true or false. [x ] True False That is correct. In the transportation cockpit, you can change the time zone in which to present time-related information. 3. How can you create freight orders manually in the transportation cockpit? Choose the correct answers.

|~xj

A Using drag-and-drop B Using freight unit building rules

|~xj C

Using command line planning

That is correct. You can create freight orders manually using drag-and-drop or using command line planning. Although you can create freight orders using freight building rules, this is an automatic process.

0



4. Determine which of the following statements are true: Choose the correct answers. |~X~| A Several freight units can be assigned to a freight order. [x ] B One freight unit can be assigned to several freight orders. C One freight unit stage can be assigned to multiple freight orders. That is correct. Several freight units can be assigned to a freight order and one freight unit can be assigned to several freight orders. However, each stage of a freight unit can only be assigned to one freight order.





UNIT 12

Carrier Selection

Lesson 1

Performing Carrier Selection Exercise 34: Execute Carrier Selection

494 503

Lesson 2

Tendering Freight Orders Exercise 35: Tender a Freight Order

509 515

UNIT OBJECTIVES

0

•

Define the parameters of the carrier selection process

•

Manage carrier constraints and allocations

•

Edit carrier selection settings

•

Execute carrier selection

•

Describe the freight tendering process

•

Tender a freight order

•

Describe communication methods for tendering



Unit 12 Lesson 1 Performing Carrier Selection

LESSON OVERVIEW Carrier selection is used to determine the right combination of carrier or carrier assignments based on cost, equipment availability, priority, and business share goals. In this lesson, you will learn about assigning suitable carriers to freight orders - either manually or automatically. LESSON OBJECTIVES After completing this lesson, you will be able to:

•


•


•


•


C arrier Selection Process Carrier S e le c tio n ^ !

Execute Carrier Selection

1-step Planning

Check Incompatibilities Determine TCM or Internal Costs

Transportation Allocations

Business Shares

Continuous Move

Build Ranking List

Automatic ^ Assignm ent

L

Manual Assignm ent

Available Carriers

L

Tendering

Figure 191: Carrier Selection Process Flow

Once a freight order has been built, a shipper will need to choose (and communicate with) the business partner responsible for moving the product. We will refer to this as carrier selection.



Carrier selection is used to assign a suitable carrier to your subcontractable business documents (for example, freight orders), either manually or automatically. The aim is to find a carrier with the lowest costs under consideration of the defined constraints. In manual carrier selection, you manually assign the required carrier to your business documents. If you have configured a check against transportation allocations, the system takes this into account and checks transportation capacities (transportation allocations) that you have defined for the individual carriers. If, during the allocation, the system finds relevant transportation allocations without capacity or that certain rules are violated by the allocation, warning messages appear. A separate optimization is available for automatic carrier selection. It takes selected optimization options into account when determining the most cost-effective carrier for all business documents that you have selected. If none of the carriers are available, the system does not assign any carrier to the relevant business documents. Strategy Options

During planning in SAP TM, strategies are defined which are optimization options for carrier selection. The system takes these strategies into account during the automatic carrier selection process. You define strategies either in the transportation lane or in carrier selection settings. Initially, the system considers the appropriate transportation lane for each freight order. This allows it to consider different settings in one run. Taking strategies and settings into consideration, the optimizer then creates a carrier ranking list containing the different carrier options. The strategy options supported are as follows: •

Cost and Priority

•

Business Share

•

Transportation Allocation

•

Continuous Move

Costs and Priorities in C arrier Selection

In carrying out carrier selection, the system can put more weight on priorities or costs. In terms of priority, the system can determine the most favorable carrier based on the priorities you have defined. In effect, this means that the system chooses the carrier with the highest priority, while taking into account the various restrictions that may be in place. Alternatively, the system can determine the carrier on the basis of lowest total cost. Costs in this case can refer to internal costs or to charges calculated in charge management (we will look at this option in a separate lesson). Internal Costs

Internal costs draw on transportation costs and carrier costs as defined for your carriers. For example, you may have defined a transportation cost per business document (freight order, for example), or you could have defined a transportation cost per unit of weight or volume. Carrier costs are typically defined per unit of distance - kms or miles. You define internal costs in the transportation lane or in the carrier profile.



Note: When we speak of internal costs here, we are not speaking of real world costs. Internal costs are used for weighting only, as part of the carrier selection process.

Business Share

Formalised firm relationships often exist with carriers in the form of contracts. These contracts can guarantee an amount of business to be allocated to a carrier which, if not met, would result in penalties. SAP TM has the tools to track these relationships and to divide business appropriately between different carriers. This supports the negotiation of freight agreements, and avoids dependency on a single vendor. The idea is to use a fixed percentage to dictate the assignment of jobs to certain carriers. The system can also take the capacity of a carrier in relation to certain routes or geographical areas into account when generating assignments.

When defining the business share context, you create business share buckets. These define the actual business share a carrier is allowed to have. There are different types of buckets available for business share creation - yearly, quarterly, monthly, weekly, and daily. Business Example

Carrier A has a weekly bucket equating to 75% of the business share on the lane between Hamburg and Frankfurt, between the validity period —01.01.2017 to 31.12.2017. In the same context, carrier B can have a defined weekly bucket of 25%. Penalties

You can define tolerances and penalty costs in relation to business share. As long as the business share for a specific carrier is within the tolerance limits, it does not affect the cost calculations during carrier ranking. Once the share allocation goes beyond a defined level, however, penalties



start to apply. Tolerances are always defined in percentage terms. Penalties are maintained as numeric values. This number (the penalty) is multiplied by the deviation percentage (the amount outside the defined tolerance range) to arrive at the penalty cost. Example

A penalty of 1,000 is defined. An excess tolerance of 10% is also defined. During business share calculation, if the excess is 12%, the excess liable for penalty is 2%. This 2 is multiplied by 1,000 to arrive at the total excess penalty cost of 2,000. Currencies in Penalty Costs

When calculating the total costs for a carrier, if you are working with charge management costs, there will be a currency assigned to the charge management costs. To assign a currency to business share penalty costs, this has to be defined under Carrier Selection Settings —>Advanced Settings —>Common Currency. If you are working with carriers from multiple geographic locations with multiple currencies, to arrive at the correct ranking, the system uses the internal common currency (maintained in the carrier selection settings) for its calculations. The currency displayed in the carrier ranking list is always the local currency of the carrier (the one maintained in the freight agreement). All freight orders in a business share context are selected for the business share penalty calculations, although these freight orders are not selected during the planning run. Business Example

Assume that in a business share context we have two carriers, A & B. No tolerances have been defined. Carrier A is awarded 60% and carrier B 40%. There are already 10 freight orders awarded, of which carrier A is assigned 6 and carrier B is assigned 4. Now let’s perform carrier selection for an 11th freight order. If carrier B is assigned this FO, carrier A will have a shortfall of business share. If the freight order is assigned to carrier A, carrier B will have a shortfall of business shares. Both options are evaluated by the system and ranked according to their suitability. Allocations

Transportation allocations allow companies to assign defined quantities of capacity to certain business partners. This includes set minimum or maximum capacity restrictions that regulate how much business is allowed with a certain carrier in a certain region for a certain means of transport. A separate business object is used to model these allocations.



Carrier 1 allocates 20 trucks/day (capacity)

Location/Zone A to Location/Zone B

Carrier 2 allocates 40 trucks/day (capacity) Figure 193: Transportation Allocation

C arrier Selection M aster Data

Carrier selection can be influenced by settings in the transportation lane. Within the transportation lane, available carriers are defined for each means of transport. The transportation lane selection settings are as follows: •

Business share rules



•

Defined cost origin

•

Logic of carrier selection

Trade lanes may be used to build up a hierarchy that is more generic. Trade lanes imply more specific trade lanes. For example, “within Germany by truck” implies “ From Frankfurt to Hamburg by chilled truck" and “within Bavaria using a truck for liquids” . Trade lanes may also overlap. For example, "from Germany by airplane" and “within Europe by airplane". Trade lane hierarchies include the following elements, and their implications: •

Transportation zone hierarchy. “ From Germany” implies “from Bavaria” , which implies “from plant in Munich” .

•

Means of transport hierarchy. "Within Germany by truck” implies “within Germany by chilled truck".

•

Means of transport - mode of transport relations. "Within Germany by road” implies “within Germany by chilled truck” .

C arrier Selection Settings

Included in optimization is a carrier selection setting. Although some of the same settings are available in the carrier settings on the transportation lane, these settings override settings maintained directly on the lane. The settings in this profile are based on strategies such as lowest cost, business share, or priority. It considers continuous move options and equipment allocations and can tender automatically based on the tendering strategy. The profile also contains more enhanced settings, such as the ability to automatically perform carrier selection after vehicle scheduling and routing. C arrier Selection Ranking

When using automatic carrier selection, the system will create a carrier ranking list of the relevant carriers for a particular shipment. For each relevant carrier, users can see a variety of information that influenced the selection process. This could include the means of transport cost, delivery performance ratings, and others. After automatic carrier selection has been performed, the ranking list will be visible in the freight order.



Continuous Moves

Simple Move

Freight Order 1

Freight Order 2

Carrier 1

Freight Order 2

Round Trip

Carrier 1

Freight Order 1 Figure 197: Continuous Moves

Continuous move scenarios can identify opportunities to avoid empty runs or utilize capacity more effectively. As part of automatic carrier selection, the system tries to combine freight orders by forming continuous moves. The aim is to reduce the costs of the freight order by assigning additional freight orders to the same carrier. The following types of continuous move are available:



•

Simple continuous move: The carrier accepts one or more additional freight orders directly after executing the first freight order.

•

Round trip: The start location of the first freight order and the destination location of the second freight order are identical.

The system cannot take into account complex round trips where multiple source locations (pick up) or destination locations (delivery) are served.





Unit 12 Exercise 34 Execute Carrier Selection

Business Example

You have been asked to investigate the carrier selection process for a typical load between a given origin and destination location.


1. Assign carrier selection setting CSEL_3100_00 to your planning profile. 2. In NWBC, enter the transportation cockpit with your planning profile and selection profiles for freight units, freight bookings, transportation units and freight orders. Use your transportation cockpit layout. Use the following data: Field

Value


SEL-##

Planning Profile

PLAN-##

Selection Profile for Freight Orders

SEL-##


SEL-##

Selection Profile for Transportation Units

SEL-##

Layout

LAYOUT-##

3. Manually create a freight order with the freight unit to CUST##-28 by dragging it to vehicle FTL-##. Take note of the freight order number. 4. Is this freight order relevant for subcontracting? Hint: Select the Carrier Ranking tab in the Subcontracting tab.

0



5. Has carrier selection been processed for this order? Hint: Select the Carrier Ranking tab in the Subcontracting tab..

6. Perform carrier selection for this freight order. Use carrier selection profile CSEL_3100_00. 7. How are the carriers ranked?

8. Why is carrier CAR##-01 ranked first?

9. While this order has triggered carrier selection, how can you tell if it has been tendered?

10. Save the freight order. 11. In NWBC, review the transportation lane US-##. 12. Which carriers are valid for means of transport FTL-##?

13. What is the carrier selection strategy for means of transport FTL-##?

0



Unit 12 Solution 34 Execute Carrier Selection

Business Example

You have been asked to investigate the carrier selection process for a typical load between a given origin and destination location.


1. Assign carrier selection setting CSEL_3100_00 to your planning profile. a) In NWBC, open the Application Administration folder and choose Planning —> Planning Profiles —> Edit Planning Profiles. b) Enter p la n -# # and continue. c) In the Profile Assignment screen area, enter Carrier Selection Setting CSEL_3100_00. d) Save your data. 2. In NWBC, enter the transportation cockpit with your planning profile and selection profiles for freight units, freight bookings, transportation units and freight orders. Use your transportation cockpit layout. Use the following data: Field

Value


SEL-##

Planning Profile

PLAN-##

Selection Profile for Freight Orders

SEL-##


SEL-##

Selection Profile for Transportation Units

SEL-##

Layout

LAYOUT-##

a) In NWBC, select the Planning folder. b) Choose Planning —> Transportation Cockpit.. c) On the Profile and Layout Sets selection screen, choose the appropriate row or enter the table data and then choose Continue.

0



3. Manually create a freight order with the freight unit to CUST##-28 by dragging it to vehicle FTL-##. Take note of the freight order number. a) Select the freight unit to customer CUST##-28. b) Drag it to vehicle FTL-## and drop it. c) Save your data. d) Record your order number. 4. Is this freight order relevant for subcontracting? Hint: Select the Carrier Ranking tab in the Subcontracting tab. Yes, based on the Subcontracting Relevance field, which is set to Relevant for Subcontracting. This is a result of the freight order type settings defined during configuration._________________________________________________________________ a) Drill into the newly created freight order by choosing the document number in the Freight Orders/ Freight Bookings screen area. 5. Has carrier selection been processed for this order? Hint: Select the Carrier Ranking tab in the Subcontracting tab.. No. No carriers are listed on the Carrier Ranking tab.__________________________________ 6. Perform carrier selection for this freight order. Use carrier selection profile CSEL_3100_00. a) In the menu bar, choose Edit and then choose Subcontracting —>Carrier Selection.

b) In the Carrier Selection Settings window, enter csel_3100_00 and choose OK. 7. How are the carriers ranked? CAR##-01 is ranked first, and CAR##-02 is ranked second.____________________________ 8. Why is carrier CAR##-01 ranked first? Carrier CAR##-01 has a cost of 1,036.33 USD/load and a priority (Carrier Peer-to-Peer Tendering Priority) of 1. CAR##-02 has a cost of 1,266.63 USD/load and a priority of 1. Since the priorities are the same, the cost is the overall determining factor. If an allocation process had been used, it would be noted in the subcontracting relevance status._________________ 9. While this order has triggered carrier selection, how can you tell if it has been tendered? The order has not been tendered. You know that because the Tendering Overview tab of the freight order is blank. Had the order been tendered, there would be additional information here.________________________________________________________________________ 10. Save the freight order.



11. In NWBC, review the transportation lane US-##. a) Choose the Master Data folder. b) Choose Transportation Network —>Transportation Lanes —>Define Transportation Lane. c) In the Start Location/Zone field, enter U S -# # . d)

In the Dest. Loc./Zone field, enter U S -# # .

e) Choose Display. 12. Which carriers are valid for means of transport FTL-##? Choose means of transport FTL-##. You can see that carriers CAR##-01 and CAR##-02 are the only carriers that are valid for means of transport FTL-##.__________________________ 13. What is the carrier selection strategy for means of transport FTL-##? Look at the details panel on the right. First, under Strategy, you can see the transportation lane is relevant to selection because the Relevant to Carrier Selection checkbox is selected. The strategy is calculated by costs, and the origin of the cost is based on internal costs. No continuous move type is assigned.________________________________________________



LESSON SU M M AR Y



•


•


•




Unit 12 Lesson 2 Tendering Freight Orders

LESSON OVERVIEW

Once a freight order has been built and a carrier selected, your business needs to let the appropriate parties know they have been selected. In this lesson you will investigate how SAP TM can support this process of order tendering. LESSON OBJECTIVES



•


•


Freight Tendering Once carrier selection has taken place, communication with the selected carrier needs to be initiated. This process is referred to as order tendering. Different tendering processes can be deployed depending upon the technology used by the carrier. You use this process to tender (offer) a freight order to one or more potential carriers. Tendering is a bidding process, in which you request one or multiple carriers to submit a quote for a transportation service that is defined in a freight order. You can select the carrier that you want to execute the transportation service by evaluating the quotes. The main characteristics of the tendering process are flexible configuration and the reduction of required manual interaction to support ease of use and lower total cost of ownership (TCO).



Carrier Selection I 1-step Planning

Execute Carrier Selection

C heck Incom patibilities D ete rm in e T C M or Internal Costs

Transportation Allocations

Business S hares

C ontinuous M ove

Build R anking List

Autom atic A ssignm en t

Manual

Order Tendering

A vailable C arriers

Tendering A ssign C arrie rto FO R

Figure 198: Subcontracting: Tendering - Context Process Flow

Tendering Types In general, there are two types of tendering. Short term tendering is where tendering is executed based on specific orders. This is known as order tendering. SAP TM supports the following short term tendering scenarios: •

Peer-to-Peer Tendering

•

Broadcast Tendering

The strategies for each are determined in planning profiles in SAP TM. Parties and Roles in the Tendering Process

At least two parties are involved in the tendering process - a customer who wants to subcontract a transportation service that is defined in a freight order, and a supplier (subcontractor) or carrier, who potentially carries out the transportation service. There are two roles on the customer side of the tendering process. The first is a transportation dispatcher, who is responsible for the transportation service, that is, the freight order. The second is the tendering manager, who is responsible for configuring and executing the tendering process and acquiring an acceptable quote from a carrier to perform the transportation service. Manual and Automatic Tendering

When a transportation dispatcher initiates the tendering process, they have two options: manual process configuration or automatic tendering. If they want to tender only a single freight order, the transportation dispatcher can choose between the two options. If they initiate a tendering process using manual configuration, the tendering manager must configure and start the tendering process manually. If the transportation dispatcher wants to tender more than one freight order, they must initiate automatic tendering and use the automatic tendering configuration in the system.



Peer-to-Peer Tendering

1.

Carrier ABC 2.

RFQ

Carrier XYZ 3.

Carrier 123 4.

Carrier DEF 5.

Carrier 789

Sequential Processing

L

Step/Carr...

Tendering Type

▼

Peer-to-Peer Tendering - Response Required

Step 1

Tendering Process ▼

Freight RFQ Based, Aw ard Automatically Freight RFQ Based, A w ard Manually Freight RFQ Based, A w ard Automatically Direct Tendering, Send Freight Order Directly

Figure 199: Peer to Peer Tendering

Peer-to-peer tendering is a process whereby freight orders are tendered sequentially or offered to preselected carriers. Order Tendering Process: Peer To Peer Example Process: Peer-to-Peer Tendering

Freight Order

Carrier Selection

Freight Order Carrier Tendering Quotation

Freight Quotation Freight Evaluation & Order Carrier Assignment Update, ■ Request for ■ RFQ Quotation & Sending acceptance / ■ Carrier ranking (RFQ) to Carrier rejection with ■ Embedded creation & publishing

price quotation

analytics for decision support

Figure 200: Order Tendering Process - Peer To Peer

Peer-to-peer tendering involves the sequential sending of freight requests for quotation (freight RFQs) to each proposed carrier. The system waits until the carrier sends a freight quotation (FQ) or until the maximum response time has passed. If the carrier does not send a quote within the maximum response time, the peer-to-peer tendering process continues, and the system sends a request for quote to the next carrier. If peer-to-peer tendering ends without an acceptable quote, the tendering process continues with the next tendering process step that you have configured. If the carrier sends a quote before the maximum response time has elapsed, the system evaluates the quote and can either accept or reject it. In the case of rejection, a new RFQ is sent out. The process continues until at least one acceptable FQ has been received. The system awards this a Quotation Acceptable evaluation result and the process ends successfully. There are two types of peer-to-peer tendering: response required and no response required.



Broadcast Tendering

Broadcast tendering is a tender process whereby freight orders are simultaneously tendered (offered) to preselected carriers. All carriers have to respond within a given maximum response time. There are two types of broadcast tendering: best offer and first acceptable offer. Depending on which one of these is being used, either the first acceptable quote wins or, after the maximum response time, the system evaluates all the acceptable quotes and selects the carrier that has submitted the quote with the lowest price. If broadcast tendering ends without an acceptable quote, the tendering process continues with the next tendering process step that you have configured.

Freight Order

RFQ

First Come, First Served SteptCarr...

Tendering Type

▼

Broadcast Tendering - Best Otter

Stepl

Tendering Process ▼

Freight RFQ Based, Award Automalicaty

▼

Freight RFQ Based, Award Manually Freight RFQ Based, Award Automaticaly Direct Tendering, Send Freight Order Directly

Figure 201: Broadcast Tendering

Tendering Profiles

The tendering profile contains basic tendering data and is a prerequisite for automatic tendering. You can use a tendering profile when you manually create a tendering plan. Within the profile, you can define multi-step tendering. This allows a company to mix tendering types. For example, you can first use peer-to-peer tendering, and if this is unsuccessful you can use broadcast tendering. In a tendering profile, you can make settings in relation to the following options: •

Choose from tendering variants - direct, peer-to-peer, broadcasting (best offer, first acceptable offer)

•

Choose fully or semi-automatic rules-based tendering (response time and price limits, automatic re-tendering)

•

Configure the tendering process and RFQ publishing

•

Set up web-based, e-mail, SMS, B2B tendering communication



•

Set up authorization-based RFQ processing and data visibility (carrier authorization to change the price and delivery dates, view tender price limit, stop date and rejection code reasons, support of free text and attachments)

•

Make settings in relation to currency

•

Maintain event monitoring and exception-based management

RFQUpdates TALan... Relative Price... MaxmumResp... Carner-Speciti... VisiMtySettings .DEFAULT NoUpdate ▼ 100% 99:59 0 NoUpdate Update, DoNot Free UpTALUponRejection Update, Free UpTALand BSUponRejection A

.

Figure 202: Tendering Profile





Unit 12 Exercise 35 Tender a Freight Order

Business Example

Before a freight order can be transported, it must be offered to, accepted by, and assigned to a carrier. This assignment could be part of a long-term arrangement or a once-off arrangement. In either case, you must be able to initiate the tendering process and understand the role it plays in the overall transportation process.

Note: Required: This exercise is dependent on the completion of the exercise Execute Carrier Selection. You must have successfully performed the preceding exercise on executing carrier selection before proceeding with tendering a freight order. 1. Tender the freight order created in the previous exercise using tendering profile TM120_00_TEND_PROFILE. 2. What is the status of tendering step 1?

3. What is the status of the RFQ sent to the first carrier?

4. Has an RFQ been sent to the second carrier?

5. Save the freight order and note the RFQ number. 6. The next steps in this exercise round out the process by creating a quotation. Accept the tendering freight order on behalf of CAR##-01.



7. Go back to the freight order. What is the response code of the quotation?



Unit 12 Solution 35 Tender a Freight Order

Business Example

Before a freight order can be transported, it must be offered to, accepted by, and assigned to a carrier. This assignment could be part of a long-term arrangement or a once-off arrangement. In either case, you must be able to initiate the tendering process and understand the role it plays in the overall transportation process.

Note: Required: This exercise is dependent on the completion of the exercise Execute Carrier Selection. You must have successfully performed the preceding exercise on executing carrier selection before proceeding with tendering a freight order. 1. Tender the freight order created in the previous exercise using tendering profile TM120_00_TEND_PROFILE. a) Open the Freight Order Management folder and choose Road —> Edit Road Freight Order. b) Enter the freight order number from the previous exercise and continue. c) In the application toolbar, choose Subcontracting —► Automatic Tendering. d) Enter tendering profile

t m i 20_00_ tend _ p r o f il e

and choose OK.

e) Save your data. 2. What is the status of tendering step 1? In process.__________________________________ 3. What is the status of the RFQ sent to the first carrier? Open._______________________________ 4. Has an RFQ been sent to the second carrier? No._____________________________________ 5. Save the freight order and note the RFQ number.


517



6. The next steps in this exercise round out the process by creating a quotation. Accept the tendering freight order on behalf of CAR##-01. a) In NWBC, open the Freight Order Management folder and choose Road —► Overview Tendering. b) Choose Freight RFQs-Open (). c) Choose your RFQ number. d) Choose Edit and select the row with the quotation. e) Choose Create Quotation. f) Select the row with the quotation and choose Submit Quotation and Save. 7. Go back to the freight order. What is the response code of the quotation? The response code of the quotation is accepted.________________________________ a) Go back to the freight order and choose Refresh. b) On the Subcontracting tab, review the tendering overview.



Com m unication M ethod Tendering

As part of the tendering process, it is important to review the communication methods that support the tendering scenarios. For carriers who may not be able to support EDI (electronic data interchange) scenarios, SAP has developed a Web Ul to improve communication. This requires subcontractors to log on to SAP TM using the Web in order to process a freight order. On a periodic basis, each subcontractor views their RFQs (modeled as tendering requests) and submits quotations (modeled as tendering responses). Each subcontractor is provided with their own user IDs and passwords, as well as the relevant authorization to restrict visibility to only the loads that have been tendered to them. Additional methods are supported, such as receiving RFQs by e-mail and SMS and submitting quotations by e-mail without the need to access an SAP TM system at all. In this case, an RFQ is sent to a carrier by e-mail or SMS message. The carrier responds to the e-mail using a regular email client on a PC or a mobile device. The e-mail is then converted (using PI) into a quotation. Carriers can accept RFQs directly, reject them with a specified reason, or accept them with changes.

Freight Order Root / Subcontracting Tendering Tendering Step Tendering Request Tendering Response

X I Message

Figure 203: Tendering Communication Methods

Advanced Communication

If a subcontractor is more technically advanced, B2B communication can be utilised. In this situation, a copy of the freight order is created for the carrier (the tendering manager or system administrator can control what is included in the copy that is visible to the carrier). The copy is persisted in the system to retain what was communicated to the carrier. A freight request for quotation (tendering request) is sent via PI and received as a forwarding quotation in the supplier's SAP TM system. The carrier can accept the order directly or, if the first carrier rejects the order, the freight order will be sent to the next carrier. Finally, a quotation confirmation is sent back to the customer and is converted into a quotation (tendering response) in the customer’s SAP TM system. The Change Controller allows you to react to changes in the FO, for example, by stopping tendering when there are major changes in the FO.



Mobile Tendering

Freight RFQs can easily be integrated with carriers who cannot implement a complex B2B integration. Mobile tendering allows a mobile device to receive new RFQs, respond to RFQs, and include changes to dates and prices. Users can check addresses and routes on the map, e-mail or phone the contact person, create a calendar entry for awarded tenders, and check other appointments in the calendar.





•


•






Unit 12

Learning Assessment

1. In relation to costs and priorities in carrier selection, internal costs do not refer to real world costs but rather to virtual costs assigned to carriers, documents, units and so on throughout the transportation process. These internal costs are used for weighting only. Determine whether this statement is true or false. | True False 2. Based on what you have learned about business share in transportation planning, which of the following statements is true? Choose the correct answer. | A Business share is an in-built mechanism in SAP TM to ensure that all carriers in a region have sufficient business. B Business share buckets provide a means for numerous shippers to pool together to create merged (shared) freight orders. | C Business share settings define the percentage of business to be allocated to various carriers. Costs are incurred for non-adherence and the system takes these into account during optimization. D A company may have working formalized relationships with a number of carriers. Business share allocation ensures that all carriers receive the same amount of business from the company. 3. Broadcast tendering refers to a process whereby all quotations received (in response to an RFQ) are broadcast to all carriers in an effort to improve transparency. Determine whether this statement is true or false. | True False



4. Which tendering types are defined in SAP Transportation Management? Choose the correct answers. | A Peer-to-peer tendering-no response required B Peer-to-peer tenderingresponse required C Broadcast tendering- first acceptable offer D Open tendering-price limit



Unit 12


1. In relation to costs and priorities in carrier selection, internal costs do not refer to real world costs but rather to virtual costs assigned to carriers, documents, units and so on throughout the transportation process. These internal costs are used for weighting only. Determine whether this statement is true or false. [x ] True False Correct. Internal costs do not imply real world costs and are used for weighting only. 2. Based on what you have learned about business share in transportation planning, which of the following statements is true? Choose the correct answer. | A Business share is an in-built mechanism in SAP TM to ensure that all carriers in a region have sufficient business. B Business share buckets provide a means for numerous shippers to pool together to create merged (shared) freight orders. |~X~| C Business share settings define the percentage of business to be allocated to various carriers. Costs are incurred for non-adherence and the system takes these into account during optimization. D A company may have working formalized relationships with a number of carriers. Business share allocation ensures that all carriers receive the same amount of business from the company. Correct. Business share settings define the amount of business (%) to be allocated to various shippers.



3. Broadcast tendering refers to a process whereby all quotations received (in response to an RFQ) are broadcast to all carriers in an effort to improve transparency. Determine whether this statement is true or false. True False Correct. Broadcast tendering refers to a scenario in which an RFQ is sent to multiple carriers at the same time and the responses are then evaluated. This is in contrast to peer-to-peer tendering, which is sequential. 4. Which tendering types are defined in SAP Transportation Management? Choose the correct answers.

|~xj

A Peer-to-peer tendering-no response required

|~xj

B Peer-to-peer tendering-response required

|~xj C Broadcast tendering- first acceptable offer D Open tendering-price limit That is correct. Peer-to-peer tendering- no response required, peer-to-peer tenderingresponse required, and broadcast tendering- first acceptable offer are tendering types available in SAP Transportation Management.


0


TM110 - ERP Integration for Order Management (Shipper Specific).pdf

Recommend Documents