T72_TM800_BPD

SAP TM 8.0

SAP ERP 6.0 EhP 5

SAP II 3.6.1

October 2011

English

Broadcast Freight Tendering (T72)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Broadcast Freight Tendering (T72): BPD

Copyright

© Copyright 2009 SAP AG. All rights reserved.

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

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

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

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

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

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 Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

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

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

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and

© SAP AG Page 2 of 28


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.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

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> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose........................................................................................................................................ 6

2 Prerequisites................................................................................................................................ 7

2.1 Master Data and Organizational Data...................................................................................7

2.2 Roles..................................................................................................................................... 8

2.3 Preliminary Steps................................................................................................................11

3 Process Overview Table.............................................................................................................14

4 Process Steps............................................................................................................................ 16

4.1 Create Sales Order.............................................................................................................16

4.2 Create Outbound Delivery...................................................................................................18

4.3 Plan Shipment..................................................................................................................... 19

4.4 Tendering Status Overview.................................................................................................20

4.5 Check Tendering Progress of SAP TM Freight Order.........................................................21

4.6 Check E-Mail Inbox for RFQ Notification.............................................................................22

4.7 Accept RFQ......................................................................................................................... 22

4.8 Update Freight Order and Award Quotation........................................................................24

4.9 Check E-Mail Inbox for Tendering Result Notification.........................................................25

4.10 Carrier Commissioning (Print Freight Order)...................................................................26

4.11 Operational Shipment Execution.....................................................................................27



Tendering ERP LTL Shipment

1 Purpose

This tendering scenario is intended for shippers who perform transportation planning in SAP ERP, but who wish to use the tendering functionality of SAP TM. The focus is on sending an RFQ to possible carriers, then selecting a carrier on the basis of availability and submitted price, and subsequently awarding the business (i.e., submitting the freight order) to the carrier. The main benefits of this are as follows:

- You are able to contract the carrier with availability that is offering the best price - It improves carrier communication while reducing manual effort- You can ensure routing guide compliance by defining carriers in the transportation network

master data.



2 Prerequisites

2.1 Master Data and Organizational DataThe organizational structure and master data of your company were created in your SAP ERP system during implementation. The rapid-deployment solution processes are configured using sample master data as outlined below.

Using Your Own Master Data and Organizational Data

You can also use customized values for any material or organizational data for which you have created master data. You will need to adjust configuration to be able to perform the tendering processes of the rapid-deployment solution using your own master data and organizational data.

SAP ERP Organizational Data:

Org-Structure Value Description

Sales Organization

1000 Dom. Sales Organization

Distribution Channel

10 Direct Sales

Division 10 Product Division 10

Shipping Point 1000 Shipping Point 1000

Transportation Planning Point

0001 City 01

Customer Master Data:

Customer (SAP ERP)

Description Location (SAP TM) Business Partner (SAP TM)

TM_CUST05Customer 05, NV 89501

CU0000150005@RD5020 150005

Customer master data is created in SAP ECC and transferred to SAP TM via the Core Interface (CIF) as locations and business partners.

Material Master Data:

Material Description

TM_PROD02 Product 02

Carrier Master Data:



Carrier Description Communication Technique

User for Portal

Password

500000 Carrier 00 Portal, e-mail YT_CAR00 YT_CAR00

500001 Carrier 01 EDI N/A N/A

500002 Carrier 02 EDI N/A N/A

Transportation Zones

Transportation Zone Description

TM_ZONE11st level zone (Zone TM_464 assigned to this zone via zone hierarchy)

TM_8952nd level zone (Location TM_CUST05 assigned to this zone via postal code)

Transportation Lanes

Transportation Lanes

From Location To Zone Means of Transport

Carrier

SP1000@RD5020 TM_895 YT_LTL

500000

500001

500002

2.2 Roles

UseThe following roles must have already been configured to test this scenario with SAP NetWeaver Business Client (NWBC). The roles in this business process documentation must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user testing the scenario.

2.2.1 Business Roles in the scenarioIn this scenario some different departments and employees (internal and external) must work together in the course of the process. These are described in further detail in the following:

