ECS/EDI Sample Application

The ECS/EDI Sample Application has been provided to give the developer a head start in building Inbound and Outbound mapping definitions. 

The theme of the sample application is order processing; Inbound Customer Orders and Outbound Purchase Orders. The sample programs provide you with all the necessary files, programs and data to process sample inbound and outbound Orders using the EDIFACT Standard, ORDERS message, Version D96A. 

The following set up instructions will guide you through the creation of the necessary sample programs and the execution of the transactions to process inbound and outbound Orders.

Sample Application Set up

Before commencing this section please ensure that you have the necessary AS/400 authority to create the required objects and that you are technically able. This section requires a good understanding of the AS/400, DB/400, PDM, RPG, Query and some knowledge of EDI.  

The sample application programs and files are shipped as source only. 

Step 1. Create the necessary objects

• Ensure that ECS/integrated email is not running.
• Sign on to the AS/400 and Add the "ECSIE" library to your library list. 
• Start PDM and locate the source members within ECSIE/SAMPLES 

The following source members should be displayed:  

• Compile all the objects in the order listed (starting with the files)  

If any of the objects fail to compile review the compiler listing and Joblog. 

Step 2. Set up the necessary ECS/integrated email configuration

The next step is to set up the EDI Events within  ECS/integrated email to enable the transaction processing of Inbound and Outbound Orders. The EDI sample Set up program (ESETUP) will perform the following: 

• Create an Inbound EDI Event called "AAA_ORD_IN" to process Inbound EDI Orders.
• Create an Outbound EDI Event called "BBB_ORD_OUT" to process Outbound Purchase Orders.
• Set up the required Header and Footer records required for the Outbound EDI Event "BBB_ORD_OUT"
• Populate the Sample Order Header and Line files with Sample Purchase Order Data.

Perform the following steps to set up the EDI Sample data:

• Ensure that the library "ECSIE" exist in the library list. 
• Call the program ESETUP by entering the following on a command line:  CALL ESETUP
• Review the EDI Events automatically created to amend the Event Administrator email address. 

Step 3. Create the necessary Folders on the PC Hosting ECS/integrated email

The sample application has been set up to process Inbound and Outbound EDI Interchanges to/from specific folders on the PC that is running the ECS/ie Client software.  It is necessary to manually create the following folders on the PC before continuing to process the EDI Samples: 

• C:\EDI\IN 
• C:\EDI\OUT
• C:\EDI\ERROR
• C:\EDI\PROCESSED

Note: If you are unable to create the folders with exactly the path as specified then it is important that the EDI Events are changed accordingly. For more information on maintaining EDI Event values click here.

Step 4. Process Outbound Purchase Orders  

The set up is complete and you are now ready to process outbound Purchase Order to create EDI Messages. 

Calling the Purchase Order EDI Selector program (E501S) reads through the Sample Order Header and selects all unprocessed records (OHPCF<>"1"). The Selector attempts to locate a related EDI Event in ECS/integrated email (File: IEXE) and if found, will call the Outbound Orders EDI Generation program E501. The result should be a an EDI Interchange in the Output folder (C:\EDI\OUT)

To create EDI Interchanges containing Outbound Purchase Orders perform the following steps:

• Ensure that the library "ECSIE" is in the library list. 
• Call the Purchase Order EDI Selector program by entering the following on a command line:   CALL E501S
• Start ECS/integrated email 
• Once ECS/ie has completed review the contents of the folder C:\EDI\OUT. It should contain an EDI Interchange that looks like the following sample: sample_edi_interchange.htm

To rerun the inbound Order process, call the EDI Samples Set up program again (CALL ESETUP) to create another Purchase Order and repeat these steps. 

Note: If the EDI Processor did not run then Edit the EDI Event to enable the EDI Processor 

Step 5. Process Inbound Orders  

Calling the Inbound Order EDI Selector program (E401S) reads through the ECS/EDI Control file and selects any Inbound Orders that have been processed by the ECS/EDI Processor and is ready for mapping to the business application. In this scenario we are have an Inbound Orders conversion program (E401) that maps the EDI Document data to the Sample Order Header file (XOH) and Order Lines (XOL). 

To process the sample Inbound EDI Order document perform the following steps:

• Locate the sample inbound EDI Interchange containing Orders; sample_edi_interchange.htm which should reside in the folder: C:\ECSIE\
• Copy the sample EDI document to the folder: C\EDI\IN
• Start ECS/integrated email 
• Once ECS/ie has completed, the file should have automatically moved from C:\EDI\IN\    to C:\EDI\PROCESSED\    and mapped the data to the ECS/EDI Transaction and Control files on the AS/400 ready for mapping to the sample application.
• Return to the AS/400 session and ensure that the library "ECSIE" is in the library list. 
• Call the Inbound Order EDI Selector program by entering the following on a command line:   CALL E401S
• Review the contents of the sample Order file (XOH & XOL) which should contain the mapped data.

To rerun the inbound Order process, repeat these steps. 

Step 6. Getting Started with development

The source code for the sample programs are well documented. Review the sample programs E401, E401S, E501 and E501S. Use these programs as templates for developing integration programs with your own business application. 

For more information on ECS/EDI integration with Business applications refer to the following: 

> How  to Integrate Inbound EDI with your Business Application

> How  to Integrate Outbound EDI with your Business Application

<<<<< Back to ECS/EDI Menu <<<<< 

Copyright © 1998-2003 Electronic Commerce Solutions All rights reserved.

ECS/integrated email & ECS/ie are trademarks of Electronic Commerce Solutions, Ltd. Other brand names and product names used in this document are the trademarks and trade names of their respective holders and may be registered.