Working with EDI Files Using the GT EDI Utility

This document explains how to use EDI formatted data in the Test Data Management suite.  This is done through the functionality explained below for generating scripts and rules, converting to XML and importing/exporting EDI format.
tdm40
This document explains how to use EDI formatted data in the Test Data Management suite.  This is done through the
 
functionality explained below for generating scripts and rules, converting to XML and importing/exporting EDI format.
Note:
 The following x12 EDI transactions are supported from the Insurance Industry.  If the processing transaction is outside the list below, a 
transaction not supported error
 is displayed during the 
convert to XML
 stage.
270 - 5010X279
271 - 5010X279 
276 - 5010X212 
277 – 5010X212 
820 – 5010X218 
820 – 5010X306 
834 – 5010X220 
835 – 5010X221 
837D – 5010X224 
837I – 5010X223 
837P – 5010X222 
Generate Schema and Rules
The process to generate Schema and Rule files for a given EDI set e.g. 837P, 834 should be run only once.
Follow these steps:
  1. Go to the first tab Generate Scripts and Rules. 
  2. Provide the SQL Server database name. Example - EDI.
  3. Select the transaction specification for which Schema is required.
  4. Click
    Generate Scripts
    to generate the scripts. 
  5. A generated Rules file is automatically moved to the rule file folder. 
Once schema scripts have been generated, create an MS SQL Server database and execute DDL scripts to generate schema and tables. Do not execute the new primary key – foreign key DDL (example
820X218_DDL_pk_fk.sql), 
because creation of Primary and Foreign keys slows down the import XML process.
Convert to XML
The Convert to XML process converts EDI files (*.txt and *.edi) to XML. Maximum file size limit is 60 MB that you can use to convert to XML.
Follow these steps to convert EDI files to XML: 
  1. Copy the EDI files to an input folder such as C:\Grid-Tools\GTEDI\input.
  2. Open the second tab in In GTEDI.exe to convert to XML. 
  3. Populate the EDI message directory with the pathname specifying where the EDI files are stored, such as C:\Grid-Tools\GTEDI\input.
  4. Click the
    Convert
    button. 
  5. Now the EDI files in the EDI message directory are converted to XML files and the EDI files.
    are moved to a subfolder named ProcessedEDI. These XML files can be imported to a database in the next step.
Importing EDI Files 
Follow these steps:
  1. Go to
    Import XML
    tab after running GTEDI.exe.
  2. Input the folder path where XML messages are present such as C:\Grid-Tools\GTEDI\input.
  3. Choose the drop down transaction specification of 
    to-be imported XMLs
    .
  4. Input the SQL Server Instance name – such as MYVAIOWIN81\EXP2014. 
  5. Input the SQL Server database name – such as EDI.
  6. Do one of the following:
    1. Choose integrated security.
    2. Populate the username and password for SQL Server authentication. 
  7. Click
    Test connection
    to test the connection. 
  8. Click
    Import.
Successfully imported EDI XML are saved in a folder named InsertedXML in the XML Message directory. Example directory pathname:  C:\Grid-Tools\GTEDI\input\InsertedXML
The inserted data can now be masked using FDM or manipulated using Datamaker. 
Exporting EDI Files
This step reads EDI messages from the SQL Server database. It then converts them into EDI files with the desired file extension and EDI separators.
Follow these steps:
  1. In GTEDI.exe, go to
    Export EDI 
    tab
    .
  2. Provide the folder path where XML messages are present such as C:\Grid-Tools\GTEDI\input.
  3. Choose the drop down transaction type rule file for
    to-be exported
     EDI messages.
  4. The imported EDI separators are used by default, however when using the 
    overwrite separators
     check box, you can chose your own segments, elements, and line separators.
  5. If you want to export all EDI messages then put
    Export Bundle Id
     as *. Otherwise give a specific valid bundle id from the ISA table of the given transaction table in the SQL Server database.
  6. Do not change the output directory name, let it be the default. This directory is created relative to location of GTEDI.exe.
  7. Populate the SQL Server Instance name – like MYVAIOWIN81\EXP2014.
  8. Populate the SQL Server database name – like EDI.
  9. Do one of the following:
    1. Choose integrated security.
    2. Populate username and password for SQL Server authentication.
  10. Click
    T
    est connection 
    to test the connection.
  11. Click the
    E
    xport
     button.
Now the windows explorer is launched to show you the exported files. Exported files are by default stored in a folder such as C:\Grid- Tools\GTEDI\BuildOutput\[transaction_code]. For example if the transaction code is 837DX224, the folder would be C:\Grid- Tools\GTEDI\BuildOutput\837DX224.