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:

  • Customer order type and dispatch policy
  • Number series
  • Loading platform
  • Routes, route departures, unloading places and exceptions
  • Route selections
  • Document handling.

The settings can be used:

  • To control a physical shipment throughout the dispatch flow
  • For customer orders, requisition orders, distribution orders and service orders

The following tables are updated:

  • Shipments are stored in the DCONSI table.
  • Routes are stored in the DROUTE table.
  • Route dispatches are stored in the DROUDI table.
  • Connections between shipments/deliveries and documents are stored in the DDOCUX table.

Before you start

The basic parameters for orders and order types are set.

Follow These Steps

  1. Settings in Customer Order Type and Dispatch Policy

    The 'Dispatch policy' field must be filled in with a dispatch policy that contains the appropriate transportation management settings.

  2. Number Series Settings

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

  3. Loading Platform Settings

    A loading platform is the place where the shipment is loaded. The code is used for sorting and selection in 'Delivery Toolbox. Open' (MWS410). You can also define rules for automatic connection between delivery and loading platform in 'Available Object Control Parameters. Open' (CMS016) and 'Loading Platform. Define Outbound' (MWS140).

  4. Route, Route Departures, Unloading Places and Exceptions Settings

    A route always has a place of loading and may have one or more places of unloading. Routes do not have to have unloading places. In that case, the route is called an open route.

    The route's place of loading must match the place specified in 'Warehouse. Open' (MMS005). The route and route departure are retrieved by the system (connected to a CO line) via the settings on the F panel in 'CO Type. Update Field Selection' (OIS014) and on the E panel in 'Route Selection Table. Open' (DRS011).

    Depending on your system calendar (CRS900) and the reception days at the customer (the customer's calendar), you can define route departure exceptions. There are two alternatives:

    • Cancel the departure
    • Reschedule the departure to another time or select another route departure instead.

  5. Route Selections Settings

    The route selection setups determine rules for how the system should select routes when a customer order line is created (that is, a delivery is created).

  6. Document Handling Settings

    Delivery documents are either manually or automatically connected to a delivery and shipment. The documents are actually connected to the deliveries. Deliveries are connected to a shipment, which results in documents being indirectly connected to the shipment.

    Note: Transportation management is no longer required to generate delivery documents. The only condition to get delivery documents is packing. No packing means no documents. Packing is set in 'Dispatch Policy' (MWS010) in the '240 Packing reporting method' field. Dispatch policy is connected to 'CO Type. Open' (OIS010) and 'Req/Distr Order Type. Open' (CRS200).
Related topics