TM Config

SAP Transportation Management

Domestic Outbound Transportation: Test Case

PUBLIC Document Version: 1.0 – 1.0 – September September 2012

Copyright © Copyright 2012 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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.

Apple, App Store, iBooks, iPad, i Phone, iPhoto, iPod, i Tunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

(C) SAP AG

2

Copyright © Copyright 2012 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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.

Apple, App Store, iBooks, iPad, i Phone, iPhoto, iPod, i Tunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

(C) SAP AG

2

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

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

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects 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.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

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

(C) SAP AG

3

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

(C) SAP AG

4

Icons in Body Text Icon

Meaning Caution Example Note Recommendation Syntax

Additional icons are used in SAP Librar y documentation to help you identify different types of information at a glance. For more information, see Help on Help  General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library .

Typographic Conventions Type Style

Description

Example text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

EXAMPLE TEXT

(C) SAP AG

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

5

Table of Contents Domestic Outbound Transportation: Test Case .............................................................................. 8 Prerequisites .............................................................................................................................. 10 User-Specific Customizing ..................................................................................................... 11 Master Data and Organizational Data .................................................................................... 12 Roles ...................................................................................................................................... 13 Process Overview Table ............................................................................................................ 14 Process Steps ............................................................................................................................ 15 Create Sales Orders .................. ................. .................. ................. .................. ................. ...... 16 Manage Transportation Requirements ................................................................................... 18 Creating or Updating Order-Based Transportation Requirements ..................................... 19 Creating Delivery-Based Transportation Requirements ..................................................... 21 Plan Freight and Select Carriers ............................................................................................ 22 Performing Automatic or Manual Planning ......................................................................... 23 Determining Planning Scope .............................................................................................. 24 Reviewing Planning Output ................................................................................................ 25 Triggering Delivery Creation ............................................................................................... 26 Starting the Tendering Process .......................................................................................... 27 Tender Freight ........................................................................................................................ 28 Evaluating Responses ........................................................................................................ 29 Performing Peer-to-Peer Tendering ................................................................................... 30 Selecting and Assigning a Carrier ...................................................................................... 31 Execute and Monitor Freight .................................................................................................. 33 Sending a Freight Order ..................................................................................................... 34 Checking the Status of Freight Orders ............................................................................... 35 Loading Freight Orders ....................................................................................................... 36 Arranging and Printing Documentation ................................. ................. ................. ............ 37 Monitoring the Freight Order in Transit ................................. ................. ................. ............ 38 Handling Exceptions ........................................................................................................... 39 Delivering the Load ............................................................................................................. 40 Setting the Status of Freight Orders ................................................................................... 41 Settle Freight Orders .............................................................................................................. 42 Retrieving Freight Orders or Bookings ............................................................................... 43 Creating a Freight Settlement Document ........................................................................... 44 Transferring Freight Settlement Documents to SAP ERP .................................................. 45 Monitoring Invoice Verification ............................................................................................ 46

(C) SAP AG

6

Reviewing Freight Cost Allocation Documents .................. ................. .................. .............. 47

(C) SAP AG

7

Domestic Outbound Transportation: Test Case This business scenario can be used by a shipper that wants to manage domestic outbound freight. The shipper is a manufacturer and distributes products through its network of plants, distribution centers, and third party warehouse operations. The shipper has a logistics organization that is responsible for the timely, cost effective, and efficient transportation of products between and from the shipper’s facilities and to the end customer. The shipper receives the order electronically or manually through ERP Sales and Distribution, performs availability checks in either ATP or GATP, plans and executes the transportation in SAP Transportation Management (SAP TM), and calculates freight costs in SAP TM before sending them to SAP ERP for payment. The main features of the Domestic Outbound Transportation scenario are described as follows: 

By seamlessly integrating SAP ERP orders and SAP TM planning processes, once a sales order or delivery is created in SAP ERP, it can be automatically transferred to SAP TM and saved as a transportation requirement. SAP TM provides the necessary transparency to determine the order requirements such as times and shipping conditions, as well as product, geographical, and customer requirements.



In the planning center of SAP TM, the transport planner can plan loads across orders based on specific user filters. This process can be either interactive or automatic. Various transportation methods can be evaluated to determine the most effective options based on cost and service.



