EDIFACT ORDRSP Outbound

Oracle Adv Positional file(Single/Multiple Partner Data File) to EDIFACT outbound including Acknowledgement reconcile scenario with Data Mapping Rules.

Problem Statement:

XYZ Company is the sender of the Purchase Order file and aims to convert it from a fixed-length flat-file format into an EDI (Electronic Data Exchange) format that can be processed in its system by Vendor/Partner.

Solution Architecture:

1. Design a Transaction using an EDI Inbound Pre-built template.

2. Create a UNB Envelope

3. Create Source Schema- Advance positional

4. Create Target Schema - EDI ORDRSP

5. Create a File Event activity

6. Create Target folder Location (LAN)

7. Create Mapping activity

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

1. Go to transaction > Select EDI Outbound Pre-built Template

Open

2. To configure the transaction provide the name in the context of the use case and a description of the Transaction.

Open

3. 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. 

4. Select and configure the EDI Configuration details like EDI Standard, EDI Standard version, association assign code, transaction set code, etc.

5. Add UNB Envelope Properties, and select the checkbox for content-based routing.

6. 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

7. Click Next to define the Source as a LAN File.

8. Click on Next to add the File Event.

9. Click on Next to select the Source data format & Layout

10. Click Next to define the Destination application account.

11. Click on Next to create a LAN File Target

12. Click on Next to fill in the File Generation Policy

13. Click on Next to define the Routing Rule

14. Click on Next to create data mapping > Load Source & Target Schema

Note: When an icon is marked as (Required), it must be mapped to a specific value in the data mapping process. Failure to do so will result in an error at the schema level during transaction execution.

Adding a new variable

Let's create a variable using the following name: varDOCCODE

Local Variable Value: normalize-space( Document_Code)

Logic of the above condition:

The expression normalize-space(Document_Code) is a function typically used in XPath or XQuery to manipulate text data. Here's what it means in simple terms:

1. Document_Code: This refers to a piece of text or string data named "Document_Code".

2. normalize-space(): This is a function used to clean up and normalize whitespace characters within a string:

   • It removes leading and trailing whitespace (spaces, tabs, newlines, etc.).

   • It also replaces multiple consecutive whitespace characters inside the string with a single space.

2. Let's create a variable using the following name: varTPCODE

Local Variable Value: normalize-space(TP_Translator_Code_855 )
Logic of the above condition:

• It takes the text stored in the variable or field named "TP_Translator_Code_855".

• It ensures that any extra spaces or tabs at the beginning or end of this text are removed.

• It condenses any multiple spaces, tabs, or newline characters within the text into a single space.

This function is useful for cleaning up and standardizing text data, making it easier to handle and ensuring consistency when working with strings in data processing or document handling tasks.

3. Let's create a variable using the following name: varPosition

Local Variable Value: string(position( ))
Logic of the above condition: In more straightforward language, the function string(position()) provides a text-based representation (string) of the current item's position (index) within a sequence or list. It is commonly utilized to exhibit or modify the order or index of items in XML or similar structured data formats.

4. Let's create a variable using the following name: varSet_0010_Loop

Local Variable Value: set-context('0010Loop', $varPosition)

Logic of the above condition: The value of $varPosition is being stored or associated with a specific identifier '0010Loop'. This identifier could be used later in the code to retrieve or manipulate the value stored in $varPosition under the context or category '0010Loop'. This kind of mechanism is often used in programming to manage and organize data based on different contexts or purposes within an application.

5. Let's create a variable using the following name: varGet_0010Loop

Local Variable Value: get-context( '0010Loop','' )

Logic of the above condition: The function aims to retrieve the value that was previously stored or set under the identifier '0010Loop'. The second parameter, '', serves as a placeholder or default value if there is no value associated with '0010Loop'.

6. Let's create a variable using the following name: varPos

Local Variable Value: position( )

The Logic of the above condition: position() appears to be a function call that retrieves the current position or index within a certain context or structure.

• In the TS_ORDRSP field, we implement a For Each Loop and utilize a Local Variable named "varPos".

• Applying Loop3_NAD,Loop3_NAD[1] & Loop3_NAD[2] For Each iteration to meet the requirement within the nested dataset.

• Applying Loop26_LIN For Each iteration to meet the requirement within the nested dataset.

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.