...
AVNET decides to update the pricing for certain electronic components due to market changes.
📑 Pre-requisites:
a. Deploy the object Zip in local/Training Environment.
Create a Network for which you are creating a transaction.
b. Create a Partner for the data exchange.
...
Design: Create transaction in Adeptia Connect to convert data
1. 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
...
Setting up the partner EDI Configurations
...
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 845
...
Expand Group Envelope Properties and define the properties.
...
| Info |
|---|
EDIX12 (Electronic Data Interchange X12) is a standard developed by the American National Standards Institute (ANSI). In EDIX12, separators are used to define the structure of the data segments and elements. The key separators in EDIX12 include:
|
Expand ISA Envelope Properties and define ISA Envelope.
...
Click Next to define the file generation policy details.
...
The Defined File name and extension will generate the output file as shown in the screenshot below.
The extension is extensively used to generate the output file to the recently updated data and time.
...
On File Generation Policy step, type the extension of the file in the File Extension text box
Click Next to define the encryption. Select Want to encrypt target file? check box if you want to encrypt the destination file
...
In the specified routing rule, the identifier Xpath is retrieved from the mapping on the source side. Within the Element name "Distributor," the value "AVNET" is specified in the respective field.
...
4.Create Mapping
...
Create Data Mapping >>Load Source and Target Schema
...
Users can search logs with Partner ID, Sender/Receiver ID, Transaction Control Number and with any other data field.
Dashboard: X12 Interchange Logs -20240729-111628.png?version=1&modificationDate=1722252268008&cacheVersion=1&api=v2&width=454) |
|
|---|
-20240729-111639.png?version=1&modificationDate=1722252268038&cacheVersion=1&api=v2&width=603)