BridgeGate™

Tutorial 9: EDI Functionality

Table of Contents

Creating Inbound EDI Templates using the built in Standards Repository

In this exercise we will be creating a 997 inbound EDI template using the Inbound Template wizard, and mapping the data to CSV data. Open the Inbound Template screen, select the Workflow Group 'sample9', and then click on the down arrow for the Workflow Group Navigator to open the context menu. If 'sample9' does not exist, then use the context menu to create a new Workflow Group 'sample9'. Then select 'New Template Wizard…'

Figure: Creating a new Inbound Template

The Inbound Template Wizard opens. Select the option to 'Create a new Inbound Template from an EDI Standard' and click next. Select the option for ANSI ASC X12 and click next. The wizard then opens a list of all X12 EDI versions found in the repository. Select 4010 for this example and click next. Finally, the wizard shows all EDI document types found for the version 4010. Each version in the repository contains different EDI documents available, and not all EDI documents are available for each version. Scroll down and locate 997, and click next. The wizard then asks you for a name for the template. Enter the name 4010_997 and click finish. The template is automatically generated and is opened for you. You are now ready to map inbound 4010 997 EDI data to an outbound template.

Inbound EDI Validation

EDI Validation is available for templates created with the options for 'SEF' and 'EDI Repository' in the above wizards. It is recommended to use templates when they are available from the EDI Repository.

By default, the option to use Data Validation is set to TRUE. You may turn off this feature at the Workflow level, when you create a Translate Workflow Item and specify the inbound template to use. You can also turn this feature off on the Test by Template screen when testing just templates.

[Screen image]

Code Set Validation

Open the 4010_997 inbound template you just created, select the Body, ST Segment, ST01 element. Finally, select the Data Validation tab.

The list of allowable values for the ST01 code set is displayed. When you create an EDI template from the EDI Repository, you do not have the option to modify the list of allowable values, as they come from a built in database. However, you are free to modify any element that does not already have a list of allowable values. For EDI templates created from a SEF, you can modify any element's allowable values, since the validation rules are stored in the template xml file itself. Storing the validation rules on the template greatly increases the size of the template xml file, so it is recommended to use the 'EDI Repository' option.

Situational Field Rules

While the 997 template does not have any situation rules, they will populate on Segments that require them when you build a template using the 'EDI repository' or 'SEF'. Below is a screen shot showing what a CONDITIONAL situational rule would look like if it existed on the AK1.

All EDI situation rules are available in the 'Rule Type' drop down on this Data Validation tab.

Stop processing on Error

For outbound EDI template validation, you can specify the option to immediately stop processing a transaction in the event you produce invalid outbound EDI data.

Outbound EDI Validation

EDI Validation is also available on outbound EDI templates, when using BridgeGate to generate EDI data.

EDI Acknowledgements