1

Closed

835 Error

description

Ran across an error that seems pretty consistent in a certain partner's 835 ERA files. The position seems to change a bit from file to file but it causes the fillowing error:

Unhandled Exception: OopFactory.X12.Parsing.Model.TransactionValidationException: Segment 'ISA*00* *00* *ZZ*MMISNEBR *ZZ*WWWWW *120130*1637*^*00501*000000032*0*P*>' in position 291 within transaction '8001' cannot be identified within the supplied specification for transaction set 835.
Parameter name: 835
at OopFactory.X12.Parsing.X12Parser.Parse(Stream stream)
at OopFactory.X12.X12Parser.Program.Main(String[] args)

Here's a deidentified sample.

Thanks!

Closed Feb 22 at 7:52 PM by dstrubhar

comments

dstrubhar wrote Feb 22 at 7:55 PM

Just checked in the fix at changeset 14543, thanks for the reminder.
I had to keep the interface the same for existing users, so I added a ParseMultiple method. The app will spit out multiple files if that's how you're calling it.

wrote Feb 22 at 7:52 PM

Resolved with changeset 14543.

nth wrote Feb 22 at 3:44 PM

Just checking to see if there's been any progress made on this... :)

dstrubhar wrote Feb 6 at 2:35 PM

Okay, I'll try and get something updated tonight.

nth wrote Feb 4 at 10:28 PM

Yep, multiple file output would be fine with me. Thanks!

dstrubhar wrote Feb 1 at 9:26 PM

I always assumed that each file would only have one interchange, but I guess that was an incorrect assumption. Since my root element of the output is the Interchange element, and xml file can only have one root, this problem would require a pre-processing step to split the file per interchange before the existing implementation of the parser will work.
Would that be an acceptable solution if the output were to produce more than one file?

Sign in to add a comment