M3 Business Engine Administrator's Guide for Transportation Execution Interface (TEI)

Purpose

The purpose of the M3 Transportation Execution Interface (TEI) is to enable an interface where transportation and customs information can be exchanged with third-party best-of-breed applications or external partners using B2B messaging.

The reasons for using a Transportation Execution Systems vary, but are normally caused by variability or high volumes in one or more of the areas above. In some cases, the focus is on outbound logistics while other companies encounter variability and high volumes for inbound logistics. Requirements for customs declarations are stipulated by suppliers or customers in countries and trade unions that require customs procedures.

A Transportation Execution Systems can be provided as a standalone product or can be included as one part of a Transportation Management System (TMS). A Transportation Management System covers a wider scope than a Transportation Execution Systems. The following table describes a Transportation Management System.

Audience

This document provides general tips and advice. The primary target group is Infor consultants and customer "super users". Some M3 experience and knowledge is important to fully understand the concepts in this document.

Note: This document does not describe the details of M3 Interface (MI) programs and their transactions, such as which files and fields are required and how they are used. For a detailed description of M3 Interface programs and their transactions, see the API Repository in M3 API Tools.

Limitations

These listed items are known limitations:

Introduction to Transportation Management Systems

Transportation Management System consisting of Transportation Planning Systems, Transportation Execution Systems, and a Transportation Reconciliation Systems. Each area is divided into the functional content included. The Transportation Execution Systems is put into a wider perspective:

Transportation Management Systems

Transportation Planning Systems

Transportation Execution Systems

Transportation Reconciliation Systems

Strategic Planning

Operative Planning

Scheduling

Shipment Execution

Freight Management

Performance Measurement

  • Demand based Route Optimization
  • Transportation Network Planning
  • Consolidation
  • Load Building
  • Freight Shopping
  • Delivery Time & Freight Cost Optimization
  • Reactive Scheduling
  • Deviation Handling
  • Document Handling (Paper or B2B)
  • Forwarder Integration
  • Customs Integration
  • Freight Auditing
  • Freight Invoice Entry
  • Freight Claims
  • Carrier Performance
  • Delivery Performance
  • Fill Rate

Scenarios for using TEI

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.

M3 Transportation Execution Interface (TEI) exchanged business transactions

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.

For more detailed information on the available inbound and outbound logistics, refer to Scenarios for Using M3 Transportation Execution Interface.

Business requirements and solutions

The primary goal of M3 TEI is to offer M3 customers the possibility to use third-party Transportation Execution Systems (TES) that manage the following:

For more details and configuration recommendations, refer to Business Requirements and Solutions for M3 Transportation Execution Interface.

TEI architecture

The current solution is push-oriented, which means that the information is created within M3 and can be processed, viewed, and changed before it is sent to the external system. This solution enables a flexible, pull-oriented information flow of transportation information together with Infor Enterprise Collaborator (IEC). This means that the integration is more flexible and the data sent to a TEI system will be pulled from M3 via IEC by using M3 APIs.

The following figure illustrates the entire functionality.

M3 TEI solution - overview

For more details, refer to Overview of TEI Architecture.

TEI Transfer triggers

The current solution offers the following TEI Transfer Triggers:

For more details on Transfer Trigger settings, refer to M3 TEI Transfer Triggers.

API overview for the TEI solution

The following figure illustrates the most common APIs involved when TEI is implemented.

M3 Transportation Execution Interface (TEI) API overview

The different API transactions available for the Transportation Execution Interface (TEI) are described in detail in this document: API Overview of M3 Transportation Execution Interface

For detailed description about M3 Interface programs and their transactions, refer to the API Repository in M3 API Tools.

M3 BE 15.1 Java

Note: In order to trigger the sending of TEI information from M3 BE to an external transportation system, the settings listed under the TEI Transfer Triggers topic must be met.

The following program flow charts illustrate the main functions, functional components, and tables involved when performing any of the four workflows.

The first two flow charts details the master data functions and their relations. The third flow chart describes workflow that involves transaction management.

Master data program flow – TEI Trigger Control

Master data program flow – TEI Output Control

Transactional program data flow

Data model

The data model contains key fields to describe the key relationships for basic understanding.

Related topics