Outbound EDI X12 856 (Automating Shipment Notifications with EDI 856)
🤔 Problem Statement:
Use Case:
XYZ Retailers have recently decided to enhance their supply chain operations by implementing Electronic Data Interchange (EDI). One critical document they aim to automate is the EDI 856 (Advance Ship Notice/Manifest), which provides detailed information about the contents of a shipment.
📑 Pre-requisites:
XYZ Retailers and ABC Suppliers must have an EDI agreement in place.
Both parties need to use compatible EDI software that supports EDI 856.
EDI network setup is completed and tested.
Item, packaging, and shipment data must be accurately maintained in both parties' systems.
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- EDI856
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
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
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
On EDI Configuration step, do the following:
Type the last used transaction control number in the Last used Transaction Control No text box.
As this is an outbound transaction, a corresponding inbound acknowledgment has to be created.
Follow the steps to define the outbound acknowledgment: Click here
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 LAN and click next to configure File Event
Define Layout: Click Next to select the File Event from drop-down list.
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.
Select and define Source Layout
3.Set Destination
Define the Destination application account.
Click Next to define the file generation policy details.
Select data Encoding: UTF-8
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
4.Create Mapping
Create Data Mapping >>Load Source and Target Schema
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.
Acknowledgement : EDI OUTBOUND
Define transaction name and description this transaction will generate the Inbound Reconcile for the above transaction.
Select the Network and Partner
Configure EDI
Set Source and define layout to generate the inbound reconcile file.
To view the status of the Acknowledgment transaction follow the steps below.
Dashboard View: Go to Configure > Transactions > All Messages > EDI X12 Interchanges
.png?version=1&modificationDate=1719831331243&cacheVersion=1&api=v2&width=747&height=304)
Summary:
Inbound EDI reconciliation process automates the validation, transformation, and integration of EDI transactions, ensuring data accuracy and integrity. This process enhances efficiency, reduces errors, and provides valuable insights into the EDI operations.