Authorizations & Roles

Version Control

Table of contents

Objective and Scope
Scope
Reference
Definitions
Rates and Routes creation in FTL
Rates
Road
Multimodal
Route creation in FTL
Creation of the route
Translation
Route modification 

1 Objective and Scope

This document presents the general process for managing FTL rates and routes in the WP1 system.

Scope

This process applies to all tariffs and deliveries to be processed in the EMEA zone (except Gorzow in Poland), and exclusively with regard to sales transport.

References

SBS OTC – Process Expert Procedure

Definitions

SD : Shipment Document. This file is a summary of all the elements necessary for carrying out a transport: route, carrier used, point of departure, point of arrival, mode of transport used ...
SCD : Shipment Cost Document. It is generated during the implementation (= ex works) of the transport mentioned in the SD where the accrual of the transport cost is created.
SHIPPING POINT : This is a code assigned to each site according to the nature of the product transported and the type of transport used (Ex: Collonges = 0151).
TARIFF ZONE : Division of a country to avoid having to enter the same tariff as many times as there are departments in the same geographical area (Ex: ZT Rhône-Alpes can include 01, 38, 69, 42)
EMEA : Europe, Middle East and Africa
TRANSPORT PLANNING POINT (TPO) : This is a code assigned to each administrative entity. It defines which site is responsible for organizing and paying for each transport.
RDT : Route Determination Table. This table allows that a route populate automatically in an order.
GOOGLE FORM : It is a way that allows sites to make emergency route requests.

Rates and Routes creation in FTL.

Rates

|

Via e-room/ Gsheetl










TK11 ou TK14/
ZWOC90B

|



On road pack, we have two different TDA's to be managed: LTL (Less Truck load =small packages) and the FTL (Full Truck Load = complete truck).
In order to find the negotiation for FTL you need to follow the indications below:
Eroom => EMEA Logistics Purchasing => Road packed=>FTL Tender
Rate creation:
The rates are created for the flows defined in eroom as Primary and backup.
In FTL, we use the packaging code: 1055653 (SD LORRY 25 TO ENVIRON).
There are more packaging codes that can be found in eroom, but are rarely used:

Inside the FTL tender there are two modes of transport negotiated: Road and Multimodal.

To create a rate in SAP you need to enter TK11 and select a condition type :

• Condition type = Z999
• Click under key combination
• Select the key combination depending on the negotiation done by Purchasing

Road:

Dangerous and non dangerous goods

Multimodal:

Dangerous and non dangerous goods

• When the key combination is selected the data can be fill:

In the end and before leaving please don't forget to save the information.
The process of rates registration can be done in two aways :

• Manually, if there is only one entry
• In mass, by using a template for Mass upload.( Available in transaction ZWOC90D and ZWOC90B).

Route creation in FTL:

|

Via e-room/ Gsheet









Google form







0VTC/
ZWOC42A

|



The routes are only created for flows indicated as Primary.
The request for a route creation can come from a Google form( for spot deliveries) or via update on eroom.

• The first step before creating a route is to check if it exists already in SAP.

To check this information, there is a procedure to be respected.
Procedure :

• Open SQ00
• Select query ZW_RCS_OC
• click under 0VTC_INFO

FTL route structure:
The necessary Information to create a route :

• Service agent name
• Service agent code
• Lead time
• Transit time
• Factory calendar

The elements for route creation must be provided by Purchasing (Eroom/Gsheet) or by the GBU through a Google form.
Create route in SAP:
Enter transaction OVTC –Route definition:
Select the pencil to create
All routes have a specific codification depending on the mode of transport used, for road is "3" e.g: 300001. To respect the sequence of the existing routes we select the last route created by going to the icon positions:

Once the final route code is discovered we use the subsequent number e.g: If the last number is 304772, the new route will be 304773.
Designation of the route:
Calendar + service agent name + Lead time + Transit time
e.g : FR HOYER 3D 2D

A route for road packed doesn't have any connection point, therefore it can be used by other sites, with this we can affirm that all the road pack road are multisite (Can be used by other GBUs/sites)
The process of route creation covers two steps:

1. Creation of the route
2. Translation

Creation of the route:

• In order to create the route properly the information below must be fill in: 

Once the information is completely inserted, press enter and save

Translation

Once the route is saved it is necessary to translate to the other available languages. The process is made to ensure that route description appears on sales order/ purchase orders at the time that the route is used, regardless of the language chosen in SAP.
To start the process is necessary to go to the Icon Edit and select translation:

then a board will appear with several languages, it is necessary to select all. It can be made by pressing the Green button and Enter:

Once you press enter, a new board will appear with the countrys and the route selected. What is required is to copy paste the description to all the countries and save at the end.

Route modification :

It can happen to receive a request for a route modification by the GBUs. The requests are usually linked to a modification of lead time, transit time, service agent, factory calendar, etc...
Before doing the modification it is necessary to analyse possible options.
3 possible options:
🡺 The route already exists: In this case instead of creating a new one, the available route code is delivered to the GBU.
🡺 The route code doesn't exist: Check if the mentioned route to be modified is not being used by another GBU. (RDT or shipment document).
🡺If not, modify the route.
Before modifying a route it is necessary to see if it is not being used by another GBU, checking the route table determination( RDT), transaction ZWOC46A.


and execute

You can also use transaction VT11 to see all GBU, through the Shipment Document, that used that route:


Continue to the end of that page and then add the date you want to check

and execute