Our EDI X.12 database is intended for developers and software integrators who develop their own EDI-capable software and need to a way to translate X.12 into readable form.
This database was initially developed for an EDI translator dealing with 820 subset (Remittance Advice) and later extended to cover other subsets. Database also includes information regarding segment/field requirements (Required, Optional, Mandatory, etc.), size, and how each segment and field should be processed and formatted - something extra you won't find elsewhere.

Specification

• Database format - Microsoft Access 2007
• Includes Access form to edit data and a few queries to simplify interaction with this database
• 120 unique EDI segments, 773 fields
• 583 unique reference "tables" / 17,389 reference records total
• All segments and fields include Descriptions, Requirement info, Type info, Size (min & max)
• Many segments and fields include additional text information and Visual Basic style string format parameter

We are proud to present our mini EDI Translator. We wrote this tool to demonstrate capabilities of the above mentioned database and our X12 Object that does most of the magic.

The X12 Object simplifies interaction with EDI data. It is intended to be directly incorporated into your web-based software if it supports VB Script. If languages are not compatible, a web service option is available.

Examples of use

• Your e-commerce needs to pass the order into your other system
• Your CRM needs to communicate shipment information to the warehouse
• You want to update order/shipment status in originating system when it changes
• You want to provide shipment tracking number to the customer when order is shipped
• You want to capture some additional information from the X12 that your other system does not
• Any other small scale projects where buying full-featured EDI translator is not an option

Specification

• Language: VB Script (can be easily ported to VBA).
• Converts any X12 message into an object. There is no limitation on transaction set, version, etc.
• Converts object back to X12 message.
• Converts X12 into XML and JSON.
• Generates 997 Functional Acknowledgment (for complete messages).
• Capable of processing multiple ISA's.
• Capable of processing partial X12 message as small as one segment.
• Developer can construct blank X12 message, fill-up all necessary properties, and return X12 interchange.
• As an alternative to doing all "by hand", the object can be initialized with a template. In this case, developer only needs to update properties specific to this transaction - the X12 structure will be defined by the template.

Complete documentation will be posted as soon as it is completed.