The carrier is determined during the load planning step or in a separate step based on costs. Several carriers may be available and SAP TM chooses one based on previously defined criteria before tendering the freight order (FOR) to the carrier.



The tendering process is based on a cascading peer-to-peer option. This means that if a carrier rejects a tender, it is automatically tendered to the next carrier. Allocations are updated based on the assignment to the transportation order (TOR) once a carrier accepts the TOR.



SAP Event Management (EM) is used to track and trace the transport.

The following optional features are not included in the scenario or this test case description: 

There are two other strategies available for carrier selection – priority and business share. These can work in conjunction with or independently of costs (business share).



Broadcast tendering is not included in this scenario.



With the integration of SAP TM and SAP Environment, Health, and Safety (EH&S), dangerous goods information can be accessed directly in transportation documents. Dangerous goods checks (such as mixed loading checks and maximal quantity checks) can be performed during freight unit building and load consolidation, as well as when checking consistency between different transportation documents. Transport-relevant dangerous goods information can be printed along with shipping instructions.

SAP Transportation Charge Management (TCM) calculates the transportation charges and transfers them to SAP ERP using the Supplier Freight Invoice Request processing component to create the purchase order (PO) and associated service entry sheet (SES). The PO is used to establish the accruals against which the carrier is paid.

(C) SAP AG

8

Variant 1 The Domestic Outbound Transportation scenario description contains a variant of the standard procedure known as “Domestic Outbound Transportation with Cost Distribution”. If you use this variant, the procedures differ to the standard procedures and are described separately in the relevant sections.

(C) SAP AG

9

Prerequisites Before you start to conduct this test case, you must complete the following tasks: 

Configure your user data (see User-Specific Customizing [Page 11])



Set up your master data and organizational data (see Master data and organizational data [Page 12])



Configure your roles (see Roles [Page 13])

(C) SAP AG

10

User-Specific Customizing Event Management Setup Ensure that you setup your user according to the Assigning User to Web Transactions details in the Integration of SAP Event Management guide. You can access the guide in SAP Solution Manager by choosing Solutions/Applications SAP Transportation Management Configuration Structures Basic Settings for SAP TM 9.0 Integration of SAP Event Management . Invoice Integration Ensure that your user profile contains the parameter TM_INVOICE_CLERK (with an initial value).

(C) SAP AG

11

Master Data and Organizational Data Master and organizational data is created in your SAP ERP system during the implementation phase. This data reflects the organizational structure of your company; master data focuses on operations, for example, master data for materials, vendors, and customers. The business process is enabled with this organization-specific master data.

You can also use customized values for any material or organizational data for which you have created master data. Use the following master data in the process steps described in this document: Master and Organizational Data

Value

Material

DOT-PROD-01

Sold-to party

DOT-CU-01 to DOT-CU-20

Ship-to party

DOT-CU-01 to DOT-CU-20

Payer Plant

3100

Storage Location

0001

Shipping Point

3100

Sales organization

3000

Distribution channel

10

Division

00

Company Code

3000

(C) SAP AG

12

Roles You must assign the following roles to the users who are to test this scenario. Transportation Management Business Role

Technical Name

Customer Service Agent

/SCMTMS/CUSTOMER_SERVICE_AGENT

Transportation Planner

/SCMTMS/PLANNER

Dispatcher

/SCMTMS/DISPATCHER

Booking Specialist

/SCMTMS/BOOKING_AGENT

Carrier Settlement Specialist (for example, Payment Specialist)

/SCMTMS/CARRIER_SETTLEMENT_SP

Customer Settlement Specialist

/SCMTMS/CUSTOMER_SETTLEMENT_SP

Freight Contract Specialist

/SCMTMS/FREIGHT_CONTRACT_SPEC

Process Administrator

/SCMTMS/PROCESS_ADMINISTRATOR

Transportation Manager

/SCMTMS/TRANSPORTATION_MANAGER

Carrier Internet User

/SCMTMS/SERVICE_PROVIDER

Display

/SCMTMS/DISPLAY

Event Management Business Role

Technical Name

Comment

SAP Event Management User

/SAPTRX/SAP_EM_USER

Required to access EM Webtransactions

Sales Order Processing

SAP_LO_SD_SALES_ORD_PR OCESSING

Required to create sales orders

Online Invoice Verification

SAP_MM_IV_CLERK_ONLINE

Required to enter and verify Carrier Invoices

