Recent changes to bugs

Improper sequencing noted with segment L3

2014-11-18T10:42:30.650000Z

I am trying to parse a X12 EDI file of 110 - 004060 . But when I tried to run the file it shows the

ERROR: 'Improper sequencing noted with segment L3 at segment 556, field 1'

Failure to transform: javax.xml.transform.TransformerException: com.berryworks.edireader.EDISyntaxException: Improper sequencing noted with segment L3 at segment 556, field 1
com.berryworks.edireader.EDISyntaxException: Improper sequencing noted with segment L3 at segment 556, field 1

From the analysis, I found that, L3 tag is appending to the <loop Id="L1">...

<loop Id="LX"><segment Id="LX"></segment><loop Id="N1"></loop></loop><loop Id="*"></loop><loop Id="*"> .... <loop Id="L1">....

basically it has to be outside the loop.

<LX>...</LX><LX>....</LX><L3><L305>746.14</L305></L3>

Please help me, what should I do now?

UNB/recipient reference parsed incorrectly

2007-09-21T09:16:03Z

When parsing an EDIFACT interchange, in the UNB segment all data elements after 0020 (interchange control reference)are handled as simple.
However, S005 (recipient reference, password) is defined by the standard as a composite one, having an optional qualifyer.
So if I have the following input:

UNB+UNOD:3+TANF2+TANF1+070920:0941+17+RECREF:122+INVOIC'

the following XML is generated:

Whereas INVOIC should go into the ApplRef attribute, and "RECREF:122" should appear somewhere.
Probably there should be a "ReceiverRef" and a "ReceiverRefQual" attribute in the interchange element.

regards
Simon Laszlo
simi6934@t-online.hu

835 PLB segment - Improper sequencing

2007-03-23T13:06:52Z

From the source I downloaded 3/20/07, I parsed an 835 with a PLB segment in it (appears in the footer right above the SE segment). I get the error 'Improper sequencing noted with segment PLB at segment 22017, field 1. From tracing through the code, I noticed that from loop level 2 you try to close three levels of loops (I guess to go to level zero). When I take out the check in your code that is checking this condition, a IndexOutOfBounds exception occurs. I worked around it by changing the LoopDescriptor assigned for the PLB segment to use loop level 1 like this:

---------
public ANSI_835() {
super("835", "Health Care Claim Payment Advice");
loops = new LoopDescriptor[] { new LoopDescriptor("1000A", "N1"),
new LoopDescriptor("1000B", "N1", 1, "1000A"),
new LoopDescriptor("2000", "LX", 1),
new LoopDescriptor("2100", "CLP", 2),
new LoopDescriptor("2110", "SVC", 3),
new LoopDescriptor("", "PLB", 1), };
}
-----------

This results in a complete parsing, but represents the PLB in a loop with Id="".

I think the intent of the level 0 loop was to go back to the interpretation of segments you get when you start parsing a document before the loops start.

