EDI X12 Interchange parsing with Iguana

This article is more of Notes for myself. There is nothing in this article that persistent reader won’t find on our online Help pages. Having said that, Iguana newby may get confused to put this puzzle together.

To begin with this example, please install and inspect carefully attached files.
Please note that processing is divided between two of channel components.

This example files have to be installed into Source and Filter components for same channel of type “From Translator to Translator”, with Filter enabled.

In Channels Source component, ‘From Translator’, this example lists EDI files in a folder and processed files moved to dedicated other folder.

Assumption is that every file contains single Interchange Envelope (ISA/IEA).

For every single Interchange Envelope there is option to generate TA1 and to store it in a file. The TA1 example is optional, you may not need it.

Every individual Transaction Set (ST/SE) is pushed to Iguana queue for further individual processing, along with additional control information to identify respective Functional Group and Interchange Envelope and source file.

When individual Transaction Set arrives to Filter (or Destination) component script, it is parsed. The data stored to database tables. Control information can be stored to database as well.

Channels Destination component may remain vacant for use in future, or you can run Filter script in Destination component, if you please.

Use attached sample data to see how this example works.

In case of doubt between other documentation to this example, please act as in this example.

Most of explanations are given as comments in between lines of script code. Please pay attention to these comments, they all very important.

Attachments:

You must be logged in to view attached files.

Some security person decided to block *.edi files upload and I noticed it only now. Well, better late than never, here is the test data:

Attachments:

You must be logged in to view attached files.