Business Requirements and Solutions for M3 Transportation Execution Interface

This document provides an overview of the concepts and functional requirements to get an overview of how M3 Transportation Execution Interface (TEI) can be used.

Note: To support the described concepts and requirements, the implemented Transportation Execution Systems must contain such functionality.

Transportation Documents

Often a Transportation Execution Systems is required when transportation documents vary between different forwarders, resulting in numerous layout requirements. Another deciding factor is that a company's export is directed to different countries, all requiring different sets of documents.

The Transportation Execution Systems is used in one of two ways: as a black box with no user intervention where documents are printed automatically via the Transportation Execution Systems, or it is used to send available information from M3 and then manually add the missing information in the Transportation Execution Systems before requesting a printout manually.

The characteristics of the major Transportation Execution Systems are that they are linked to the forwarders used on the local market and have knowledge and functionality to produce all types of forwarder documents.

By using event triggers in M3 TEI, you can select the event that suits the implementation and trigger a push of information to the Transportation Execution Systems at the right moment. If the event triggers do not work for you, use the manual events or the manual TEI creation function.

Note:  Configuration Recommendations

The event triggers that are recommended to use for transportation documents are:

  • RELEASE_PICK
  • DELIVERY_ISSUED or DELIVERY_CLOSED or DELIVERY_INV
  • SHIPMENT_ISSUED or SHIPMENT _CLOSED or SHIPMENT _INV

If the event triggers don't work use any of these manual events triggered by option 53 'Trigger TEI'.

  • MANUAL_PACKAGE (MWS423)
  • MANUAL_DEL (MWS410)
  • MANUAL_SHP (DRS100)

If the manual events also don't work for you, use the manual option to create a TEI transfer via 'TEI Transfer. Manually Create' (MYS510).

The type of Transportation Documents with configuration requirements are listed in the following

Hauler Integration

Hauler integration involves activities that occur before, during, and after the actual transport assignment occurs. Often B2B messaging is used to integrate consignor, hauler, and consignee.

A possible scenario for the transportation process and the information exchanged between consigner, hauler, and consignee:

The process described above covers a wide area where the Transportation Execution Systems on the market covers some or all activities. Some information flows are managed solely inside the Transportation Execution Systems and some are managed in the Transportation Execution Systems combined with interfaces to the backbone ERP.

The list below gives an overview of what you can achieve with M3 TEI combined with a Transportation Execution Systems that has such function built in.

Note:  Configuration Requirements

The event triggers that are recommended to use for hauler integration depends on the activity. See activity sections for recommendations.

If the event triggers don't work use any of these manual events triggered by option 53 'Trigger TEI'.

  • MANUAL_DEL (MWS410)
  • MANUAL_SHP (DRS100)

If the manual events also don't work for you, use the manual option to create a TEI transfer via 'TEI Transfer. Manually Create' (MYS510). Refer to section 4 for details regarding MYS510 and manual decision to create TEI transfers.

Customs Integration

Customs integration involves activities that occur before the actual export or import assignment occurs. Often B2B messaging is used to integrate consignor and customs authorities.

Support for customs processing is part of some Transportation Execution Systems, but not all. Quite often the functional requirement is specific to the markets to which you export or import.

The list below gives an overview of what you can achieve with M3 TEI combined with a Transportation Execution Systems that has such a function built in.

Note:  Configuration requirements

The event triggers that are recommended to use for customs integration are so different comparing customs declaration and bonded warehouse.

If the event triggers don't work use any of these manual events triggered by option 53 'Trigger TEI'.

  • MANUAL_DEL (MWS410)
  • MANUAL_SHP (DRS100)

If the manual events also don't work for you, use the manual option to create a TEI transfer via 'TEI Transfer. Manually Create' (MYS510).

Track & Trace

Track & Trace is a collection of features that enable different parties such as consignor, hauler, consignee, and final consignee to monitor a shipment and its present status.

When the transportation process has started, it is vital to be able to track where a certain parcel or shipment is located. Such a process requires both tracing capabilities and detailed reporting. The use of RFID, bar code scanning, and so on is important for enabling a track and trace process.

Related topics