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.
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
Configure :
To Create a 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
Select and configure the EDI Standard X12, EDI Standard Version 004010, transition Set Code to 860
Set Source
Layout
Destination
Create Mapping
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.