Define Settings for Transportation Management

This document explains how you define the settings for the transportation management workflow.

Outcome

Settings for transportation management are defined for the following areas:

The process can be used to control a physical shipment throughout the dispatch flow or for customer orders, requisition orders, distribution orders and service orders.

Before You Start

The basic parameters for orders and order types are set.

Follow These Steps

Customer Order Type and Dispatch Policy

  1. Start 'CO Type. Open' (OIS010/G). The 'Dispatch policy' field must be filled in with a dispatch policy that contains the appropriate transportation management settings.

  2. Start 'CO Type. Update Field Selection' (OIS014) by selecting option 14 on the (OIS010/B) panel or entering H in the 'Panel sequence' field. You define routes and departures on the F panel.

  3. Start 'Dispatch Policy' (MWS010). Fill in the '160 Shipment assembly point' field on the F panel.

  4. Fill in the '240 Packing reporting method' field on the G panel.

  5. Fill in the '330 Automatic connection to shipment' field on the G panel.

  6. Fill in the '340 Point to connect delivery documents' field on the G panel.

Number Series

Start 'Number Series. Open' (CRS165). Use the help text in the 'Series type' field to guide the setup.

Note: Make sure that you set up these number series in the central (blank) division and that you provide enough 'room' between the start number and the final number for your future shipment numbers, etc.

Loading Platform

  1. Start 'Loading Platform. Open' (DRS016). Select a warehouse and fill in the 'Loading platform' field. Open the E panel.

  2. Fill in the Location, Description and Name fields.

  3. In (MWS410), you can use the OQLODO loading platform field in your views (CRS020) and sorting options (CRS021).

  4. Start 'Available Object Control Parameters. Open' (CMS016) if you want to define rules for automatic connection between delivery and loading platform. For loading platform, the MMAD7 field group should be selected. Set the values for loading platform in 'Loading Platform. Define Outbound' (MWS140).

Routes, Route Departures, Unloading Places and Exceptions

Route Selections

  1. Start 'Route Selection Field. Enter' (CRS727). The E panel is displayed.

  2. The Priority field indicates the order (1–10) in which a combination of object values is to be checked. 1 is the highest priority.

  3. The Field field is retrieved from 'Field Group. Display Permitted Fields' (CRS109). Here the 'DRKEY- Transportation planning keys' field group is used.

  4. Start 'Route Selection Table. Open' (DRS011). This can also be started by using F14=Select table in (CRS727).

  5. Depending on the keys defined in (CRS727), you can have up to four possible 'Start value' fields per priority entered.

  6. Specify your first priority in the Priority field. Fill in values in the 'Start value 1, 2, 3, 4' fields. Press Enter.

  7. Fill in the following fields on the E panel:

    • Route
    • Route departure
    • Selection method (crucial field)
      Note: The field help says 'reschedule in', which means schedule earlier in time, and 'reschedule out', which means schedule later in time.
    • Try lower priority
    • Departure days
    • Route departure days (displays the setup in (DRS006)).

Simulate Route Selections

The route pre-selection can have a complicated setup and it is important to test that the logic and basic data are correct. There is a simulation program to assist you, 'Check Route Departure (DRRTVRDE)' (MTS028).

The purpose of this program is to give the user a good tool for tests and simulation of route pre-selection.

(MTS028) has two primary tasks:

Document Handling

For more information on how to handle the documents in the transportation workflow, refer to Manage Delivery Documents and Labels.

Parameters to Set

Program ID/ Panel Field The field indicates …
(OIS010/G) Dispatch policy … a dispatch policy, which must contain the appropriate transportation management settings. See below.
(OIS014/F) Route … how routes and departures are proposed by default for a new customer order in the Route and 'Route departure' fields.
(OIS014/F) Route departure … whether the field heading and contents are displayed and whether the contents can be changed.
(MWS010/F) 160 Shipment assembly point … selecting and filtering possibilities in 'Delivery Tool. Open' (MWS410). You are not required to follow the settings in this field in the transportation workflow.
(MWS010/G) 240 Packing reporting method

… the packing reporting method. You do not have to perform packing if you will run the transportation workflow. However, if you want the delivery documents generated and printed, you must select packing alternative 1, 2, 3 or 4.

Instructions about packing are in the document How to Perform Packing.

Fill in the '260 Package numbering method' and '265 Automatic execution of packaging actions' fields.

(MWS010/G) 260 Package numbering method … whether automatic package numbering is used per delivery number.
(MWS010/G) 265 Automatic execution of packaging actions … whether packaging actions should be executed automatically as soon as a delivery is fully packed.
(MWS010/G) 330 Automatic connection to shipment … whether the test described in the field help is done to determine whether a new delivery number is automatically assigned to a shipment.
(MWS010/G) 340 Point to connect delivery documents … when delivery documents are automatically connected to a delivery.
(CRS165/B) Series type

… the series type. These must be selected:

