Using the EDI Transformation Module
In this brief tutorial, we’ll cover configuring and using the EDI Transformation Module to convert ANSII 837 and similarly formatted documents to and from XML.
You’ll will need to download the Sample EDI file in order to complete this tutorial.
Click this link if you require instructions on how to import an .eipb file.
Creating a New Route
We’ll begin by creating a new Route to configure for our transformation. Click the Add Route button, indicated above.
Naming the Route
Opening the Route
Open the newly created Route for editing.
With the Route opened you should see the main eiConsole screen.
Configuring the Source
Select the Listener stage, then select the Directory / File option from the Listener Type drop-down. You’ll then provide values for Polling Directory (here we’ve chosen C:\in), which is the location from which we’ll be searching for EDI files, and for Polling Interval, which is how often the directory is checked for new files.
Configuring the Target
Next we’ll need to configure a Target to send the transformed data to. Select the Transport stage, then Directory / File from the Transport Type drop-down. You’ll need to configure Target Directory, which is where the transformed result files will be placed, Target File Name, which is the file name (minus extension) of the resulting file, and optionally Target File Extension, which is the extension for the created file.
Adding a Source Transform Format
To configure our transformation, we’ll first need to add a new Format to the Source Transform stage. Click on the stage, then on the Add Format button. You’ll then be asked to provide a name for the Format; for this tutorial, we’ll simply use EDI Transformation.
Configuring the Transformation
With the new Format added, you should see the Source Transformation screen now showing configuration panels for both a Transformation Module and for XSLT. In the Transformation Module drop-down, select the EDI transformation module. This is the component that facilitates transformations between EDI and XML formats. There’s not a lot of configuration required here, but we’ll cover each item below:
- Use Friendly Names. This specifies if the resulting XML element / tag names should be named according to the intuitive or documentative names provided in the EDI standard. For example, instead of getting a tag name like “NM108”, you’ll be provided with “NM108_IdentificationCodeQualifier.” This can produce more verbose XML results, but can be very useful for mapping as well as for debugging.
- Validate Message. This will attempt to validate the EDI data against its detected format definition.
- Throw Exception on Invalid Message. If “Validate Message” is also checked, this will cause the component to fail if an EDI message does not match the format definition. The error message will provide validation details.
- Use Custom Metadata. This, in conjunction with the Custom Metadata File option, will enable you to provide an alternate format definition in an XSD format. This is not required or recommended for most users.
- Expected Message Type. This allows you to specify what message type (such as “837”) is expected by the transformation.
- Custom Metadata File. This is the location for the Use Custom Metadata option.
Switching to Test Mode
Configuring the Test
Once in Testing Mode, select the Source Transform stage, then click the Start Test Here and End Test After Here options. This will limit our test only to the selected EDI transformation stage. Select the From File for Alternate Testing Data.
Executing the Test
Next, click Execute Test. You’ll be asked to provide an input file representing the EDI input file to test against. Select a provided sample file or a file you have handy, then hit OK.
Reviewing the Results
After the test completes, you should see a green checkmark for a success. You can then click the View Stage Output button to see the results of the transformation.
The XML Results
The Stage Output Viewer should now show you the XML results of your EDI transformation. As the Route is currently configured these XML results will be delivered to the directory you specified in the Transport stage. You can also use this XML in the Data Mapper (see related tutorials) to transform this format to another, such as to another XML format, to Microsoft Excel worksheets, or even to do insertions into databases.