EDIFACT
...
Inbound
EDIFACT Inbound Single Partner Data File to Oracle Adv Positional file including Acknowledgement generation scenario with Data Mapping Rules.
...
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)). .
...
Sample File
...
Understanding the sample file details:
AVNETEU
: Sender or organization name.4511866069
: Order or transaction identifier.0010
: Segment identifier indicating a header segment.CTCTLEDPPOI ORDEROR4511866069
: Order type or description.AVNETEU
: Buyer or seller organization name.BE11
: Additional identifier or location code.20231011
: Date.1
: Quantity or another numeric value.EDIFACT
: Standard identifier.
...
📄 Solution Architecture:
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
...
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.
...
EDI Configuration Example:
Field | Description | Sample Value |
---|---|---|
EDI Standard | Type of EDI standard used | EDIFACT |
EDI Standard Version | Version of the EDIFACT standard | D.96A |
Association Assigned Code | Code assigned by the association | (Empty) |
Transaction Set Code | Specific type of EDI transaction/document | ORDERS |
Example EDIFACT Message with Sample Data
Segment | Element | Description | Sample Value |
---|---|---|---|
UNA | Service String Advice |
| |
UNB | S001 | Syntax Identifier |
|
S002 | Interchange Sender |
| |
S003 | Interchange Recipient |
| |
S004 | Date and Time of Preparation |
| |
0020 | Interchange Control Reference |
| |
UNH | 0062 | Message Reference Number |
|
S009 | Message Identifier |
| |
BGM | C002 | Document/Message Name |
|
1004 | Document/Message Number |
| |
1225 | Message Function Code |
| |
DTM | C507 | Date/Time/Period |
|
NAD | 3035 | Party Qualifier |
|
C082 | Party Identification Details |
| |
LIN | 1082 | Line Item Number |
|
C212 | Item Number Identification |
| |
QTY | C186 | Quantity Details |
|
UNS | 0081 | Section Control |
|
UNT | 0074 | Number of Segments |
|
0062 | Message Reference Number |
| |
UNZ | 0036 | Interchange Control Count |
|
0020 | Interchange Control Reference |
|
Explanation
UNA Segment: Defines separators.
UNB Segment: Contains interchange header information including sender and recipient.
UNH Segment: Message header segment identifying the message type and reference number.
BGM Segment: Provides the message name, number, and function.
DTM Segment: Specifies the date/time related to the message.
NAD Segment: Identifies the buyer.
LIN Segment: Describes line item details.
QTY Segment: Specifies quantity.
UNS Segment: Section control.
UNT Segment: Message trailer indicating the number of segments.
UNZ Segment: Interchange trailer indicating the control count and reference number.
This example provides a comprehensive view of how EDIFACT messages are structured and the role of each segment.
Select and configure the EDI Configuration details like EDI Standard, EDI Standard version, association assign code, transaction set code, etc.
...
Association Assign Code: Code, designated by the organization responsible for creating and managing the specific message type, serves as a unique identifier for the message.
...
In the Transaction settings page > select the Repository File Retention.
...
Click Next to define the Source as a LAN File.
...
Info |
---|
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. |
Click on Next to add the File Event.
...
Click on Next to create data mapping > Load Source & Target Schema
...
Info |
---|
Note: When an icon is marked as |
Firstly we create variables
...