Sales Assistant (Internal)Normally, the business process starts with a sales order. In this case, one person from the sales department is responsible for the creation of sales orders from customers. This person therefore has direct contact with the customer and inserts all relevant information (i.e., customer-specific



information about loading and unloading times, preferred carrier etc.) in the SAP ERP sales order. If the customer makes any changes to the order (e.g. changes quantities), this person updates the sales orders in the system.

In the scenario described in this document, the (scenario) process will be started with an outbound delivery without any reference to a sales order. This is naturally just one of the many options available in the real business world, but the idea is to show you different alternatives.

Shipping Specialist (Internal)In this case, one employee from the logistics department is responsible for the creation of outbound deliveries. This person therefore inserts all relevant information in the ERP outbound delivery, including:

- Item information- Picking information- Loading information- Transport information- Dates and times- Shipment information- Foreign trade or customs information

If any changes occur for his outbound delivery, (e.g. the quantity changes), this person updates the outbound delivery in the system. If all relevant information is available in the system, the planning process can be triggered.

Transport Specialist (Internal)Once the outbound delivery is created in the system, another person from the transportation department needs to create the ERP shipment. This person is responsible for all transport-relevant information, such as:

- Own or external truck fleet information- Times and dates- Distance and durations- Printing all relevant transportation documents- Manual/automated transportation planning- Planning optimization- Relevant means of transport- Shipping type- Shipping conditions- Stages and hubs- Partner information- Tendering information - Etc.

This person collects all this information and afterwards creates the ERP shipment, which can include several outbound deliveries. Once the shipment creation process is complete, this person changes the status of the ERP shipment in order to hand over the shipment to the next responsible person, the tendering manager.

Tendering Manager (Internal)The tendering manager is the person responsible for the following tendering process. This person therefore sends out the shipment to one or more preferred carriers for tendering. During this process, the tendering manager will check the entire communication between his company and the



carriers. If the external carrier accepts the shipment request, the tendering manager will evaluate the incoming offers, select the best one, and send all relevant information to the winner of the tendering process. S/he will then cancel all other offers.

Customer Service Agent (External)The customer service agent is an employee from an external carrier company. This person is responsible for all incoming transportation requests from customers of this logistics service provider (LSP). This person therefore receives all relevant information from the external customer request and evaluates this document. If the LSP is able to provide trucks for this request, this person sends out an offer for this request. During this process, the customer service agent checks the entire communication between his company and the customer.

If the external customer accepts the offer, the customer service agent will receive an order from the customer by e-mail, fax, or EDI and will trigger all relevant steps at the company to process the order.

2.2.2 Technical Roles

SAP ERP:

Business Role Technical Name Process Step

Sales Assistant SAP_LO_SD_SALES_ORD_PROCESSING All steps performed in SAP ERP relating to sales orders

Shipping Specialist SAP_LE_OUTB_DEL_PROCESSING All steps performed in SAP ERP relating to outbound deliveries

Transport Specialist

SAP_LE_TMS_PLANNING All steps performed in SAP ERP relating to shipments

SAP TM:


Tendering Manager

/SCMTMS/TENDERING MANAGER Tendering Process

External:


Customer Service Agent

Portal User Tendering Process

These roles include the transactions required for the steps described in the process documentation in hand. You can work with your own roles if they contain the transactions mentioned in the Process Overview Table section.



2.3 Preliminary Steps

2.3.1 Adjust SAP GUI Settings to Display Technical Keys

To alter the display of dropdown list items, you should adjust the settings in your SAP GUI as follows:

1. Choose Customize Local Layout - Options or press Alt F12

2. Open folder Interaction Design

3. Select Visualization & Interaction

4. In the Controls section, select radio pushbutton Show keys within dropdown lists

5. Choose the OK pushbutton.

2.3.2 Contact Persons for E-Mail Notifications

To receive notifications for published freight RFQs, rejected quotations, and awarded quotations by e-mail, you must maintain the e-mail address of the user performing the process steps. The address must be maintained for the carrier’s contact persons.

In this scenario, you need contact persons with Internet users for the following carriers:

Carrier Contact Person (BP Number)

Name of Contact Person

E-Mail Address User Name / Password

