Transportation Management

Transportation management is a tool that is used to manage all outgoing shipments. A shipment is your delivery placed on one physical truck/train/boat or any other method of delivery. A shipment can also contain pick-up deliveries for customer returns that should be picked up, or pick-up deliveries for transportation orders to make sure that the vehicle is arriving on the departure/delivery address at the correct time.


A shipment is picked, packed, reported, and shipped.

The following tables are updated:

Before you start

No prerequisites are needed.



Shipment in M3 is defined as a number of delivery numbers connected to one shipment. Use of shipment means that the dispatch flow (a number of delivery numbers) is controlled by the shipment. This is known as transportation management.

Transportation management: All releases controlled by shipment

Shipment (DRS100)

Customer order lines from different customers and for different delivery addresses (different deliveries in M3) can be added to a shipment, assuming that the places of unloading for these customer orders are defined on the shipment’s route setup.

If you do not want to track the progress of a physical shipment, then you should not use transportation management. Just issue the goods using the process described in Dispatch Handling. That flow is simpler than the transportation flow because there are fewer steps.

Transportation management works seamlessly together with the following areas:

Customer orders transaction type (3)

Requisition orders transaction type (4)

Distribution orders transaction type (5)

Manufacturing orders material issue.

Customer order returns

Transportation orders


Routes are used to define route departure, place of unloading, unloading sequence, lead time, etc. Route types are used to control the setup of the route and its application throughout the transportation management.

Every element does not need to be entered in the system to use route/route departure. For example, routes do not have to have unloading places. In that case, you create a route with route type 1=Open route.

A route always has a place of loading, and may have one or more places of unloading. The place of loading must match the place defined in ‘Warehouse. Open’ (MMS005). If the place of loading and the place of unloading, as defined in ‘Place. Open’ (MMS008), are in the same country, the transportation documents will be different than if these places are situated in different countries. If the route is a domestic route, another CMR document will be generated. Note that in the definition of the places, a time zone can be entered to cover time zone conversion.

The route and route departure are retrieved by the system via the settings on the F panel in ‘CO Type. Update Field Selection’ (OIS014) and ‘Route Selection Table. Open’ (DRS011).

The code for the route can, for example, be geographical (Spain, Sweden, etc.) or it can be named after the forwarding agent that carries out the transport operations.

Document handling

Delivery document(s) are connected to a delivery. The following standard documents can be connected to a delivery:

Delivery numbers uses

Shipment number uses

A shipment number contains several delivery numbers connected to one shipment. Use of a shipment number means that the dispatch flow (a number of delivery numbers) is controlled by the shipment. This is known as transportation management.

The system can be set up to automatically assign new delivery numbers to a shipment. The test that follows determines whether this automatic connection should be made.

All of the following statements should be true:

Back order preselection logic

Back order deliveries have been changed to respect route preselection logic. The requirement that the new solution meets is the possibility to reschedule a back order to the next best possible departure occasion. This is activated by performing so-called route preselection for any action in the dispatch flow that triggers creation of a back order delivery number.

Before this functional change was performed, a back order delivery was always placed on the same departure date and time as the original delivery number. This caused inaccurate departure dates and times and transaction dates and times. Moreover, no consolidation of back order deliveries to one future delivery was performed.

The following dispatch flow action may create a back order:

The back order delivery number that is created will be connected to the route, route departure, departure date and departure time that the route preselection logic calculates based on the point of time when the back order is reported. Normally this would find the same route but possibly a new route departure number, and most likely a new departure date and time will be calculated.

The rescheduling of the back order delivery will also affect the calculation of the transaction date and time, presented in 'Delivery. Open Toolbox' (MWS410/E), that affects the automatic picking list creation.

The rescheduling will not change any information on the underlying order line (CO/DO/RO/MO). The route, route departure, departure date and departure time will keep the original values.


Related topics