...
Design: Create transaction in Adeptia Connect to convert data
Configure: Define TransitionTransaction
To Create a an Outbound Transition Click Transactions > Templates.
On the Templates screen, navigate to the Outbound Template
...
Select Network and Partner
...
EDI Configuration Example:
EDI Standard | EDI Standard Version | Association Assigned Code | Transaction Set Code |
---|---|---|---|
EDIX12 | 4010 | ACMEEDI | 850 |
EDIX12 | 5010 | XYZEDI | 810 |
EDIX12 | 6020 | ABCEDI | 856 |
EDIX12 | 4010 | SUPPLYCO | 855 |
EDIX12 | 5010 | PARTNEREDI | 830 |
EDIX12 | 6020 | TRADECO | 865 |
In the above table:
EDI Standard: Remains EDIX12 for all entries, indicating the standard being used.
EDI Standard Version: Includes different versions like 4010, 5010, and 6020, showcasing variations across releases.
Association Assigned Code: Provides unique identifiers such as ACMEEDI, XYZEDI, etc., which are typically assigned by associations or organizations involved in EDI.
Transaction Set Code: Lists various transaction types such as 850 (Purchase Order), 810 (Invoice), 856 (Advance Ship Notice), 855 (Purchase Order Acknowledgment), 830 (Planning Schedule), and 865 (Purchase Order Change).
Each row represents a different combination of EDI standard version, association assigned code, and transaction set code, demonstrating the flexibility and variability within the EDIX12 standard for electronic data interchange.
Select and configure the EDI Standard X12, EDI Standard Version 004010, transition Set Code to 856
...
Logs provide runtime details about the inbound and outbound transactions.
Users can search logs with Partner ID, Sender/Receiver ID, Transaction Control Number and with any other data field.
Dashboard: X12 Interchange Logs |
---|
Acknowledgement : EDI OUTBOUND
...