(C) SAP AG

13

Process Overview Table Process Step Sales Order Processing

TM: Managing Transportation Requirements

TM: Planning Freight and Selecting Carriers

Business Role Customer Service Agent



Transaction Code

VA01 VA02

SE38 NWBC

NWBC

Expected Results Sales order is created. Order-based transportation requirements (OTRs) and delivery-based transportation requirements (DTRs) are created and transferred to the SAP TM system. Freight orders are created according to freight unit planning. Carriers are selected.

TM: Managing Freight Orders


NWBC

Freight orders are created and freight units assigned manually. Carriers are selected.

TM: Tendering Freight


NWBC

Carriers are finalized by peer-to-peer direct tendering. Freight order is sent to carrier.

TM: Executing and Monitoring Freight


NWBC

Fright order is executed and monitored for different events.

TM: Settling Freight Orders

Carrier Settlement Specialist

NWBC

Invoice is created and transferred to the SAP ERP system.

(C) SAP AG

14

Process Steps To test this scenario, you must complete the following activities and procedures: 

Create Sales Orders [Page 16]



Manage Transportation Requirements [Page 18]



Plan Freight and Select Carriers [Page 22]



Tender Freight [Page 28]



Execute and Monitor Freight [Page 33]



Settle Freight Orders [Page 42]

(C) SAP AG

15

Create Sales Orders In this procedure, you create a sales order and a corresponding delivery document. The SAP ERP order process is tightly integrated with the SAP TM planning process. Once a sales order or delivery is created in the SAP ERP system, it can be automatically transferred to the SAP TM system and saved as a transportation requirement. SAP TM provides the necessary transparency to determine the order requirements such as times, products, and geographical and customer requirements. A customer service agent creates sales orders aut omatically or manually in the SAP ERP system. When the sales orders are saved and if they are relevant for transfer, they are transferred to the SAP TM system automatically and saved as order-based transportation requirements (OTRs).

Procedure 1.

On the SAP Easy Access screen of your SAP ERP system, choose Logistics and Distribution Sales Order Create or call transaction VA01.

2.

Enter order type ODOT (standard order) and press ENTER.

3.

Enter the following data: Field

Sales

User Action and Values

Sold-to party

DOT-CU-01

PO Number

ODOT-001

Req. deliv. Date

Pricing date

Material

DOT-PROD-01

Order quantity

100 Bags

4.

Press ENTER.

5.

If necessary, copy the confirmed quantity and date or select the Complete dlv checkbox.

6.

If required, enter a payment term such as NT30.

7.

Press ENTER.

8.

Select the Sales area for customer with 3000 USA Philadelphia / Final customer sales / cross-division.

9.

Save your entries. Make a note of the sales order number: __________

10. Access the change transaction from the SAP Easy Access menu by choosing Logistics Sales and Distribution Sales Order Change or calling transaction VA02. 11. Enter your order number and press ENTER.

(C) SAP AG

16

12. Choose

Sales Document

Deliver

.

Ensure that the selection date is same as the one you entered in the Req. deliver Date field. 13. Save your entries. Make a note of the sales document number: __________ 14. Repeat the above steps to create further sales orders with different requirements and delivery dates. You can, for example, use the following data: Sold-to party

PO Number

Req. deliv. Date

Material

Order quantity

DOT-CU-02

ODOT-CD-01

Today + 10 days

DOT-PROD-01

10 Bags

DOT-CU-03

ODOT-CD-02

Today + 10 days

DOT-PROD-01

15 Bags

DOT-CU-07

ODOT-002

Today + 10 days

DOT-PROD-01

100 Bags

DOT-CU-08

ODOT-003

Today + 10 days

DOT-PROD-01

100 Bags

DOT-CU-09

ODOT-004

Today + 10 days

DOT-PROD-01

10 Bags

DOT-CU-17

ODOT-005

Today + 11 days

DOT-PROD-01

150 Bags

DOT-CU-10

ODOT-006

Today + 14 days

DOT-PROD-01

10 Bags

DOT-CU-14

ODOT-007

Today + 13 days

DOT-PROD-01

10 Bags

Result Sales orders and delivery documents are created. Order-based transportation requirements (OTRs) and delivery-based transportation requirements (DTRs) are also created.

