ValidateTranslate Process

The ValidateTranslate example shows how to validate input data and translate data from one format to another.

For more information about validating and translating data, see Instream and Translator.

Example Process

The ValidateTranslate process is illustrated here:

Process Definition

This process demonstrates how the Validation and Translation functions work together to process an inbound EDI. The process performs the following steps:

  1. The FilePoller activity polls the input directory. If a file exists then the process starts.
  2. The X12 Prescanner activity scans the X12 EDI.
  3. A Java activity selects the appropriate configuration files based on the data contained in the EDI.
  4. The Instream activity generates a 999 Acknowledgment response.
  5. The Instream activity validates the input EDI and generates a TA1 Acknowledgment response.
  6. The Translator activity translates the EDI to a XML file format and writes the translated data to a file.

Prescanning

This activity performs the following operations:

  1. The FilePoller activity polls for a file named *.txt in the directory specified in the File Name field of the Configuration tab. It finds the 837I_4010_H_5provider.txt file and the process starts.

    The 837I_4010_H_5provider.txt file is passed to the X12Prescanner activity.

  2. The X12Prescanner activity parses the X12 document header (ISA/GS/ST) segments and saves each element into a separate output field.

  3. The information is passed to the Java Activity named select_config_files.

For more information about prescanning data, see EDIFACTPrescanner and X12Prescanner.

Selection of Configuration Files

This activity performs the following operations:

  1. The select_config_files Java activity examines the data provided by the X12 Prescanner activity and uses the information from the GS01, GS08, and ST01 elements to select the appropriate validation guideline, translation map, and configuration profiles.

  2. The select_config_files Java activity passes the information to both the Write File activity named WriteACK_999 and the Instream activity.

Validation and Response Generation

This activity performs the following operations:

  1. The Instream activity generates a 999 Acknowledgment response document, which reports the status of implementation guide syntax edits.

  2. The Instream activity validates the input EDI (837I_4010_H_5provider.txt) using the validation guideline and configuration profiles selected by the select_config_files Java activity.

  3. The Instream activity generates a TA1 Acknowledgment response document, which acknowledges the receipt of the contents of the transaction.

  4. The TA1 Interchange Acknowledgment is saved as a text file.

  5. The validated file is passed to the Translator activity.

For more information about validating data, see Instream.

Translation

This process performs the following operations:

  1. The Translator activity translates the validated file from EDI to Flat File format using translation maps specified by the select_config_files Java activity.

  2. The Translator activity generates a file containing the translated output data.

For more information about translating data, see Translator.

Contents
Search Results