OUTBOUND - EDI X12

Outbound EDI X12 845 (EDI 845: Price Authorization Acknowledgment/Status)

Problem Statement:

Use Case:

AVNET (Supplier): The supplier providing electronic components.
SNA (Retailer): The retailer purchasing electronic components from AVNET.

Goal:

To efficiently communicate price changes, discounts, and allowances for electronic components from AVNET to SNA using the EDI 845 transaction set.

Pre-conditions:

Both AVNET and SNA have agreed to use EDI for their transactions.
EDI systems are in place and properly configured for both parties.
Initial pricing agreements have already been established between AVNET and SNA.

Triggers:

AVNET decides to update the pricing for certain electronic components due to market changes.

Pre-requisites:

Deploy the object Zip in local/Training Environment.
Create a Network for which you are creating a transaction.
Create a Partner for the data exchange.

Solution Architecture:

Design a Transaction using an EDI Outbound Pre-built template.
Create Source Schema- EDI845
Create Target Schema - Advance positional
Create a File Event activity
Create Target folder Location (LAN)
Create Mapping activity
EDI Configuration

Solution:

Design: Create transaction in Adeptia Connect to convert data

1. Configure : Define Transaction

To Create an Outbound Transition Click Transactions > Templates.
On the Templates screen, navigate to the Outbound Template

To Define 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

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

On EDI Configuration step, do the following:

Type the last used transaction control number in the Last used Transaction Control No text box.

Expand Group Envelope Properties and define the properties.

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:

Segment Terminator:
- Typically a tilde ~
- Used to mark the end of a data segment.
Element Separator:
- Typically an asterisk *
- Used to separate individual elements within a segment.
Sub-element Separator (also known as Composite Element Separator):
- Typically a colon :
- Used to separate sub-elements within a composite data element.

Expand ISA Envelope Properties and define ISA Envelope.

2, Define Source: Select the File source application

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

Define Layout: Click Next to select the File Event from drop-down list.

3.Set Destination

Define the Destination application account.

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

Create/Add Variables

Let's create a variable using the following name: VarGetPosition

Condition Applied: get-context( 'TotalLIN', '')

The purpose of get-context('TotalLIN', '') is to fetch data associated with the context named 'TotalLIN'

Check for the data input.

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.

Dashboard: X12 Interchange Logs

Dashboard: X12 Interchange Logs