OTRs and DTRs can be transferred automatically to SAP TM only if the output type is TRSO in the sales order and the delivery document. Check the output type in the sales order by choosing Extras Output Header Edit . Check the output type in the delivery document by choosing Extras Delivery Output Header . Variant 1 If you are using the cost distribution variant, sales orders with PO numbers ODOT-CD-01 and ODOT-CD-02 are created. In the following steps, use the sales orders only.

(C) SAP AG

17

Manage Transportation Requirements This activity enables companies to tightly integrate their SAP ERP system and their transportation planning and execution system. The activity supports shippers by transferring order information from SAP ERP to SAP Transportation Management (SAP TM), thus providing the planning system with transportation requirements at a very early stage. This enables transportation planning to take advantage of longer planning horizons, which leads to better results in the optimization process and greater flexibility in the decisions that need to be taken during transportation planning. In this scenario, you can create and maintain the following requirements: 

Order-based transportation requirements (see Creating or Updating Order-Based Transportation Requirements [Page 19])



(Optional) Delivery-based transportation requirements (see Creating Delivery-Based Transportation Requirements [Page 21])

(C) SAP AG

18

Creating or Updating Order-Based Transportation Requirements In this procedure, you create and check an order-based transportation requirement (OTR).

Procedure 1.

In your SAP ERP system, call transaction SE38.

Steps 2 – 9 are not required if the transportation order (TOR) already exists (this is created automatically in the Creating Sales Orders [Page 16] procedure). 2.

In the Program field, enter TMTRQCHECK and choose Execute.

3.

Choose Sales order .

4.

Enter the sales order number.

5.

Select the Display all messages checkbox.

6.

In the RFC destination field, enter the logical system name of the SAP TM system.

7.

Choose Execute.

8.

Make a note of the TM Object number: __________ This is the TOR number.

9.

Choose Back .

10. In SAP NetWeaver Business Client (SAP NWBC), choose ERP Logistics Integration Transportation Requirement Display Order-Based Transportation Requirement . 11. Search for the OTR number created in the Creating Sales Orders [Page 16] procedure. 12. Select the OTR link. 13. Check the data in the following table. All data should match the SAP ERP d ata: Tab Page

Value

At Header Level General Data

Document type, service level, order reference

Business Partner

Bill-to- party, payer, consignee

Document Flow

TOR number, sales order number, freight unit numbers

Terms and Conditions

Incoterms, Incoterm locations

(C) SAP AG

19

Tab Page

Value

At Item Level Item Level

Products, quantity, delivery dates

Note

Text information

14. Make a note of the following numbers:

o

TM Object number: __________

o

Freight Unit numbers: __________

15. Repeat the above steps for all sales documents.

Changes to a sales order (in SAP ERP) update the OTR (in SAP TM) either automatically or as the result of a transfer. Variant 1 For the cost distribution scenario, repeat the above steps for the sales order numbers assigned to ODOT-CD-001 and ODOT-CD-002 . In addition, select both OTRs and choose the Start Transportation Cockpit pushbutton on the Display Order-Based Transportation Requirements screen.

Result When sales orders that are relevant for transfer are saved, they are automatically transferred to the SAP TM system and saved as order-based transportation requirements (OTRs).

(C) SAP AG

20

Creating Delivery-Based Transportation Requirements In this optional procedure, you create and check delivery-based transportation requirements (DTRs). This procedure is not necessary if you create the delivery document in SAP ERP, which creates the DTR automatically.

Procedure 1.

In your SAP TM system, call transaction SE38.

2.

In the Program field, enter /SCMTMS/DLV_BATCH and choose Execute.

3.

Select Sales Order as the Document Type.

4.

Enter the sales order number in the Original Order field. Choose Execute.

5.

Make a note of the TM Object number: __________ This is the delivery order (DOR) number.

6.

Choose Back .

7.

In SAP NetWeaver Business Client (SAP NWBC), choose ERP Logistics Integration Transportation Requirement Display Delivery-Based Transportation Requirements .

8.

Search for the required DOR number.

9.

Select the DOR link. Check that all details are correct.

10. In your SAP ERP system, choose SAP ECC Menu Logistics Sales Order Change or call transaction VA02.

Sales and Distribution

11. Enter the sales order number in the Document field. Choose Enter . 12. Choose Document flow .

