Unable to get iteration basis address
› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Unable to get iteration basis address
- This topic has 9 replies, 2 voices, and was last updated 8 years, 6 months ago by
Jim Kosloskey.
-
CreatorTopic
-
June 1, 2016 at 5:07 pm #55095
Can anyone tell me what Unable to get iteration basis address ‘5(%g1).2(0)’ means? -
CreatorTopic
-
AuthorReplies
-
-
June 1, 2016 at 6:50 pm #84061
It means that address path does not exist I think.
Run your inbound message through the associated message testing tool (HL/7, X12, etc.) and see if that address path (sans the %g1) appears in the output. I would set the display to level 1 or higher until I can see the fulll address path.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
June 1, 2016 at 7:06 pm #84062
Thank you! I tried running the 837P through 5010 and HIPAA-005010A1.
I get multiple rows stating
[0:TEST] [mid:0xd78710] The # 333 segment encountered ‘N4’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
And then many rows that are correct but then the file doesn’t finish. It gets down to the LX Assigned # but then the garbage above comes out at the sv2 line.
-
June 1, 2016 at 10:27 pm #84063
It appears the 837 you are getting does not match any of those standards.
You may need to make your own variant (but you should not if they are X.12 compliant).
Make sure you only have one message and that you have stripped the envelope off.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
June 6, 2016 at 7:08 pm #84064
Hi Jim, Thank your for the update. I will try with one st. But unfortunately the file comes in with multiple st’s. When you talk about x.12 compliant could you be more specific?
-
June 6, 2016 at 9:14 pm #84065
What version did the sending system indicate they were built at (003020, 004010, 004030, 005010, 005040, etc.)?
If it is one of the versions you tested with, you have eliminated the envelope, are using only one ST, and you are receiving the ‘out of sequence’ and other errors from the X12 tester then it could be the messages you are receiving do not match the standard indicated.
Could be they have a segment or group misplaced or out of order or they are not providing a required group or segment.
Hopefully it will be easier to diagnose once you reduce to just one ST.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
June 6, 2016 at 9:36 pm #84066
I just noticed you are specifying the HIPPA variant.
I suspect things might work better using the appropriate version number (004010, 005010, etc.) non-HIPAA.
Last time I tried to use the Cloverleaf provided HIPAA variants I had no success. I noticed that apparently an effort was made to try and simplify the work by defining the loops as individual repeating groups in these variants. Unfortunately, in my experience, this did not work for me but using the non HIPAA variants for the same version did.
If that is true, then also unfortunately you will probably need to rework your Xlate(s).
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
June 8, 2016 at 6:57 pm #84067
We MUST use HIPPA compliant files.
I tried it and got the below when I ran the x12 test.
Please Wait ……
Command Issued: hcixlttest -i -e ASCII -d 3 -f eof -F nl -p “{COMPONENT {|}} ” 837P_to_vrlmultiplegroups.xlt “E:/cloverleaf/cis6.1/integrator/vhspclvrapp1/data/837I Clean Short Claim file no isa.edi” “E:cloverleafcis6.1integratorvhspclvrapp1data837I Clean Short Claim file no isa results”
Command output:
MESSAGE 1
[0:TEST] [mid:0x1b83480] The # 39 segment encountered ‘SV2’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 40 segment encountered ‘DTP’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 41 segment encountered ‘LX’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 42 segment encountered ‘SV2’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 43 segment encountered ‘DTP’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 44 segment encountered ‘LIN’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 45 segment encountered ‘CTP’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 46 segment encountered ‘HL:0’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
[0:TEST] [mid:0x1b83480] The # 47 segment encountered ‘PRV’ is out of order when parsing x12 (HIPAA-005010A1 {}) for message type ‘837’. Segment ignored.
-
June 8, 2016 at 6:58 pm #84068
Attaching what I have so far . . . . Why can’t I attach a file????
-
June 8, 2016 at 9:14 pm #84069
I was not suggesting you use differeent files but rather the 005010 varinat provided rather than the HIPAA-005010 variant.
I notice Cloverleaf is complaining about there being to ISA/IEA so perhaps you need thosor the testing tool on the release of Cloverleaf you are using.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
-
AuthorReplies
- The forum ‘Cloverleaf’ is closed to new topics and replies.
