TPECPostOffices.xml file

This file contains Post Office definitions for Trading Manager. They represent logical inputs and outputs of data and there is no equivalent representation in TPEC. Since they are required, they are generated as follows:

• Get Post Office: A single post office is defined for all inbound and outbound data going into Trading Manager. Its nickname is hard coded to "EDI" and the path to the directory is defined in the TPEC2CM Configuration File.
• Outbound Put Post Office: A single post office is defined for all outbound data going out from Trading Manager to the external partners. Its nickname is hard coded to "EDO" and the path to the directory is defined in the TPEC2CM Configuration File.
• Inbound Put Post Office: One inbound put post office is defined for each unique combination of inbound Functional Group and Version/Release. This simplifies the implementation of the user maps need to convert inbound EDI data into the application format. The nickname is the two-character Functional Group ID plus one character representing an index for the Version/Releases found. These post offices are built from the TPEC Inbound Trading Specs. The conversion tool verifies that each Transaction and Version/Release combination is defined in Trading Manager.