Result When delivery documents that are relevant for transfer are saved, they are automatically transferred to the SAP TM system and saved as delivery-based transportation requirements (DTRs).

(C) SAP AG

21

Plan Freight and Select Carriers You use this business activity to create and process the business objects that are required for transportation. In this scenario, you can create the following business objects: 

Planning scope (see Performing Automatic or Manual Planning [Page 23])



(Optional) Planning profile (see Determining Planning Scope [Page 24])



Planning output (see Reviewing Planning Output [Page 25])



(Optional) Delivery in ERP creation (see Triggering Delivery Creation [Page 26])



Carrier selection (see Starting the Tendering Process [Page 27])

(C) SAP AG

22

Performing Automatic or Manual Planning In this procedure, you determine the planning scope for optimizer planning.

Procedure 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Transportation Cockpit .

Planning Planning

2.

On the Profile and Layout Sets screen, enter the following criteria: Field

Value

Selection Profile (FUs)

DOT-GEN-SEL-01

Planning Profile

DOT-PLAN-PROF-01

Selection Profile (FOs)

DOT-GEN-SEL-01

Selection Profile (FBs)

DOT-GEN-SEL-01

Capacity Selection Setting

DOT-CAP-SEL-01

3.

Save the selection.

4.

Select the profile set and choose Continue.

5.

Search for and select the required freight units.

6.

Choose

7.

The system proposes a temporary freight order (FOR) number.

Optimizer Planning Selected Entries with All Resources

.

Choose Accept . 8.

Choose Save. The system confirms that freight orders have been created.

9.

Make a note of the freight order numbers: __________

Variant 1 If you are using the cost distribution variant, you must plan your transportation activities manually as follows: 1.

Select the appropriate freight units for the selected OTRs.

2.

Assign the freight units to one of the vehicle resources displayed by using drag and drop. The system creates a freight order.

3.

Save the freight order.

Result Freight orders are created and a vehicle resource is assigned to each freight order.

(C) SAP AG

23

Determining Planning Scope In this optional procedure, you can change the planning profile and check the planning output.

Procedure 1.


Planning Planning

2.

On the Profile and Layout Sets screen, select the following criteria: Field

Value

Selection Profile (FUs)

DOT-GEN-SEL-01

Planning Profile

DOT-PLAN-PROF-01

Selection Profile (FOs)

DOT-GEN-SEL-01

Selection Profile (FBs)

DOT-GEN-SEL-01

Capacity Selection Setting

DOT-CAP-SEL-01

3.

Save the selection.

4.

Select the profile set and choose Continue.

5.

Search for and select the required freight units.

6.

Choose

7.

Check the planning output.

8.

If you want to change the planning profile, choose Selection Screen .

9.

On the Profile and Layout Sets screen, select other criteria and continue planning.

(C) SAP AG

Optimizer Planning Selected Entries with All Resources

.

Change Profile Selection

Profile

24

Reviewing Planning Output In this procedure, you review the planning output.

Procedure 1.


2.

Select a recently created freight order.

Planning Planning

The details of the freight order are displayed in the lower right-hand window. On the Overview screen, the vehicle resource that is assigned to the freight order is displayed. 3.

Go to the Stages tab page. Check the source and destination location, total distance, and departure and arrival times at each location.

4.

Go to the Map tab page to view the route. Select the route, right-click, and choose Show Route to see the actual route.

(C) SAP AG

25

Triggering Delivery Creation In this optional procedure, you create a delivery document in SAP ERP from information in SAP TM.

This procedure is necessary only if the delivery document has not yet been created in SAP ERP.

Procedure You can use either of the following options. Option 1 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Overview Planning Freight Unit .

Planning Worklist

2.

Sort and select freight units from your personal object worklist (POWL) by highlighting the row containing the freight unit.

3.

Choose Create Deliveries in ERP .

4.

Select your freight units and choose Create Delivery Proposal .

5.

Choose Send Delivery Proposals to ERP .

6.

Choose Close to close the window.

Option 2 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Planning Freight Order .

2.

Sort and select your freight order from the POWL.

3.

Choose Create Deliveries in ERP .

4.

Choose Send Delivery Proposals to ERP .

Planning Overview

Result Delivery documents are created in SAP ERP for each freight order.

(C) SAP AG

26

Starting the Tendering Process You perform this procedure to select carriers by direct peer-to-peer tendering. For this scenario, the tendering process is automatic and peer-to-peer.