500000 John Doe YT_CAR00 / YT_CAR00

Procedure to Determine Contact Person for a Carrier

1. Access the transaction for maintaining business partners by choosing:

SAP TM SAP Menu Master Data General Define Business Partner

Transaction Code BP

2. Choose Business Partner – Open or press SHIFT+F5

3. A dialog box opens: enter the business partner no. of the carrier for which you want to maintain a contact person.

4. Choose the Relationships pushbutton or press SHIFT+F1

5. The contact persons are displayed with description has Contact Person. Select the line and choose the Partner Detail pushbutton.

6. A dialog box appears displaying the ID and name of the contact person. Choose the Display pushbutton or press F7.

7. The business partner data of the contact person is now displayed. Check the Internal ID, Name, and E-mail Address fields and adjust the table above as required.



8. In the Display in BP role field, select BUP005 Internet user. Go to the Internet user tab page. Check the user name and adjust the table above as required.

The contact persons are created with an internal ID. The ID in your system will most likely be different to this. Therefore, please adjust the above table to your system settings.

The rapid-deployment solution also assumes that the usernames and password for the portal user are created using YT_CAR<2 digit carrier-no>. If the usernames and passwords in your system environment are created differently, adjust the above table accordingly.

9. Choose the Save pushbutton or press CTRL+S.

Procedure to Assign E-Mail Addresses

10. Access the transaction for maintaining business partners by choosing:

SAP TM SAP Menu Master Data e General Define Business Partner

Transaction Code BP

11. Choose the Business Partner – Open pushbutton or press SHIFT+F5.

12. A dialog box opens: enter the business partner no. of the contact person whose e-mail address you want to maintain.

Use the internal ID for the contact person’s business partner master record

13. Go to the Address tab page

14. Maintain the e-mail address that you want to receive e-mail notifications

15. Choose the Save pushbutton or press CTRL+S

2.3.3 Carrier Communication via EDI

The scenario assumes that an EDI connection is established for communication with carrier 01 and carrier 02. The rapid-deployment solution package is delivered with SAP II for which default partner roles have been configured. However, if you are not using SAP II and do not have another EDI connection established, you can still execute the scenario by simulating the carrier response.

Carrier Contact Person (BP Number)

Name of Contact Person

E-Mail Address User Name / Password

500001 Carrier 01 YT_CAR01 / YT_CAR01

500002 Carrier 02 YT_CAR02 / YT_CAR02

To do this, proceed as follows:



1. Access the SAP TM tendering personal object worklist (POWL) for open RFQs by choosing:

SAP NetWeaver Business Client (SAP NWBC)

SAP TM80 NWBC Freight Order Management Land Overview Tendering

Transaction Code NWBC

2. In the Active Queries area in the POWL, select query Open RFQs.

3. Identify the RFQ for which you need to create a quotation and select the line by choosing the first column.

4. Choose the Edit pushbutton. The RFQ is displayed in a new window.

5. Select the RFQ by clicking in the first column.

6. Choose the Create Quotation pushbutton. A new line is inserted in the table view. Maintain the response code and, if required, the price.

7. Select the line of the quotation and choose Submit quotation and save

8. Close the window

Carriers’ Responses in this ScenarioIf you want to enter manual responses for EDI carriers, proceed as follows.

Carrier / Tendering

Carrier 00 Carrier 01 (EDI) Carrier 02(EDI)

Broadcast Accept with Price Accept with Price Reject

Peer-to-Peer



3 Process Overview Table

Process Step Business Condition

Business Role Transactions Code

Expected Results

Create Sales Order New sales order is entered for a customer

Sales Assistant VA01

Create Outbound Delivery

Sales Order is due for delivery

Shipping Specialist VL01N

Plan Shipment The transportation is planned for due deliveries

Transportation Specialist

VT01N

Tendering Status Overview

Monitor current tendering processes

Tendering Manager NWBC Freight Order UI

Check Tendering Progress of SAP TM Freight Order

Check tendering Processes

Check E-Mail Inbox for RFQ Notification

Notifications were sent via e-mail and EDI


Accept RFQ Customer Service Agent

NWBC Freight Quotation UI

