Scenarios for Using M3 Transportation Execution Interface

This document describes the available inbound and outbound logistics for M3 Transportation Execution Interface (TEI).

Overview

The major ERP systems on the market do not normally provide the depth of functionality as the Transportation Execution Systems do. To do so, the ERP vendors need to invest time and knowledge in a vide variety of market requirements. This situation leads us to the reasons to invest in ERP and Transportation Execution Systems integration. The information to exchange between M3 and the Transportation Execution Systems is related to transactional information that is exchanged in the latter part of the supply chain execution process. The Transportation Execution Systems should normally not have the possibility to reschedule orders, shipments, or deliveries. Planning capabilities are related to strategic or operative planning as described earlier. The initial integration point is established after the proactive shipment and delivery planning is finalized in M3. The final point of integration is placed when all documentation required for a physical delivery is produced. Integration capabilities related to post-processing is not a part of the TEI interface.

The figure displays business transactions that can be exchanged between M3 and a Transportation Execution Systems. The transactions in italics (upload) are currently not included in TEI solution.

M3 Transportation Execution Interface (TEI) Exchanged Business Transactions

Outbound Logistics Process

The relation between a Transportation Execution Systems and the outbound supply chain execution (SCE) process is normally started after the picking list is released and packages are created inside M3. This should be considered as the initial integration point.

The chosen initial integration point varies among users but is based on the dispatch process configuration and the functionality that should be managed by the Transportation Execution Systems.

Several additional integration points can be used depending on when documents must be produced and when forwarder integration and/or customs integration is required.

One example of how the outbound SCE process in M3 can relate to the process in a Transportation Execution Systems:

Note: M3 BE currently does not offer support for the upload of information. The main information to upload are identities and status information created in the Transportation Execution Systems. Uploading this information will enable tracking both in M3 and in the Transportation Execution Systems.

Inbound Logistics Process

The relation between a Transportation Execution Systems and the inbound supply chain execution process is normally started when the shipment is confirmed from the supplier (external PO or internal DO).

The chosen initial integration point varies among users but is based on the characteristics of the inbound process and the functionality that should be managed by the Transportation Execution Systems. A Transportation Execution Systems is normally used to manage import and customs declaration for inbound logistics.

Several additional integration points can be used depending on when the customs documents must be produced and when customs integration is required.

One example of how the inbound SCE process in M3 can relate to the process in a Transportation Execution Systems:

Note: M3 BE currently does not offer support for the upload of information. The main information to upload are customs identities and customs status information created in the Transportation Execution Systems. Uploading this information will enable tracking both in M3 and in the Transportation Execution Systems.
Related topics