EDIFACT INVOIC Inbound
EDIFACT Inbound Single Partner Data File to Oracle Adv Positional file including Acknowledgement generation scenario with Data Mapping Rules, Test with sample Files and Test Cases.
Problem Statement:
Here XYZ Company is the receiver and it is receiving the Invoice/Bill from its Vendor/Partner through EDI (Electronic Data Exchange) and wants to convert it into the format in which it can process it in its system (here the format is Position (fixed length flat file)).
Solution Architecture:
An EDIFACT INVOIC is typically sent by a seller, such as a manufacturer or distributor, to a buyer, like a retailer, after an order has been shipped. This document confirms that the order has been delivered and requests payment from the buyer to finalize the transaction.
Design a Transaction using an EDI Inbound Pre-built template.
Create a UNB Envelope
Create Source Schema- EDI INVOIC
Create Target Schema - Advance positional
Create a File Event activity
Create Target folder Location (LAN)
Create Mapping activity
Solution:
Define Transaction
...
Select Network and Partner
...
EDI Configuration
...
Transaction Settings
...
Select Source
...
Create a File Event
...
Select Destination
...
...
Pre-requisites:
a. Create a Network for which you are creating a transaction.
b. Create a Partner for the data exchange.
Solution:
Design: Create transaction in Adeptia Connect to convert data
Go to transaction > Select EDI Outbound Pre-built Template
...
To configure the transaction provide the name in the context of the use case and a description of the Transaction.
...
Select the Network from the Select Network field & Select the partner for whom you are creating this Transaction. All the Partners of the Network(s) to which this Template belongs will be populated in the field.
...
Select and configure the EDI Configuration details like EDI Standard, EDI Standard version, association assign code, transaction set code, etc.
...
In the Transaction settings page > select the Repository File Retention.
Repository File Retention- DONT DELETE, DELETE, DELETE ON SUCCESS, and DELETE ON SUCCESS EXCEPT SOURCE DATA
...
Click Next to define the Source as a LAN File.
...
Click on Next to add the File Event.
...
Select the Event that you have created
...
Click Next to define the Destination application account.
...
Click on Next to create a LAN File Target
...
Select LAN File Target/Select Mode type/Give File Name/Add File Extension
...
Select Target Data Format/Target Layout
...
Select Layout
...
Create an Advance Positional Target Data Layout
...
Click on Next to create data mapping > Load Source & Target Schema
...
Firstly we create variables
Let's create a variable using the following name: varTP_Code
Condition applied : "WHEN CONDITION{$Input_EDIFACT_D07A_INVOIC/EDIRoot/UNB/UNB02/UNB0201='O0013000023HELLA-KG-EDIP' } VALUE=['HELLA_EU' ]WHEN CONDITION{$Input_EDIFACT_D07A_INVOIC/EDIRoot/UNB/UNB02/UNB0201='O0013000023HELLA-KG-HER' } VALUE=['HELLA_EU_HER' ]WHEN CONDITION{$Input_EDIFACT_D07A_INVOIC/EDIRoot/UNB/UNB02/UNB0201='O0013000023HELLA-KG-BHTC' } VALUE=[ 'HELLA_EU_BHTC']WHEN CONDITION{$Input_EDIFACT_D07A_INVOIC/EDIRoot/UNB/UNB02/UNB0201='O0013000023HELLA-KG-HIS' } VALUE=[ 'HELLA_EU_HIS']OTHERWISE VALUE=['ERROR' ]"
...
Let's create a variable using the following name: varNAD_ST_0201
Condition applied: “$Input_EDIFACT_D07A_INVOIC/EDIRoot/TS_INVOIC/Loop2_NAD/NAD[NAD01='ST']/NAD02/NAD0201"
...
Let's create a variable using the following name: varTp_loc
Condition applied: WHEN CONDITION{ $varNAD_ST_0201='1014'} VALUE=['SBI1014' ]WHEN CONDITION{ $varNAD_ST_0201='1015'} VALUE=[ 'SBI1015']WHEN CONDITION{ $varNAD_ST_0201='1000'} VALUE=['SBI1000' ]WHEN CONDITION{ $varNAD_ST_0201='1025'} VALUE=[ 'SBI1025']WHEN CONDITION{ $varNAD_ST_0201='1263'} VALUE=['SBI1263' ]OTHERWISE VALUE=[ 'ERROR']
...
Let's create a variable using the following name: varLANtax_amt
Condition applied: round( $Input_EDIFACT_D07A_INVOIC/EDIRoot/TS_INVOIC/Loop26_LIN/Loop27_MOA/MOA/MOA01/MOA0102 * 0.19,2)
...
Let's create a variable using the following name: varNAD_BY
Condition applied: $Input_EDIFACT_D07A_INVOIC/EDIRoot/TS_INVOIC/Loop2_NAD/NAD[NAD01='BY']/NAD02/NAD0201
...
Let's create a variable using the following name: varTP_BILL_LOC
Condition applied: WHEN CONDITION{ $varNAD_BY='317050'} VALUE=[ 'SBI1014']WHEN CONDITION{ $varNAD_BY='317051'} VALUE=['SBI1015' ]WHEN CONDITION{ $varNAD_BY='317052'} VALUE=['SBI1000' ]WHEN CONDITION{ $varNAD_BY='317053'} VALUE=[ 'SBI1025']WHEN CONDITION{ $varNAD_BY='317054'} VALUE=['SBI1263' ] OTHERWISE VALUE=[ 'ERROR']
...
We
...
implement the For Each operation at the
...
top level
...
on the
...
destination side.
$Input_EDIFACT_D07A_INVOIC/EDIRoot/TS_INVOIC/Loop26_LIN
...
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
Navigate to the Dashboard to access execution details. The Status column will indicate the current status of the transaction.
Select the execution icon located under Action to delve into specific information about the transaction.
To gain insights into each step's execution details, click on the information icon corresponding to that particular step.
For additional transaction details, expand by clicking on the More arrow within the Action menu.
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 any other data field.