Table of Contents

Objective
Scope
Definitions
Entry of Rates and Route Creation
Rate Creation Dry Bulk/Liquid bulk:
Liquid bulk rate:
Route creation:
Route modification :
3 [ possible options:|#_qmovi5vnslp0]

Objective

This document presents the general process for managing Bulk transport rates and routes in 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.

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
DG and NDG : If we are dealing with a Dangerous Goods or Non Dangerous Goods flows

Entry of Rates and Route Creation

|


Via e-room/ Gsheet






TK11 or TK14/
ZWOC90B

|

Rate Creation Dry Bulk/Liquid bulk:

Creation of new rate:
The rates are created for the flows defined in eroom as Primary and backup
Before creating a new rate it is necessary to check if it already exists in SAP through TK13

• Eroom => EMEA Logistics Purchasing

1. Dry bulk

List of packaging codes used:

The rate is created in SAP by entering TK11:

Depending on the information in eroom more specific in column " Currency/Unit" we may have two type of condition type:



-Condition Z981: lump sum price has a unique value of rate regardless of the quantity shipped.
-Condition Z982: Price per ton, the rate has a minimum invoice price and a price per tonage.( Use scale Id: 207916)
On Dry bulk we can find two modes of transport, Road and Multimodal. Depending on this, we select the following key combination:











Rate registration:
Line 3 and 4 are used for multimodal transport, represented with shipping condition AV:

• Shipping type
• Service agent
• Destination country
• Packaging material
• Shipping point
• Destination postal code
• Shipping condition

Line 6 and 7 are used for road transport:

• Shipping type
• Service agent
• Destination Country
• Shipping point
• Target postal code
• Packaging material

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

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

Liquid bulk rate:

Creation of new rate:
The rates are created for the flows defined in eroom as Primary and backup
Before creating a new rate it is necessary to check if it already exists in SAP through TK13

• Eroom => EMEA Logistics Purchasing

liquid bulk :
List of packaging codes used:

Note:
The process of rate creation in liquid buk is the same as Dry bulk with two modes of transport, following four key combinations available in condition types: Z981 and Z982. The only difference lies on the packaging codes.

Rate creation in mass.

The process of rate creation in mass is done when there is a significant amount of rates to be updated at the same time. For this we use transactions ZWOC90D and ZWOC90B.
ZWOC90D- Extraction of the template in an excel file:





Selection of the key combination preceded the entrance of the data necessary to create the template (usually the information added is a rate created in SAP):

Once the information please press execute.
After pressing execute a board with two information will appear, always select Pre-filled sheet:

The file is generated with the information previously entered in SAP:


The following step is to entered the new rates and save in two formats:




The excel workbook to have the information in excel in case you need to check the information added. And the Unicode text because is the format read in SAP to upload the rates.

ZWOC90B- Upload rates in Mass.
To complete the process of rate registration in Mass you need to upload the file saved in Unicode Text. For this,write the transaction in SAP and press enter. A board will appear and here you must add the following information:

• Condition type: Z982 or other condition type.
• File Header Line Number: In this information you always put "2", because it is when the system will start to read the rates.
• File name: The file with the rates saved in Unicode text.

To finish the process press execute.
In order to have the rates uploaded with success in SAP you must get the following information:

Route creation:

|

Via e-room/ Gsheet












Google form








0VTC/
ZWOC42A

|

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

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

1. 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

1. 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 after 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 as shown below 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 requested modifications it is necessary to analyse possible options.

3 possible options:

🡺 The route already exists and in this case instead of creating a new one and double, 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.( TDA or shipment document).
🡺If not, modify the route itself.
Before modifying a route it is necessary to see if it is not being used by other GBU by checking the route table determination( TDA), transaction ZWOC46A.

and execute