Originally posted by: jdavee

We've been researching better ways to use WTX as a validator.  The problem is with custom type trees originating with the standard X12.  We have several data sets that deviate from ANSI standard X12 (mostly inherited junk data we've been trying to eliminate for years). 

WTX type trees for ANSI X12 are customized to accept the deviation.  When data comes in that fails to parse, WTX will mark it as invalid but we can't get a simple report as to WHY it failed.  Manual research is required.

Some tools like EDISim do a great job validating or analyzing X12 by ANSI standards.  The deviation is picked out and displayed very quickly.  But it won't accept these custom X12 files since they have acceptable deviations that EDISim will still pick out and reject.

EDISim uses SEF files to store the definitions for the X12.  SEF is an open format to define X12 data (and other types) that is human and machine readable.  It's a type tree of sorts.  I've found several other commercial X12 apps that support SEF files. 

Here's a link to info on SEF from the originators of the format:

http://www.edidev.com/articles/createIG/HowToCreateIG.html

We're currently researching how difficult it might be to edit SEF to support the customized X12, which would let EDISim validate our custom data.  I'd prefer something within WTX to do this.

So, has anyone tried to use SEF files with WTX?  Anything with WTX reporting validation or parsing issues in a readable form (not an incomprehensible trace file)?

Jim

Originally posted by: Laurent(Satisco)

Hi Jim,

I have no competences yet on SEF, but some on data validation/report

Have you tried using the Data Audit to get the details you need? It is usually the best place to get accurate information, and produition-suitable (for me, the mtr files are NOT production suitable). You may need to "tweak" the type trees a bit to help information to flow out, usually the right Identifier attributes in the right place will help

Best regards,

Laurent

Originally posted by: jdavee

Laurent, thanks for the reply!  I have a developer currently exercising the Audit settings to see if we can get closer to what we're after.

I'm also understanding how EDISim is able to report such detail on the issues it finds, and it again goes back to the SEF files.  Each validation point contains a description element and that's what gets reported.  I can quickly copy the description of the problem and send it right back to the source.  I'm having doubts that we'll be able to incorporate such detail in our type tree or audit settings, so we'll still have to have some type of lookup or repository to hold the descriptions.

WTX is really good at knowing there's a problem with the data and its parsing.  Getting it to communicate more than pass/fail is getting more interesting the deeper we go.

Jim