Procedure Option1 Once you save the temporary freight order, the system generates an RFQ (request for quotation) and sends it to a carrier based on predefined selection criteria. Option2 (If Tendering Does Not Start Automatically) 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Land Overview Tendering .

2.

Select your freight orders.

3.

Choose

4.

Enter the tendering manager, for example, with the tendering profile DOT-TEND-PROFP2P and choose OK .

Tendering Start

Freight Order Management

.

Result Carriers are selected by tendering and RFQs are sent to carriers for all freight orders.

For direct tendering, the carrier can respond only by accepting or rejecting the freight order. In this test case, the first carrier rejects the freight order. SAP TM retenders it to the second carrier and the second carrier accepts.

(C) SAP AG

27

Tender Freight You use this business activity to send freight requests for quotation (freight RFQs) to carriers. Carriers can accept or decline these freight RFQs and change data, such as the price, when returning the freight quotations. You can then automatically accept the tender and send the freight order back to the awarded carrier. A tendering process starts if you or the system determines more than one possible carrier. The tendering process results in one carrier being selected to execute the freight order. In this scenario, tendering freight includes the following tasks: 

Peer-to-peer tendering (see Performing Peer-to-Peer Tendering [Page 30])



Assigning carriers (see Selecting and Assigning a Carrier [Page 31])

(C) SAP AG

28

Evaluating Responses Procedure 1.


2.

In the Program field, enter /SCMTMS/TEND_CONT_PROCESS and choose Execute.

3.

On the Parallel Processing Profile screen, choose Execute. The system selects the best acceptable quotation and ignores the remaining quotations.

4.

Navigate to the Tendering Overview tab page and check the following for the awarded quotation:

(C) SAP AG

o

The response code in the Response Code column is Accepted .

o

The RFQ status is B and the quotation status is Sent .

o

The evaluation result is OK .

29

Performing Peer-to-Peer Tendering The carrier is determined during load planning or as part of a separate, cost-based step. Several carriers may be available and one is chosen based on predefined criteria. The system tenders the freight order to the chosen carrier. The tendering process is based on a cascading peer-to-peer option. This means that if a carrier rejects a tender, it is automatically tendered to the next carrier. Allocations are updated based on the assignment of the transportation order.

Procedure 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Land Overview Tendering .

2.

Go to Freight RFQs.

3.

Select the first RFQ sent to a carrier in Starting the Tendering Process [Page 27]

4.

Choose Create freight quotation, and then choose Reject or Accept .


This action is performed with the role of a carrier. The carrier can either accept or reject the received RFQ. 5.


6.

In the Program field, enter /SCMTMS/TEND_CONT_PROCESS and choose Execute.

7.

On the Process freight quotations and overdue freight RFQs screen choose Execute.

8.

Choose OK . View the messages on the Freight quotations and overdue freight RFQs screen.

9.

Choose Back .

Result The freight RFQ has been accepted, the tendering process is successful, and the carrier has been awarded the freight order.

(C) SAP AG

30

Selecting and Assigning a Carrier In this procedure, you assign a carrier to a freight order.

Procedure Choose one of the following options: Option 1 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Land Edit Freight Order .

2.

Enter a freight order number and choose Continue.

3.

Go to the General Data tab page.

4.

Check the carrier that is assigned to the freight order under Transportation.

5.

On the Tendering Overview tab page, check the Status and Response Code of the RFQs for all carriers.


For one of the quotations, the Response Code should be Accepted . Option 2

Option 2 is optional because the carrier is selected by automatic peer-to-peer tendering. 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Land Overview Freight Orders .

2.

Select a freight order from the list.

3.

Choose

4.

On the Profile and Layout Sets screen, choose New .

5.

Enter the following in selection criteria:

Subcontracting

Carrier selection


.

Field

Value

Selection Profile

DOT-GEN-SEL-01

Carrier Selection Settings

DOT-CAR-SEL-01

6.

Select the row and choose Start Carrier Selection.

7.

Choose

Carrier selection Automatic

.

Option 3 1.


2.


(C) SAP AG


31

3.

Choose

Subcontracting

Carrier selection

.

4.

In the Carrier Selection Settings field, enter DOT-CAR-SEL-01 .

5.

Choose OK .

6.

Save the document.

