Product: Transaction Manager
Article Link:
A Trading Partner Map (sometimes referred to as a Transaction Type) is Transaction Manager's user-friendly version of an Electronic Data Interchange (EDI) Map that determines the structure of the Raw EDI data, displayed as an interactive user form that allows a user to easily view, edit, or create EDI compliant transactions without needing to know the underlying EDI structure.
By providing a Editable Form rather than straight EDI - any user can quickly identify the data they need to validate or modify simply by looking at the Field Name and its corresponding value rather than worrying about EDI Segments and Elements.
Raw EDI Displayed
Every Transaction within Transaction Manager is represented as an interactive displayable form. This form represents the Raw EDI that is actually being used to contain the data that is ultimately being traded with your Trading Partner.
When a Trading Partner sends a Purchase Order (850) for example - they are sending the PO # of MMC-30323 in what's known as an EDI Element which is linked to a specific Segment of the data (BEG03 - for the PO#). Transaction Manager utilizes the Transaction Types to build a form that displays the BEG03 into a Field called PO # instead making it much easier to find.
Formatting Display Values
You may notice that often a Dropdown Box or even a Number may display different in Transaction Manager's form view versus the Raw EDI. This is done automatically for user convenience by converting EDI Codes (often 2 or 3 digits) into human-readable formats, such as converting the Purchase Order Purchase from 00 to Original, the Purchase Order Type from DS to Dropship, or a Total/Amount field being displayed with a decimal when the Raw EDI excludes it.
These formatted values make it easier to see, and understand the values being passed without needing to cross-reference your Trading Partner specifications manually as it's already built inside of the Transaction Type inside Transaction Manager.
Trading Partner Maps
Every Trading Partner has their own unique set of Transaction Types which represent the provided EDI Maps given to us by the Trading Partner that dictates how the data is to be structured, formatted, and sent based on X12 EDI Standards.
Accessing Transaction Types
Navigate: Trading Partners β (Partner) β Preferences β Transactions
Within the Transaction Setup screen you can see all available Trading Partner Maps listed for every supported EDI Transaction Type that TrueCommerce has received EDI Mapping Specifications from the Trading Partner.
Variations
You may come across multiple of the same Transaction Types - each a variation of the core Transaction Type, for example a 4010- 856 - Ship Notice/Manifest - Pick and Pack might also have a 4010 - 856 - Ship Notice/Manifest - Pick and Pack Import variant.
These variations are created for specific use-case scenarios when the standard map may need some special adjustments to accommodate your Business Process while still maintaining the Trading Partner Specifications/Requirements defined in by their EDI Map Specifications sheet.
Common Variations
Transaction Type Variant | Description |
Import | Used to skip all Auto-Calculations performed on standard maps. Allowing full control of values such as Totals, Amounts, Discounts, and Shipping Quantities that are otherwise auto-calculated. |
New | New variants typically cover additional requirements imposed by a Trading Partner that do not apply to most common configurations |
P2P Turnaround | Peer-To-Peer (P2P) Turnaround Variants are used for special log needed when you need to use the Turnaround feature from a separate Trading Partner to create the transaction for this Trading Partner. |
It is always recommended to start with the standard version (defined by the simplest name) and switching to a variation only if required
rev 6/6/2025