05A SSCC sequence number (defined for each division)
06A Unit documents
06B Euro1 documents
06C Pro forma invoice
07A Delivery notes
08A Package number
13W Wave number
31X Waybill number
32A Shipment number
41A Consignee's reference number
(DRS016/B) Warehouse … the warehouse ID. Normally, the warehouse is used to distinguish different geographic locations within a company.
(DRS016/B) Loading platform

… a code that identifies the loading platform where the shipment is loaded.

The code is used for sorting and selection in 'Delivery Toolbox. Open' (MWS410).

(MMS005/F) Place of loading

… the geographical location where a shipment is loaded from a delivering warehouse.

Enter a place of loading when you enter a route. When you then create a separate shipment, this place of loading is transferred to the shipment.

The place of loading for each delivering warehouse is entered in (MMS005). Places of loading are defined in (MMS008).

(DRS005/B) Route type … the route type associated with the route. The route type is used to control the setup of the route and its application throughout the transportation process. There are five types to select from. Refer to the field help for a description of the different types.
(DRS005/E) Place of loading … the place of loading. The value specified here must match the place of loading specified in 'Warehouse. Open' (MMS005).
(DRS005/E) Delivery method … the delivery method. This method is used to create a shipment if you use transportation management. If you use the *SYSH setting in 'CO Type. Update Field Selection' (OIS014), the value in this field will be shown on the F panel in 'Customer Order. Open' (OIS100). Thus, the method of delivery is not retrieved from the 'Customer master' field, but rather from the route master file. In this case, the 'Delivery method' field cannot be edited on the (OIS100/F) panel. If you use *SYSL, on the other hand, this field can be edited in the order header.
(DRS005/E) Forwarding agent … the forwarding agent. The value in this field is retrieved from 'Supplier. Open' (CRS620). Customer type 5=Forwarding agent.
(DRS005/E) Transportation equipment … the transportation equipment. The value in this field is retrieved from 'Transportation Equipment. Open' (DRS013).
(DRS005/E) Transportation service ID ...the ID of a specific service that a forwarder supplies. This is used in the Simplified pack process. See How to Perform Packing.
(DRS005/E) Parameters shipment … the shipment parameters. If you activate these parameters, these fields will become mandatory when you handle the shipment. You will then have to enter this information if it is missing when you generate the transportation documents.
(DRS005/E) Accumulated … the total data connected to this route that is managed by the system. The values accumulated can be found in 'Route. Connect Unloading Places' (DRS021).
(DRS005/F) Stipulated internal lead time days/ hours/minutes … the picking and packing times that are deducted from the departure date to calculate the planning date. Based on the scheduled time of departure, this lead time is used to calculate the latest time when the goods to be shipped must be available in stock; that is, the planning time.
(DRS006/B) Route … the current route.
(DRS006/B) Departure … one or more departures that reoccur with a defined interval (for example, once a week).
(DRS006/E) Delivery method … the delivery method will be used when you create the shipment. The delivery method field in this program overrides the one specified for the route on the (DRS005/E) panel.
(DRS006/E) Forwarding agent … the forwarding agent. This field overrides the one specified on the (DRS005/E) panel.
(DRS006/E) Transportation equipment … the transportation equipment. This field overrides the one specified on the (DRS005/E) panel.
(DRS006/E) Transportation service ID

..the ID of a specific service that a forwarder supplies.

This is used in the Simplified pack process. See How to Perform Packing.

(DRS006/E) Day of deadline … how many days before the day of departure the locking of the shipment takes place.
(DRS006/E) Time of shipment locking … the time of locking (hh, local time), which describes the hour of the day when a shipment using this route departure should be locked.
(DRS006/E) Stipulated internal lead time days/ hours/minutes … the stipulated internal lead time. The value in this field overrides the one specified on the (DRS005/F) panel.
(DRS006/E) Load platform … a sorting option in 'Shipment. Open' (DRS100).
(DRS006/E) Departure day

… the departure day. This field is crucial because it shows on which days the departures can take place. You have seven positions, one for each day of the week. This setting will control the selection of the next possible route departure. Based on this departure date, the picking and packing time is deducted to get the planning date, and the transportation lead time is added to get the confirmed delivery date.

Example:

1001000 means that departures take place on Mondays and Thursdays.

If an order is entered for delivery on Tuesday, the system will reschedule to Thursday or Monday, depending on the setting in 'Selection method' field on the E panel in 'Route Selection Table. Open' (DRS011).

(DRS006/E) Day of arrival … the day of arrival, and is used for information purposes only.
(DRS006/E) Time of departure … the time of departure in hours. See 'Departure day' above.
(DRS006/E) Time of arrival … the time of arrival, and is used for information purposes only.
(DRS006/E) Valid From–To … the period during which the route departure is valid.
(DRS021/B) Unloading sequence

… the unloading sequence. This sequence is important for the printing of the loading list. Items that must be delivered first must be loaded last.

Example:

A route has three via destinations called City 1, City 2 and City 3. The sequence for this route is City 3, City 1, City 2. In other words, City 3 has the lowest sequence number and City 2 has the highest. This means that all deliveries to City 2 will be loaded first, while the deliveries to City 3 will be loaded last so that they can be unloaded first.