Variant 1 If you are using the cost distribution variant, use option 2.

Result The system assigns carriers to all freight orders.

(C) SAP AG

32

Execute and Monitor Freight This activity covers the actual execution of the transportation process. The transportation planner checks whether freight orders are ready for execution, the customs declaration is complete, and the relevant documents have been printed. If a customs process is involved, freight orders are blocked. After the GTS system has returned a positive result, actual execution can start. In this activity, the freight orders are loaded and deliveries are carried out. The activity also handles the various exceptions that may occur during transportation. At the end of the process, you receive the corresponding execution information. This activity comprises the following freight order procedures: 

(Optional) Send freight order to carrier (see Sending a Freight Order [Page 34])



Check freight order status (see Checking the Status of Freight Orders [Page 35])



Load freight order into the system (see Loading Freight Orders [Page 36])



Print related documents (see Arranging and Printing Documentation [Page 37])



Monitor transit (see Monitoring the Freight Order in Transit [Page 38])



Handle exceptions (see Handling Exceptions [Page 39])



Deliver (see Delivering the Load [Page 40])



Set status to completed (see Setting the Status of Freight Orders [Page 41])

(C) SAP AG

33

Sending a Freight Order In this procedure, you send a freight order to a carrier. This procedure is optional since, in the automatic peer-to-peer tendering process, the quotation is sent to the carrier automatically. Variant 1 If you are using the cost distribution variant, you can ignore this procedure.

Procedure 1.


2.


3.

Choose

Subcontracting

Send to Carrier


.

Result The freight order is sent to the carrier.

(C) SAP AG

34

Checking the Status of Freight Orders You perform this procedure to check the status of freight orders.

Procedure 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Land Display Freight Order .


2.

Enter the freight order number and choose Continue.

3.

Go to the Statuses tab page and check the status of the following items: Field

Expected Value

Fixing

Open

Life cycle status

In Process

Execution status

Not Started

Subcontracting Status

Sent

Execution Block

Empty

If the Statuses tab page is not visible, right-click the folder icon to the right of the tab pages that are displayed. The system displays a list of all available tabs. You can select the Statuses tab page from this list.

(C) SAP AG

35

Loading Freight Orders You perform this procedure to load freight orders.

Procedure 1.

In your SAP Event Management system, choose Event Management Web Interface Search or call transaction /SAPTRX/EM_START .

2.

In the Tracking Scenario field, choose .

3.

In the Freight Order field, enter the freight order number and choose Apply .

4.

Choose Display Details.

5.

Choose Report All Expected Events.

6.

Enter the actual event date and time for Loading Start , Loading End , and Proof of Pick up.

7.

Select the row and choose Send .

Shipper Freight Order Transport Visb Process

Result In SAP TM, the status of the freight order is changed to In Execution.

(C) SAP AG

36

Arranging and Printing Documentation You perform this procedure to print a freight order document.

Procedure 1.


2.


3.

Choose Print and then Print Preview .


Result The freight order document is displayed as a print preview.

(C) SAP AG

37

Monitoring the Freight Order in Transit You perform this procedure to display and update the status of a freight order.

Procedure 1.


2.


3.

Enter the freight order number and choose Apply .

4.

Select the row containing your freight order and choose Display Details.

5.


6.

Enter the actual event date and time for Departure, Customs Clearance, and Arrival at Destination.

7.

Select the row and choose Send .

8.

In SAP NetWeaver Business Client (SAP NWBC) for SAP TM, choose Management Land Edit Freight Order .

9.

Enter the freight order number and choose Continue.


Freight Order

10. Go to the Execution Information tab page at header level. Check that all event dates have been updated.

Result Actual event dates have been added to the freight or ders in the SAP EM system and this information has been transferred to SAP TM.

(C) SAP AG

38

Handling Exceptions You perform this procedure to handle any exceptions that may delay or damage the freight order and report the event.

Procedure 1.


2.


3.


4.

Select the freight order and choose Display Details.

5.

Select the Delay checkbox to introduce a delay and choose Apply .

6.

Select the event for which you want to report a delay from the Delayed Event list; here you can also find other details related to the delay.

7.

Choose Send .

8.

If configured, an alert mail is sent to the “Responsible Person”.

9.

In SAP NetWeaver Business Client (SAP NWBC) for SAP TM, choose Management Land Edit Freight Order .


