Practice X12 Inbound (Single/Multiple Partner Data File) to Oracle Adv Positional file including Acknowledgement generation scenario with Data Mapping Rules Test with sample Files and Test Cases Prepare, Test with sample Files and Test Cases
EDI X12 Standard
· Widely used in North America for various industries including healthcare, supply chain, transportation, and finance.
· Defines standards for various business documents such as purchase orders, invoices, shipping notices, and more.
Common EDI X12 Transactions:
850: Purchase Order
810: Invoice
856: Ship Notice/Manifest
837: Health Care Claim
997: Functional Acknowledgment
INBOUND-EDIX12
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
Configure :
To Create a Inbound Transition Click Transactions > Templates.
On the Templates screen, navigate to the Inbound Template
To Define Transaction Provide the name and description of the Transaction.
Select Network and Partner
Select and configure the EDI Standard X12, EDI Standard Version 004010, transition Set Code to 860
Select The Source
Define the File Event
Set Destination
Create Mapping
Create Variables
Condition Applied
WHEN CONDITION{$Input_X12_004010_860/EDIRoot/TS_860/BCH/BCH01='01' } VALUE=['Y' ] OTHERWISE VALUE=['' ]
We apply For Each at the Root level at the Destination end.
$Input_X12_004010_860/EDIRoot/TS_860
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.