TEI transfer entities

This section describes the entities included in TEI and their relation to already existing entities.


The TEI domain is oriented around the TEI transfer entity that is the result of a request for download of transportation related information. To each TEI transfer relations exist related to either outbound or inbound logistics with their respective entities.

Related entities such as shipments, deliveries, delivery lines, packages, purchase orders, and purchase order lines are created inside M3 based on the outbound and inbound process flow. The creation of the involved entities is configurable and has variations based on the flexibility when configuring the M3 product.

Event-based document triggers that are selected by the user automatically initiate a TEI transfer when an event occurs. Selected event triggers are chosen considering the normal processing activities inside M3. An example of such trigger is when a shipment is closed and no further deliveries will be added to the shipment. Another example is when a delivery is issued and all picking lists for a delivery number are issue reported. Alternatively, TEI transfers can be manually initiated allowing for user-defined grouping outside normal grouping identities such as shipments, deliveries, and purchase orders.

Entities outline

The following entities outline contains some simplifications regarding the connection between a package and a delivery line and the relations to the picking list entity.

TEI Transfer Entities Description



TEI Transfer

Represents a request to download a set of information from M3 related to the TEI.

The TEI Transfer holds several attributes with the purpose to represent key information for each request to download transportation information. These attributes are:

Message direction, Direction, Transfer ID, Status, Event, Event Key, Document Number, Document variant, partner level.

Document Definition

Represents each M3 document number and document variant with program used to create document.

The integration to a Transportation Execution Systems is represented by document number 915 but several document variants (00 - 99) can be used. Document variants are used to enable several integration points in the dispatch flow depending on what information that is needed at what stage in the process. One example would be to send label information when picking lists are released as variant 00. Later when the Delivery is issued variant 01 is used to send more information regarding all transport and customs documents.


Available detectable events in the Supply Chain Execution (SCE) and Purchase Order Processing (PUR) process. Each event holds a list of allowed documents for the event. Some events will allow for and initiate a TEI transfer. For allowed events, see 'TEI Transfer Events'.

Document Trigger

Represents the combination of a detectable event, sequence number and object combination. Points at one or several document numbers and document variants to be triggered when the event occurs for the defined objects.

Document Output Control

Holds several control information related to the TEI document number and document variant.

The control information includes e.g. identities, number series, document number and variant, transfer and package IDs and transfer variants.


A Shipment collects a number of Deliveries that share the same characteristics regarding Departure date/time, Mode of delivery, Forwarder, Route, transport equipment, etc.


A Delivery collects a number of order lines that share the same characteristics regarding Consignor, Consignee, Departure date/time, Terms of delivery, Mode of delivery, Forwarder, Route etc.

Delivery line

A specific delivery line categorized by order category (Customer order, Distribution order, Requisition order or Manufacturing order). The delivery line specifies the item number and quantities. It's linked to and is a result of an order line created in each order categories' order entry function.

Pick list

Represents each individual picking list created out of one delivery. Different rules, system defined and user defined, applies for how to split a delivery into several picking lists. The timing of stock entry and allocation can also result in split picking lists per delivery.


Represents each physical package to be shipped (CO/DO/RO) or received (DO). The package either contains items, other packages or a combination of both. Holds information about the physical attributes (weight, volume, etc.) connected to a package.

Package Group

Represents a group of packages sharing the same characteristics regarding packaging or packaging group. The grouping can be requested with Delivery, Shipment or Transfer ID as grouping level.

Purchase order

Represents a purchase from a specific supplier.

Purchase order line

Represents the item to be purchased and quantities.

Purchase order line transaction

Represents each reporting transaction made against a PO line after the order line is entered. One example is a goods receipt transaction.

Related topics