Subject:X12 Validation Author:Felix Santiago Date:01 Feb 2008 10:29 AM
I have a project to correct validation problems in ANSI837 files. I can read the file using the EDI to XML converter if I disable the validation and make all segments as optional. I would like to be able to determine where the validation fails so that I can correct the segment and output a file that is free of ANSI errors (missing elements, etc). Anyone has any suggestions on how to approach this project?
Subject:X12 Validation Author:Tony Lavinio Date:01 Feb 2008 12:08 PM
Using the EDIConverterException, it is possible to write a little EDI
validator. Here is how the code would look in Java. If you need a C#
version, I can post that as well.
It will write warnings and non-fatal errors to the console, and keep
going until it hits a fatal error or end-of-file.
Subject:X12 Validation Author:Felix Santiago Date:01 Feb 2008 12:19 PM
Thanks Tony. It looks complicated. :(
I was looking for something that could be set so that others will be able to do the correction to the file and revalidate. They can then upload the file to a clearinghouse for processing.
Subject:X12 Validation Author:Tony Lavinio Date:01 Feb 2008 04:15 PM
If you build that, you get a command line tool that can be used to
validate X12 and EDIFACT files.
Or, you can use Stylus Studio, and load the file. If there is an
error, it will report it, and you can fix it there.
Try File|Open, choose the X12 file, check the 'Convert using XML
Converters?' box, and select EDI. Errors will be shown during loading
if there is a problem. Then fix the EDI file, and retry until it
works.
Subject:X12 Validation Author:Felix Santiago Date:01 Feb 2008 08:11 PM
That is exactly the procedure I was following, however, there were too many errors so it is difficult to tell where the errors are in the file. Sometimes there may be over 1000 transactions.