Update Freight Order and Award Quotation

All carriers have responded and/or the tendering deadline approached

Tendering Manager NWBC Tendering UI

Check E-Mail Inbox for Tendering Result Notification

Tendering has ended and the carriers are informed about the results


Carrier Commissioning (Print Freight Order)

The freight order is printed and faxed to the selected carrier

Tendering Manager NWBC Freight Order UI

Operational Shipment Execution

The truck arrives on the yard, and the transportation specialist performs check-in

Transportation Specialist

VT02N



Example Process Flow



4 Process Steps

4.1 Create Sales Order

UseThe sales representative enters a sales order for goods to be shipped to the customer. The customer has ordered a full truckload of goods. This is the starting point for the entire business process.

Procedure

1. Choose:

SAP ECC6.0 SAP Menu Logistics Sales and Distribution Sales Order Create

Transaction Code VA01

2. On the Create Sales Order: Initial Screen, enter the following data:



Order Type Sales Organization Distribution channel Division

OR 1000 10 10

3. Press ENTER to confirm your entries.

4. On the Create Sales Order: Overview Screen, enter the following data:

Sold-to-Party

PO Number Req.deliv.date Material Order Quantity

150005 Free text Actual date + one week TM_PROD02 5

5. Press ENTER to confirm your entries and confirm dialog box Change Invoice date: The billing date is re-determined.

6. Choose Goto Header Shipping

7. In the shipping overview, enter the following data: shipping Cond: 04 Transport Service


9. Save the document and note down the document number _____________________________

If you change the shipping condition, you will be asked if routes and shipping should be re-determined. In this case, choose Redetermine.



Result The sales order is created. Since the shipping condition is set to 04, the sales order is not transferred to SAP TM for planning. Instead, this process assumes that transportation planning is performed in SAP ERP.

4.2 Create Outbound Delivery

UseThe shipping specialist generates an outbound delivery with reference to the sales order. This will be relevant for transportation planning in SAP ERP.

PrerequisitesA sales order has been created.

Procedure

Typically, the outbound deliveries are created collectively, either using a background report or the delivery due list. However, to avoid unnecessary complexity, a single delivery is created for the sales order.

1. Choose:

SAP ECC6.0 SAP Menu Logistics Sales and Distribution Shipping & Transportation Outbound Delivery Create Single Document With Reference to Sales Order

Transaction Code VL01N

2. On the Create Outbound Delivery with Order Reference screen, enter the following data:

Shipping Point

Selection Date

Order

1000 Today + 1 week

Your sales order no. from above


4. Save the outbound delivery document by choosing Outbound Delivery Save.

5. Note down the delivery document number for later on during transportation planning.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

ResultAn outbound delivery was created that is relevant for transportation planning. The outbound delivery will not be transferred to SAP TM since shipment planning is performed in SAP ERP.



4.3 Plan Shipment

UseThe transportation specialist checks today’s delivery pool and creates an outbound shipment in SAP ERP for the previously created delivery. A default carrier is assigned to the shipment by assigning a route to the shipment. However, this default carrier will be substituted with an appropriate carrier determined using the SAP TM tendering platform.

By setting the tender status to New Offer, the transportation specialist starts the transfer to SAP TM and therefore the tendering process.

Prerequisites A transportation-relevant outbound delivery has been created in SAP ERP.

Procedure1. Choose:

SAP ECC6.0 SAP Menu Logistics Sales and Distribution Shipping & Transportation Shipment Create Single Documents

Transaction Code VT01N

2. On the Create Shipment: Initial Screen, maintain the following entries.

Transportation Planning Point

Shipment Type

0001 YT30 SAP TM Integration

3. Choose Edit Select Further Deliveries or press the F6 key.

4. On the select outbound deliveries screen, maintain the following data.

Field Data

Transptn Plang Date Today

Include deliveries in processed shipment

Uncheck the selection box

5. Process the delivery selection by pressing the F8 key.

6. In the lower area of the Create: Shipments and Deliveries screen, select the outbound delivery you generated in the previous step.

7. Assign the outbound delivery to the shipment in the upper area of the screen using drag and drop.