Freight Order

10. Enter the freight order number and choose Continue. 11. Go to the Execution Information tab page at header level. Check that the delayed event has been updated in the series of events.

(C) SAP AG

39

Delivering the Load Procedure 1.


2.


3.


4.


5.

Enter the actual event date and time for Unloading Begin, Unloading End , and Proof of Delivery .

6.

Select the appropriate rows and choose Send .


Result The status of the freight order and freight unit changes to Executed .

(C) SAP AG

40

Setting the Status of Freight Orders You perform this activity to check the status of the freight order after registering the final delivery.

Procedure 1.



2.

Enter the freight order number and choose

3.

Go to the Status tab page. Check that the Confirmation Status is now Confirmed .

4.

Choose Save.

Subcontracting

Confirm

.

Result The execution status of the freight order changes to In Process when execution starts. Once execution has been completed, the execution status of the freight order changes to Executed .

(C) SAP AG

41

Settle Freight Orders This business activity triggers the creation of a self-invoice or the verification of an invoice for subcontracted transportation services. Actual invoice verification takes place in SAP ERP. This business activity ensures that the amounts paid are correct for the logistical ordering and execution process. The activity requires the following procedures: 

Retrieve freight orders for settlement (see Retrieving Freight Orders or Bookings [Page 43])



Generate settlement documents (see Creating a Freight Settlement Document [Page 44])



Transfer the settlement document to SAP ERP for payment (see Transferring Freight Settlement Documents to SAP ERP [Page 45])



(Optional) Monitor the settlement process (see Monitoring Invoice Verification [Page 46])

(C) SAP AG

42

Retrieving Freight Orders or Bookings In this procedure, you retrieve the freight orders that you invoiced.

Procedure 1.

In SAP NetWeaver Business Client (SAP NWBC), choose Worklist Overview Freight Settlement Documents .

Freight Settlement

2.

Select the query for Freight Orders All .

3.

Search for and select freight orders for which you need to create invoices.

4.

Choose Calculate Charges to calculate freight charges.

Result The total amount on the Charges tab page contains a value and the document is ready for invoicing. Variant 1 Proceed as described above and save the freight order. In addition to the charge calculation, costs should be distributed automatically. Choose the Cost Distribution tab page and check whether the information is complete.

(C) SAP AG

43

Creating a Freight Settlement Document You perform this procedure to create freight settlement documents for freight orders.

Procedure 1.


2.

Select the Freight Orders link.

3.

Search for and select the freight orders that you want to invoice.

4.

Choose

Follow Up

Create Settlement Document

Freight Settlement

.

The freight settlement document appears in a new window. 5.

Choose Save All .

6.

Make a note of the new freight settlement document number.

Result The freight settlement document is created.

(C) SAP AG

44

Transferring Freight Settlement Documents to SAP ERP You perform this procedure to transfer a freight settlement document to your SAP ERP system.

Procedure 1.


Freight Settlement

2.

Choose Freight Settlement Documents All .

3.

Select your freight settlement documents and choose Save and Transfer .

4.

In SAP NetWeaver Business Client (SAP NWBC), choose Display Freight Orders .

5.

Enter a freight order number and choose Continue.

6.

Go to the Document Flow tab page.

7.

Check the purchase order and the goods and service acknowledgement under Successor Business Documents.

8.

Make a note of the purchase order and the goods and service acknowledgement numbers: __________

Freight Settlement Land

Variant 1 Check whether a service entry sheet has been created and note the number. Service entry sheet number: _________________

Result The freight settlement document has been transferred to SAP ERP and the invoicing status of the document has changed to Completely Invoiced .

(C) SAP AG

45

Monitoring Invoice Verification In this optional procedure, you monitor the invoice verification in the SAP ERP system. Variant 1 If you are using the cost distribution variant this procedure is mandatory.

Procedure 1.

On the SAP Easy Access screen for SAP ERP, choose Logistics Materials Management Purchasing Purchase Order Display or call transaction ME23N.

2.

Choose Other purchase document .

3.

Check the short text of the material; it should be the freight order with an item number.

4.

Go to the Purchase Order History tab page at item level.

5.

Check the services, material document number, and goods receipt number.

Result You can monitor the invoice settlement document that is transferred to SAP ERP.

(C) SAP AG

46

TM Config

Recommend Documents