Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Inbound EDI X12 860 (Purchase Order Change Request - Buyer Initiated

Problem Statement:

XYZ Manufacturing company, currently utilizes a manual process for managing purchase order changes from their trading partners. This process is labor-intensive, prone to errors, and often results in delays that affect our supply chain efficiency and customer satisfaction. To streamline operations, they aim to implement an automated system for handling inbound EDI X12 860 (Purchase Order Change Request - Buyer Initiated) transactions.

Objective

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

 

Solution:

Design : Create transaction in Adeptia Connect to convert data

1. Configure : Define Transition

  1. To Create a Inbound Transition Click Transactions Templates.

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

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

image-20240613-101238.png
  1. Select Network and Partner

image-20240613-105228.png
  1. Select and configure the EDI Standard X12, EDI Standard Version 004010, transition Set Code to 860 

image-20240614-095545.pngimage-20240614-095722.pngimage-20240614-095835.pngimage-20240614-095942.pngimage-20240614-100424.png

 2, Define Source:

  1. Select The Source type and File Event

image-20240614-100728.pngimage-20240614-101021.png

Define the File Event

image-20240614-101205.pngimage-20240614-101350.pngimage-20240614-101456.pngimage-20240614-101629.png

Set Destination

image-20240614-101928.pngimage-20240614-102052.pngimage-20240614-102234.pngimage-20240614-102322.pngimage-20240614-102357.pngimage-20240614-102800.png

Create Mapping

image-20240614-102927.png

Create Data Mapping

Load Source and Target Schema

image-20240618-071737.png

Create/Add Variables

Global Variable: varPricingqty

Condition Applied

WHEN CONDITION{$Input_X12_004010_860/EDIRoot/TS_860/BCH/BCH01='01' } VALUE=['Y' ] OTHERWISE VALUE=['' ]

image-20240617-043700.png

We apply For Each at the Root level at the Destination end.

$Input_X12_004010_860/EDIRoot/TS_860

image-20240618-065315.png

Local Variable 1:

./Loop5_N1/N1[N101='ST']/N104

image-20240618-063900.pngimage-20240618-070107.png

Local Variable 2:

varS_ST_EDI_LOC_CODE

WHEN CONDITION{$varST_LOC='H050' or $varST_LOC='1300'} VALUE=['EAVN1824' ]
WHEN CONDITION{$varST_LOC='H464' or $varST_LOC ='H204' } VALUE=['EAVN1823' ]
WHEN CONDITION{$varST_LOC='1303'} VALUE=['EAVN43685']
WHEN CONDITION{$varST_LOC='1373'} VALUE=['EAVN52820']
OTHERWISE VALUE=[$varST_LOC ]

image-20240618-064046.png

Local Variable 2: IF CONDITION{ $Input_X12_004010_860/EDIRoot/TS_860/BCH/BCH01='01'} VALUE=[ 'Y']

image-20240618-064223.png

Local Variable 4:

varTP_CODE

image-20240618-064401.png

Local Variable 5:

normalize-space( $Input_X12_004010_860/EDIRoot/TS_860/ST/ST02)

image-20240618-064522.png

Check for the data input.

image-20240617-044444.png

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.

  • No labels