8. Move to the overview data of the shipment by choosing Goto Shipment Overview or press SHIFT + F4.

9. On the Deadl. tab page, choose the Planning pushbutton.

Check that the systems determined automatically based on Customizing contain the following data.



- Legs of the shipment on the Stages tab page

- Forwarding agent

- Route

- Dates and times of the shipment on header level, for instance Shipment start and Shipment end.

10. On the Stages tab page, select the row of the stage and choose the Stage Details pushbutton.

Enter Planning Times on TAB Duration and distance:

o Start: today + 1 week – 2 days

o End: today + 1 week

- Choose the Copy pushbutton.

11. Go to the Tender tab page.

12. Set the tender status to New Offer from Shipper.

13. Save the shipment by choosing Shipment Save or choose the save pushbutton.

14. Note down the shipment document number.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

ResultThe transportation specialist created an outbound shipment in SAP ERP to identify and subcontract an appropriate carrier. The shipment is transferred to SAP TM for tendering.

4.4 Tendering Status Overview

UseOn a regular basis, the tendering manager checks the personal object worklist for shipments from SAP ERP and their tendering status.

PrerequisitesA shipment that is relevant for tendering has been transferred to SAP TM.

Procedure1. Access the SAP TM tendering personal object worklist (POWL) for freight orders by choosing:




2. In the Active Queries area of the POWL, select query All Created from ERP Shipment.

3. On the top right of the query for ERP shipments, choose the Filter pushbutton.



4. In the Subcontracting Status column, set the value to In Tendering. All ERP shipments that are currently in tendering will be filtered.

5. Identify the freight order that was generated by the transfer to SAP TM of the shipment previously created in SAP ERP.

ResultBy checking all ERP shipments that were transferred to SAP TM for subcontracting, the tendering manager identified the previously created ERP shipment for which tendering has already started.

4.5 Check Tendering Progress of SAP TM Freight Order

UseIn SAP TM, the tendering manager enters the freight order that was created from the ERP shipment to validate the current tendering process.

PrerequisitesA shipment that is relevant for tendering was transferred to SAP TM.

Procedure

1. In freight order query All Created from ERP, select the line of the shipment that was created previously in SAP ERP and choose the Edit pushbutton or click on the link assigned to the underlined freight order number to open the freight order. The system opens a new window for the freight order.

2. After entering the freight order, go to the General Data tab page.

3. Verify that the means of transport YT_LTL has been assigned to the freight order according to the load smaller than xx.xxx LB.

4. Go to the Subcontracting tab page.

5. Check the following areas on the Subcontracting tab page.

- Sub tab page Tendering Overview displays the current tendering process status. The RFQ was sent to all broadcast carriers.

- Tendering Plan in the lower section of the screen is the origin of the current tendering process based on the tendering process settings derived from the LTL means of transport and the US region of the final shipment destination.

ResultThe tendering manager checked the current subcontracting status for the ERP shipment as well as the correct automatically determined tendering process settings.



4.6 Check E-Mail Inbox for RFQ Notification

UseThe contact person of carrier 00 / BP 500000 checks his/her e-mail for new RFQ notifications.

PrerequisitesThe e-mail address of the user performing the business process has been assigned to the contact persons for carriers as described in above.

The e-mail assignments must be completed before starting the process. The e-mails are sent during creation of the TM freight order because the notifications are sent automatically.

Procedure

1. Open your e-mail program (not part of the SAP applications)

2. Go to the inbox and open the e-mail message received from the tendering manager. The lower part of the e-mail contains an overview of the requested shipment, including the following data:

- RFQ number

- Shipment start date

- Shipment end date

- Means of transport

- Quantities/dimensions of the load

- Ultimate date and time for the expected reply

A link in the upper section provides access to the shipper’s Internet portal.

3. Note down the RFQ number.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

ResultThe carrier’s contact person received an e-mail providing the most important information about the requested shipment and a link to the shipper’s subcontracting platform.

4.7 Accept RFQ

UseThe carrier’s user accesses the shipper’s subcontracting Web platform via an Internet browser to accept the request at the date and time requested by the shipper.



