SteveDW

We are receiving the following error from BizTalk when attempting to create a 997 acknowledgment file for an inbound 837 Institutional file:

Event Viewer Error:

Error: 1 (Field level error)

SegmentID: AK4

Position in TS: 586

Data Element ID: AK44

Position in Segment: 4

Data Value:

6: Invalid character in data element

When we parsed the file and located the line in error, it turns out that the 837I contains a ">" character. There seems to be an issue related to the use of the ">" as a segment delimiter. The problem is manifested only if the inbound source file (e.g. 837) contains an actual error. This is because the segment data is directed to the 997, where these characters are used in the XML. This creates an error in the XML to EDI transformation. This issue surfaced based on the receipt of an 837I with the BE/BG out of sequence issue. If there is no error in the inbound 837I file, it is not necessary to use the data to build the 997, and thus there is no problem creating the 997 file.

Here is the actual line from the 837I:

HI^BE>45>>>99~



Re: BizTalk EDI and AS2 Error creating 997 acknowledgment for 837 Institutional

Mohsin Kalam 每 MSFT

Try opening the XML file and seeing what exactly is the character representation of the ">" in the XML. Since "<" and ">" are one of the special characters with respect to XML files, the receive pipeline should store them as &lt; and &gt; respectively if used in the data. If you see the actual characters in the XML file and not these codes, then the EDI assembler will throw the error because it confuses this with the opening and closing of a node. If you do indeed see them as is in XML, let me know and we can dig deeper

I ran a similar scenario with these two symbols as erroneous data and the 997 was correctly generated. I verified that these 2 characters were indeed represented with special codes in XML. I then serialized that XML and it worked like a dream.

Thanks

Mohsin Kalam

www.mohsink.com - blog about R2 EDI





Re: BizTalk EDI and AS2 Error creating 997 acknowledgment for 837 Institutional

SteveDW

Thanks Mohsin. We can see the representation in the file, as follows:

<AK44>BE&gt;BE&gt;&gt;&gt;3000</AK44></AK4>

So, if the reserve XML characters are being handled, what is causing the 997 EDI transformation to fail

I've provided the event log error again here:

Error: 1 (Field level error)
SegmentID: AK4
Position in TS: 586
Data Element ID: AK44
Position in Segment: 4
Data Value:
6: Invalid character in data element





Re: BizTalk EDI and AS2 Error creating 997 acknowledgment for 837 Institutional

Mohsin Kalam 每 MSFT

This is interesting. Could you email me the 997 if possible and I will try to run some test on it. My email is in my profile.

Thanks

Mohsin Kalam

www.mohsink.com - Blog about BizTalk R2 EDI





Re: BizTalk EDI and AS2 Error creating 997 acknowledgment for 837 Institutional

Mohsin Kalam 每 MSFT

Followed up offline with this customer. The problem was that the component separator being used under the party settings was colliding with a data field. The issue was fixed when the component separator was changed to a ":" from ">".

Considering this issue resolved.

Thanks

Mohsin Kalam

www.mohsink.com - Blog about Microsoft BizTalk R2 EDI