Resolution:
Description:
============
When upgrading from EDI 5.3 to EDI 5.4, outbound transactions that previously worked with BusinessConnect start failing with EDI-XML validation errors.  The most common error seen is:

Transaction Validation Error

Node:  01: Transaction Set Identifier Code
Context:  Transaction-XXX | Segment-ST | Element-143
Location:  Segment:1 | Element:1
Category:  Rejecting
Severity:  Normal
Brief:  : Transaction Identifier Code and Functional Group Identifier Code mismatch. [ID=0x3939440]
Details:  Value of element ST01 (Transaction Set Identifier Code) does not match to value of element GS01 (Functional Identifier Code). Expected value of GS01 is 'HB' for this transaction type. Segment ST is defined in the guideline at position 010. This error was detected at: Segment Count: 1 Element Count: 1 Character: 1017 through 1020
ID:  0x3939440
Data:  [271] in [ &ltElement-143&gt271</Element-143> &ltElement-329&gt0005</Element-329> ]

Environment:
==========
TIBCO BusinessConnect EDI Protocol 5.4.X all versions

Resolution:
=========
The EDI 5.4 engine contains some upgrades to the XEngine that are more sensitive to the XML transaction header.  You can resolve the issue by changing the Transaction header XML (an example 271 header is shown below from this):

&ltTransaction-271 Type="Transaction" XDataVersion="1.0" Standard="HIPAA" Version="V4010X092" GUID="">

to this:

&ltTransaction-271>

Also, EDI 5.4 and EDI HIPAA 5.3 include revised guideline files for the HIPAA transaction which have been updated to the latest CMS (Center for Medicare and Medicaid Services) standards.  Consequently, transactions that may have been valid on previous versions of the EDI HIPAA product may generate validation errors with the new version.