Implementation: EDI to XML

Use Cases

EDI 850 to XML (Orders) - Inbound: Convert incoming EDI 850 (purchase orders) to XML format.

Steps

EDI to XML Conversion

1. Retrieve EDI File:

   • Action: Fetch the EDI inbound file from the LAN location.

   • Purpose: This file contains the purchase orders that need to be processed.

2. Convert to IDoc:

   • Action: Transform the EDI file into an IDoc (Intermediate Document) format.

   • Purpose: IDoc is the standard data structure used by SAP to transfer data.

3. Post to SAP:

   • Action: Send the IDOC to the SAP system for further processing.

   • Purpose: SAP needs to process this data according to predefined business rules.

Processing in SAP

4. Process IDoc in SAP:

   • Action: SAP processes the received IDoc.

   • Purpose: Perform necessary operations based on the content of the IDoc, such as updating order statuses or generating invoices.

5. Generate Outbound IDoc:

   • Action: Based on the processed data, SAP creates an outbound IDoc.

   • Purpose: This IDoc will be used to send the processed information back to the external system.

Implementation:

1. Go to Configure> Transaction> Template> Select EDI Inbound.

2. Define Transaction> Provide Name and Description of the Transaction.

3. Select Network & Partner.

4. Add EDI Configuration Details.

In this table:

• EDI Standard: Remains EDIX12 for all entries, indicating the standard being used.

• EDI Standard Version: Includes different versions like 4010, 5010, and 6020, showcasing variations across releases.

• Association Assigned Code: Provides unique identifiers such as ACMEEDI, XYZEDI, etc., which are typically assigned by associations or organizations involved in EDI.

• Transaction Set Code: Lists various transaction types such as 850 (Purchase Order), 810 (Invoice), 856 (Advance Ship Notice), 855 (Purchase Order Acknowledgment), 830 (Planning Schedule), and 865 (Purchase Order Change).

Each row represents a different combination of EDI standard version, association assigned code, and transaction set code, demonstrating the flexibility and variability within the EDIX12 standard for electronic data interchange.

5. Set Source as LAN File.

6. Select File Location > Create a File Event.

7. Create an Archive File.

Create Archive File

• Create Archive File (Optional): When this checkbox is selected, it allows for the archiving of files.

• Archive Folder Name: Specifies the path where the archived files will be stored. In this example, it is set to \\INBOUND\Grainger INC\850.

• Auto Organized Archive Folder Based On Date: This checkbox, when selected, organizes archived files into folders based on the date.

• Add Archive File Time Stamp: This checkbox, when selected, adds a timestamp to the archived files to indicate when they were archived.

• Time Stamp Format: This allows you to set the format of the timestamp. Here, it's set to mm-dd-yyyy for the date and HH-mm-ss for the time.

8. Select Destination as LAN File.

9. Create LAN File Target.

10. Create Target Layout: IDOC Layout

11. Create Mapping: