This figure illustrates the entire TEI functionality.
The M3 TEI 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 list provides a brief explanation of the events in the M3 TEI solution.
One way to trigger the creation of a TEI transfer is to use a predefined event. When this event occurs, the TEI transfer document can be triggered. Examples of events are the printing of a picking list or the issue of a delivery.
Another way to trigger the creation of a TEI transfer is to use the manual triggering that is added in some functions. By selecting option 53 from the delivery toolbox (MWS410) or shipment toolbox (DRS100), you can create a TEI transfer including delivery information. From the package toolbox (MWS423), you can select option 53 to trigger a TEI transfer including package information.
The third way to create a TEI transfer is to do a manual selection in a report version and let the system create one or more transfers from the selection. When creating a TEI transfer for an outbound transaction, selection objects from shipment and delivery are used. For an inbound transaction, selection objects from either the delivery (DO) or the purchase order or purchase order line are used.
Event-based document control (EDC) is used to trigger a TEI transfer either from a system event (for example, a raise of status) or from a manual event (for example, using option 53 in the delivery toolbox). The EDC function is based on predefined events that are controlled by a selection table to detect when or whether a specific document should be printed. This function can be used for several documents and one specific document is the TEI transfer document.
The TEI transfer document is not a regular document but rather a trigger used to start the creation of a TEI transfer. This document will only contain basic information about either the event that triggered the creation or information from the selection made in a report version. The document number used for the TEI transfer document is 915. Only document variant 00 is standard but any value up to 99 can be used. It is recommended to use one combination of document number and document variant for each set of output information that will be used. For example, if package information should be sent to an external transportation system one document variant should be used but another document variant is used if delivery information is sent to a Transportation Execution Systems.
This function is central for managing TEI transfers. It will call other functions to trigger specific tasks. For example, when the function MYRTVTOC is called to retrieve an output control record and to create a TEI transfer header, then the function MTITHEPI will be called. When a TEI transfer is sent to an external system, it is done by this function which creates an MBM trigger and sends it to IEC.
Certain data that should be added to a created TEI transfer is object controlled. This data is retrieved from the MDOCTI table. The external transportation system that should receive a specific TEI transfer is one of the parameters that is managed in this function. This program will be called for every event triggered TEI transfer.
When a TEI transfer header is checked, added, or changed, the function MTITHEPI is used. Every managing of a TEI transfer in the MTITHE table is managed by this function.
In the same way as MTITHEPI manages TEI transfer headers, this function manages TEI transfer details. When a TEI transfer detail in MTITDE should be processed in any way, it is done by the function MTITDEPI.
This function is used to manage TEI transfer headers that are already created. From here a TEI transfer header can be changed, added, and manually sent to the external system.
This function is used to manage TEI details that are created and connected to a transfer header. TEI details can be added, deleted, or changed in this function.
When the TEI transfer has been sent to IEC, it will be used to trigger a predefined template, a IEC mapping. These templates will use several different APIs to retrieve transactional information from M3 in a sequence.
The output from the IEC mapping will always be in XML format. If the receiving system can manage XML files, there is no need for additional processing of the output file.
In those cases where the receiving system only can manage a flat file format, the XML file can be converted. This is done by using the flat file repository.