PrerequisitesSingle Sign-On has been deactivated to permit access to the shipper’s Internet portal from the link in the e-mail. To deactivate Single Sign-On, adjust the following setting in Internet Explorer:

IE -> Tools -> Internet Options -> Security -> Customer Level-> Don t prompt for client certificate selection … -> Disable

If you use another browser, follow the specific instructions for your browser.

The user and the password described in paragraphError: Reference source not found must be known.

Procedure

1. Follow the link to the shipper’s subcontracting Web platform from the e-mail received from the shipper’s tendering manager. A new Internet browser window opens showing the logon screen of the SAP TM 8.0 Web portal.

2. Log on to the TM system as a carrier using the following login credentials.

Username YT_CAR00

Password YT_CAR00

3. Choose the Logon pushbutton. The NetWeaver Business Client user menu for the carrier’s Internet user opens.

4. Go to the personal object worklist by choosing: Freight Order Management Land Overview Tendering for Carriers.

5. In the Freight RFQs category, select query Open.6. Identify the new request for quotation based on the RFQ number noted down from the previously

received e-mail for RFQ notification.7. Select the row of the RFQ and choose the Edit pushbutton above the table to open the RFQ. A

new Internet browser window opens showing the RFQ data.8. Select the RFQ and choose the Create Quotation pushbutton. A new row appears in the

quotations table.

If the pushbutton Create Quotation cannot be selected, first choose Edit.9. In the Response Code column, select Accept from the dropdown list.10. In the Price column, enter 1294.21 USD.

11. To send acceptance to the shipper, select this line and choose the Submit Quotation and Save pushbutton from the Quotations table menu.

12. Choose the OK pushbutton to confirm the dialog box and send the rejection to the shipper. The system issues the success messages confirming that the freight quotation was consistent and that the freight quotation has been sent to the shipper.

13. Log off the system and log on again using your own user (not the carrier contact person’s Internet user).

ResultSince the carrier is able to provide the required vehicle resource at the requested date and time, the contact persons of carrier 00, 01, and 02 accept the request for quotation and submit the quotation to the shipper. (Process step 4.6.1 was executed in the external carrier system).



4.8 Update Freight Order and Award Quotation

UseThe tendering manager checks the freight order and analyzes the freight quotations received. First, he checks which carriers have responded to the RFQ: The contracted/preferred carriers included in the broadcast tendering have all accepted the RFQ.

The tendering manager must now select the best carrier for this shipment manually based on price in addition to other criteria, such as carrier reliability. In this business process, the tendering manager selects carrier 1 based on the price offered by the carrier.

Freight costs are calculated for the freight order when the carrier is selected

PrerequisitesAll carriers have responded to the RFQ.

Background job Process Quotations and Overdue RFQs evaluates the RFQ responses from carriers and starts valid follow-up actions relating to the tendering process settings. This program must have been scheduled for background processing as described in the configuration guide.

To expedite processing you can also start the program manually:

1. Choose:


SAP TM80 NWBC Application Administration Background reports – Process Quotations and Overdue RFQs


2. Choose the Execute pushbutton.

Procedure1. Access the POWL for freight orders by choosing:




2. In the Active Queries area of the POWL, select query Freight Orders - All Created from ERP Shipment

3. Choose the Show Quick Criteria Maintenance pushbutton.

4. In the Subcontracting Status field, set the value to 02 - In Tendering. This will select all freight orders currently in tendering.

5. In the Tendering Status field, set the value to 03 – Review Required.



Broadcast tendering is configured to run for two hours after sending the RFQ (maximum response time). If the maximum response time for tendering has not yet expired, the status is 02 – Published.

6. Choose the Apply pushbutton.

7. All freight orders for which tendering has ended, but no carrier has been awarded, are displayed.

8. Identify your freight order and select the freight order by choosing the displayed row.

9. Go to the freight order by choosing the underlined freight order number or choosing the Edit pushbutton. The freight order is displayed in a new window.

10. Go to the Subcontracting tab page.

11. Go to the Tendering Overview tab page.

12. Choose the quotation for carrier 500000 by selecting the line in the table view. Choose the Award Quotation – Award pushbutton.

