INBOUND - EDI X12 With Acknowledgement

Inbound EDI X12 850 (Purchase Order)

Problem Statement:

Situation:

A large retail company with a wide network of suppliers and vendors faces challenges in managing purchase orders efficiently. Manual order processing leads to errors, delays, and increased operational costs. The company aims to automate its procurement process to improve accuracy, speed, and efficiency.

Objective:

The primary objectives for deploying the EDI 850 transaction set to achieve:

1. Automate Order Processing

2. Improve Order Accuracy

3. Enhance Communication

4. Enable Order Tracking

5. Support Scalability

Solution Architecture:

1. Design a Transaction using an EDI Inbound Pre-built template.

2. Create Source Schema- EDI850

3. Create Target Schema - Advance positional

4. Create a File Event activity

5. Create Target folder Location (LAN)

6. Create Mapping activity

7. EDI Configuration

Pre-requisites:

1. Deploy the object Zip in local/Training Environment.

2. Create a Network for which you are creating a transaction.

3. Create a Partner for the data exchange.

Solution:

Design: Create transaction in Adeptia Connect to convert data

1. Configure : Define Transaction

1. To Create an Inbound Transition Click Transactions > Templates.

2. On the Templates screen, navigate to the EDI Inbound Template

Open

3. To Define Transaction Provide the name and description of the Transaction.

Open

4. Select Network and Partner

 EDI Configuration Example:

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.

5. Select and configure the EDI Standard X12, EDI Standard Version 004010, transition Set Code to 860. Keep Transaction Properties, Interchange Properties, Group Properties, Document Properties and Advance Properties to Default Settings.

As this is an inbound transaction, a corresponding outbound transaction will be defining an outbound transaction for acknowledgment.

Follow the steps to define the outbound acknowledgment: Click here

 2, Define Source:

Select the Source type as LAN and click next to configure File Event

Define the File Event > Name >Trigger Type (On file Created)

Specify the file base location path, user ID, and password. Then choose the event start date as well as the expiry date and time.

Select Trigger Simple and polling frequency as per the requirement.

3. Set Destination

Define the Destination application account.

Click on Next to create a LAN Account Information

Define Target Layout

4. Create Mapping

Create Data Mapping >>Load Source and Target Schema

Mapping Expression - here for each is used for $Input_X12_004010_850/EDIRoot/TS_850

The mapping expression for each $Input_X12_004010_850/EDIRoot/TS_850 is used to iterate through each TS_850 transaction set within the input EDI 850 document. This allows the mapping tool to process and transform each occurrence independently, ensuring comprehensive and accurate data transformation.

Steps to Turn on the Transaction

After you have Saved and Exit the Transaction page. You will be asked to Turn on the transaction

 Viewing execution details

• Go to the Dashboard to view execution details. The Status column shows execution status of the transaction.

• Click the execution icon under Action to view the detailed information about transaction.

• Click the information icon under the respective Icons to know details of execution at a that step.

• Click More arrow under Action menu to know further details of the transaction.

EDI Dashboard and EDI X12 Interchange logs

• 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.

Acknowledgement: EDI OUTBOUND

Define transaction name and description this transaction will generate the Outbound Acknowledgement.

Select the Network and Partner

Configure EDI: Standard, Version, Transaction Code, Indicator, Sender, Recover ID and Envelop Version etc.

Set Destination and define the event.

Summary:

Outbound acknowledgement transactions (e.g., EDI 997) between Suppliers and Retailers automates the confirmation of EDI message receipt and validation. This process improves communication accuracy, enhances operational efficiency, and ensures compliance with EDI standards.