...
The goal is to develop and implement a robust solution that facilitates the automated processing of inbound EDI X12 860 transactions. This solution should seamlessly integrate with their existing ERP system, ensure data accuracy, and enhance operational efficiency.
📄 Solution Architecture:
Design a Transaction using an EDI Inbound Pre-built template.
Create Source Schema- EDI860
Create Target Schema - Advance positional
Create a File Event activity
Create Target folder Location (LAN)
Create Mapping activity
EDI Configuration
📑 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 Inbound Transition Click Transactions > Templates.
On the Templates screen, navigate to the EDI Inbound Template
...
To Define a Transaction Provide the name and description of the Transaction.
...
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 this 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 860
...
specifically under the "EDI Configuration" section. Here are the details shown in the image:
Test/Production Indicator: Set to "P-Production".
Generate Acknowledgement: Set to "Yes - With error detail".
If the user prefers not to generate an acknowledgment, they have the option to select “No”.
Compliance Check: Checked.
Data encryption at rest: Set to "Use Global Policy".
...
2, Define Source:
Select the Source type as FTP and click next to configure File Event
...
Define the File Event > Name >Trigger Type (On file Created)
| Info |
|---|
File Event Recommended setting: Need to maintain the polling frequency at 1 minute and ensure that the stable time is not less than 10 seconds. |
Specify the file base location path, user ID, and password. Then choose the event start date as well as the expiry date and time.
...
Define the Destination application account.
...
Click on Next to create a an FTP Account Information
...
4. Create Mapping
...
Go to the Dashboard to view execution details. The Status column shows the execution status of the transaction.
...
Click the information icon under the respective Icons to know the details of execution at a that stepthat step.
Click the More arrow under the Action menu to know learn further details of the transaction.
...
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=2&modificationDate=1722252078602&cacheVersion=1&api=v2&width=454) |
|
|---|
-20240729-111639.png?version=1&modificationDate=1722252094506&cacheVersion=1&api=v2&width=603)