(DRS021/E) Place of unloading

… the place of unloading. One or more places of unloading can be entered. If the country code of this place of unloading differs from the country code of the place of loading (MMS008), then you have defined a route that goes abroad and different delivery documents will be generated.

Note: In the definition of the place of unloading, a time zone can also be entered to cover time zone conversion.
(DRS021/E) Unloading sequence

… the unloading sequence. This field is used to indicate which delivery address identity is the key to the unloading sequence for a certain route. The valid alternatives are:

0 = Postal address

1 = Unloading zone.

(DRS021/E) Transport lead time days/ hours/minutes

… the transportation lead time that will be added to the departure date/time to calculate the confirmed delivery date. This information is shown on the (DRS005/F) panel. Note: A local transportation lead time can be defined on the F panel in 'Route Selection Table. Open' (DRS011).

Note: Time is always expressed based on the place of loading. The system will calculate the time between the different unloading places.
(DRS021/E) Transport distance … the distance between the place of loading and this place of unloading. This is also summarized on the (DRS005/E) panel.
(DRS021/E) Via address … the Via address. When the goods do not arrive directly from your warehouse at the customer's warehouse, you can predefine these addresses in 'Via Address. Open' (CRS300). This field is used for information purposes only.
(DRS022/B) Unloading and loading sequence … the unloading and loading sequence. Depending on the unloading sequence on the (DRS021/E) panel, you can specify either the postal code or the unloading zone to direct the printout of the loading list.
(DRS007/B) Route and departure … the current route and departure
(DRS007/B) Valid from … the start date for the departure's exception.
(DRS007/E) Valid From–To … the period for the exception, which is crucial information.
(DRS007/E) Time of departure … the time of departure. Use this field if you want to use the same departure date but a different time.
(DRS007/E) Cancelled route departure

… the cancelled route departure. The valid alternatives are:

0 = Replacement

1 = Cancellation.

(DRS007/E) Replacing route departure … the replacing route departure, which you should enter if necessary.
(CRS727/E) Priority

… the order (1–10) in which a combination of object values is to be checked. 1 is the highest priority.

If the object values are not qualified according to the objects selected for priority 1, then values for objects selected for priority 2 are checked, and so on.

(CRS727/E) Field

… the field retrieved from 'Field Group. Display Permitted Fields' (CRS109). Here the 'DRKEY- Transportation planning keys' field group is used.

These keys will determine which route and route departure will be retrieved to calculate the planning date and the confirmed delivery date, based upon the selected departure date. The route and route departure will be entered on the customer order lines in (OIS101).

The keys are checked by the system from left to right and from top to bottom. The first hit found will determine the route and route departure used.

Note: It is crucial to get this setup right the first time because if you change the key values here, you will lose records in 'Route Selection Table. Open' (DRS011). Use priority 5 (not the highest and not the lowest priority) as a base.
(DRS011/B) Start value … the start value. Depending on the keys defined in (CRS727), you can have up to four possible 'Start value' fields per priority entered.
(DRS011/B) Priority … the priority. Fill in values in the 'Start value 1, 2, 3, 4' fields.
(DRS011/E) Route … the route, which is defined in (DRS005).
(DRS011/E) Route departure … the route departure. This field is not mandatory, but if you use it, then only this individual route departure will be used, even if there are more departures connected to the route in (DRS006).
(DRS011/E) Selection method

… the selection method. This field is crucial because it manages the rescheduling if there is no predefined route departure available for the requested delivery date. Read the field help for the valid alternatives.

Note: The field help says 'reschedule in', which means schedule earlier in time, and 'reschedule out', which means schedule later in time.

Back order route pre-selection

The route pre-selection for a back order will be performed as defined in 'Route Selection Table. Open' (DRS011).

For example, if you use selection method 1='Reschedule in', then you will in most cases not retrieve any valid results from the route pre-selection date calculation.

(DRS011/E) Try lower priority … whether it is possible to use lower priorities in the pre-selection in order to find the best route and departure.
(DRS011/E) Departure days

… the departure days. You can fill in this field if there is no route departure defined in (DRS006). On the right side of the panel, the 'Route departure days' field displays the setup in (DRS006).

If there are departure days defined in (DRS006), you can only leave out departures in this field. You cannot add extra departures.

(DRS011/E) Route departure days

… the days of the week for which the pre-selection applies.

The field contains seven positions. The first position is for Monday, the second for Tuesday, and so on. One alternative should be entered for each day of the week.

Different alternatives are valid for the field depending on whether only routes are used or whether both routes and departures are used. If the selection method 0 is selected for departures, then only routes are used.

When only routes are used, the valid alternatives are:

0 = No route on this day

1 = Route on this day

0 = No departures on this day

1 = Departures on this day

Blank = Departures on this day.

When departures are also used, the valid alternatives are:

0 = No route on this day

1 = Route on this day

0 = No departures on this day

1 = Departures on this day

Blank = Departures on this day.

Related topics