Here is the last part of console debug log. Please forgive me for not posting my x12 source as it contains patient data. I don't think it would be hard to reproduce this error - just add a PLB segment:
...nextToken in the QTY
...nextToken in the QTY
parsing segment CLP within the 835 document
considering segment CLP while in loop 2100 with stack /2000/2100
plugin query for segment CLP
Number of descriptors found: 1
checking level context -1
checking loop context * with current loop stack /2000/2100
considering segment CLP using descriptor loop 2100 at nesting level 2: encountering segment CLP anytime
transitioning to level 2
closing 1 loops
popped LoopContext loopName:2100 position:0 repetitions:0 mandatory: off the stack
pushed 2100 onto the stack
closing 1 loops
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
...nextToken in the CLP
parsing segment CAS within the 835 document
considering segment CAS while in loop 2100 with stack /2000/2100
plugin query for segment CAS
No descriptors found
considering segment CAS using descriptor null
...nextToken in the CAS
...nextToken in the CAS
...nextToken in the CAS
...nextToken in the CAS
parsing segment NM1 within the 835 document
considering segment NM1 while in loop 2100 with stack /2000/2100
plugin query for segment NM1
No descriptors found
considering segment NM1 using descriptor null
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
parsing segment NM1 within the 835 document
considering segment NM1 while in loop 2100 with stack /2000/2100
plugin query for segment NM1
No descriptors found
considering segment NM1 using descriptor null
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
...nextToken in the NM1
parsing segment REF within the 835 document
considering segment REF while in loop 2100 with stack /2000/2100
plugin query for segment REF
No descriptors found
considering segment REF using descriptor null
...nextToken in the REF
...nextToken in the REF
parsing segment DTM within the 835 document
considering segment DTM while in loop 2100 with stack /2000/2100
plugin query for segment DTM
No descriptors found
considering segment DTM using descriptor null
...nextToken in the DTM
...nextToken in the DTM
parsing segment DTM within the 835 document
considering segment DTM while in loop 2100 with stack /2000/2100
plugin query for segment DTM
No descriptors found
considering segment DTM using descriptor null
...nextToken in the DTM
...nextToken in the DTM
parsing segment QTY within the 835 document
considering segment QTY while in loop 2100 with stack /2000/2100
plugin query for segment QTY
No descriptors found
considering segment QTY using descriptor null
...nextToken in the QTY
...nextToken in the QTY
parsing segment PLB within the 835 document
considering segment PLB while in loop 2100 with stack /2000/2100
plugin query for segment PLB
Number of descriptors found: 1
checking level context -1
checking loop context * with current loop stack /2000/2100
considering segment PLB using descriptor loop at nesting level 0: encountering segment PLB anytime
transitioning to level 0
closing 3 loops
ERROR: 'Improper sequencing noted with segment PLB at segment 22017, field 1'

Failure to transform: javax.xml.transform.TransformerException: com.berryworks.edireader.EDISyntaxException: Improper sequencing noted with segment PLB at segment 22017, field 1
com.berryworks.edireader.EDISyntaxException: Improper sequencing noted with segment PLB at segment 22017, field 1

Multi-Thread issue

2006-05-02T09:34:11Z

When lots of threads are submitted for big files,
EDIException for format errors are thrown. Single
thread working properly. Inspecting the code

EDIReaderFactory.java
has
protected static EDITokenizer tokenizer;

which is giving problems for many threads.
I have commented the static variable and changed
public static EDIReader createEDIReader(InputSource
source, boolean debug)
throws EDISyntaxException,
IOException {
EDIReader parser;
Reader inputReader =
EDIAbstractReader.createReader(source);
// NEW LOCAL VARIABLE Instead of static
EDITokenizer tokenizer=null;

Incorrect path to jar's in Inspect scripts

2006-04-18T15:03:57Z

The inspect scripts will fail because they reference
version 3.6 of the jar files instead of 3.7

i.e. The correct lines in Inspect.sh should be:
set CP=%EDIREADER_HOME%\edireader-3.7.jar
set CP=%CP%;%EDIREADER_HOME%\edireader-plugins-3.7.jar

Instead of:
set CP=%EDIREADER_HOME%\edireader-3.6.jar
set CP=%CP%;%EDIREADER_HOME%\edireader-plugins-3.6.jar

Invalid 997 generated

2005-09-14T19:30:52Z

The 997 generated closes the AK1 (Functional Group)
Response Header with AK5 (Transaction Set Response
Trailer), when it should be closed with AK9 (Functional
Group Response Trailer).
There is also no way to send the following responses,
it always sends A (Accepted):

E Accepted, But Errors Were Noted.
M Rejected, Message Authentication Code (MAC) Failed
P Partially Accepted, At Least One Transaction Set Was
Rejected
R Rejected
W Rejected, Assurance Failed Validity Tests
X Rejected, Content After Decryption Could Not Be Analyzed

Also, you may want to use java.text.DateFormat instead
of formatting dates yourself.