If you select a quotation from an EDI carrier, you could also choose the function Award Quotation – Award & Send to award the quotation and send the freight order to the carrier via EDI.

13. Choose the Save pushbutton.

ResultThe tendering manager selected the cheapest carrier (e.g. 500000) based on the quotations from broadcast tendering and assigned it to the freight order. Saving the freight order updates the ERP shipment with the following information from the tendering process:

- The carrier who was awarded the business- The actual price of the shipment (only if a quotation was selected that included a price)- The tendering status

4.9 Check E-Mail Inbox for Tendering Result Notification

UseThe contact persons of the carriers will be notified about the tendering result. The carrier who was awarded the business receives a notification e-mail stating this. The contact persons of carriers 500001 and 500002 were not informed about the negative outcome of the bidding process.



PrerequisitesTendering has been completed and the freight order was awarded to a carrier.

The background program for sending notification e-mails is scheduled as a periodic background job (for more information, see the configuration guide).

Procedure

1. Open the e-mail program (not part of the SAP applications) for the contact person of carrier 500000.

2. Go to the inbox and open the e-mail message received from the tendering manager. The e-mail informs the carrier’s contact person of the tendering result. The lower part of the e-mail body also lists the following information:

- RFQ number

- Shipment start date

- Shipment end date

- Means of transport

- Quantities/dimensions of the load

- Ultimate date and time for the expected reply

A link in the upper section provides access to the shipper’s Internet portal.

3. Repeat steps 1-2 for the contact person of carrier 01 and carrier 02.

ResultThe contact person of carrier 500000 is informed of the tendering result.

4.10 Carrier Commissioning (Print Freight Order)

UseAfter the freight order has been awarded to a carrier based on the RFQ, the freight order is sent to the carrier to confirm the commissioning of the carrier. Note that this message does not constitute the final shipping instruction or bill of lading since not all relevant information (e.g. packaging, handling units) is known at this time.

If carrier communication is via EDI, the message is sent automatically if you selected Award & Send during step 12 of section 4.9.

- Print out/preview the freight order in SAP TM- The tendering manager sends the freight order to the awarded carrier by fax



PrerequisitesThe tendering process has been completed successfully and the carrier is assigned to the freight order.

Procedure1. Access the SAP TM tendering personal object worklist (POWL) for published RFQs by

choosing:




2. In the Active Queries area of the POWL, choose query Freight Orders – All Created from ERP Shipment

3. Select your freight order and choose the Edit pushbutton.

4. Choose Print – Print Preview

5. A dialog box appears showing the different documents you can print. Choose the required document, e.g. Create Road Waybill (U.S.) and choose the OK pushbutton

6. The document is displayed in a new Adobe Reader window. If desired, print the document and fax it to the carrier 00.

ResultYou have printed the freight order and submitted it to the carrier. The subsequent process steps are performed by the carrier: 4.10.1 Receive commissioning and 4.10.2 Send Truck as shown in the process flow diagram.

4.11 Operational Shipment Execution

UseThe truck arrives on the yard. The transportation specialist identifies the relevant shipment using the paperwork that the driver brings to the office and performs the check-in. In addition, the clerk verifies whether the information is complete:

- Correct carrier is assigned- Status of the shipment- Verify cost information

If everything is correct, check-in is performed. If any data is missing, the clerk notifies the transportation manager.

PrerequisitesThe shipment was updated with the tendering result.



Procedure

1. Access the Change Shipment transaction by choosing:

SAP ECC6.0 SAP Menu Logistics Logistics Execution Transportation Execution Change Single Documents

Transaction Code VT02N

2. On the Change Shipment: Initial Screen, enter the relevant shipment no. as defined on the paperwork provided by the driver (or as noted from above). Press the ENTER key.

3. On the Shipment Type Change – Overview screen, verify the correct carrier no.

4. Go to the Tender tab page.

5. Verify the price in the Actual Costs field.

6. Go to the Deadlines tab page.

7. Choose the Check-in pushbutton to confirm the check-in. Note that the execution date/time for Check-in is set to the current time.

8. Save your changes.

ResultYou have verified the data in the shipment and processed driver check-in. The next step would be to load the freight onto the truck and execute the shipment.
