- This topic has 0 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
I’ve applied the hotfix and changed the schema to exclude the sibling data. Each claim is now in it’s own file with the 2300 loop falling below the 2000C patient loop instead of the 2000B subscriber loop as one would expect. The problem is when I try to use one of these newly split files as instance data for the 837 I schema in a map. When I Validate Instance I get the following errors:
Invoking component…
C:\bts\edisend\{304F6751-AD45-490D-8702-6223640754D1}.xml: error BEC2004: Segment level : Segment ID – CLM : Position – 27 : Segment Has Data Element ErrorsC:\bts\edisend\{304F6751-AD45-490D-8702-6223640754D1}.xml: error BEC2004 Segment level Field Error Segment ID - CLM Field Position - 2 : Current value - 1015.10 Invalid character in data element
C:\projects\EdiProcessorSingle\EdiProcessorSingle\Schemas\X12_00401_837_I.xsd error BEC2004 Validate Instance failed for schema X12_00401_837_I.xsd, file <file:///C:\bts\edisend\{304F6751-AD45-490D-8702-6223640754D1}.xml>.
Component invocation succeeded.
Has anyone run across this issue? I passed those same xml files to an existing BTS 2006 developer and they pass validation against the old 837I schema. I've also tried the pre sibling split versions and they pass validation. It's only the files generated with the Split_Without_Sibling_Data="Yes" that throw the errors above.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.