CAUSE
The
GlobalBusinessIdentifier attribute is generated in the RNIF 1.1 Acknowledgement message by
the Rnmsgtoackall.xml map file. The Extensible Stylesheet Language Transformations (XSLT) logic in the Rnmsgtoackall.xml map
file checks for the presence of the
GlobalBusinessIdentifier attribute directly under a
BusinessDescription element as follows:
<PartnerRoleDescription> <PartnerDescription> BusinessDescription GlobalBusinessIdentifier
The document
definitions that are associated with a 3C3 PIP and with a 3C4 PIP maintain the
GlobalBusinessIdentifier attribute directly under a
BusinessIdentification element as follows:
<PartnerRoleDescription> <PartnerDescription> BusinessDescription BusinessIdentification GlobalBusinessIdentifier
The
document definition that is associated with a 3C3 PIP and with a 3C4 PIP maintain the
GlobalBusinessIdentifier attribute in a different location. Therefore, this value is never populated
by the Rnmsgtoackall.xml map file when a RNIF 1.1 Acknowledgement message is generated
for a 3C3 PIP document and for a 3C4 PIP document.
RESOLUTION
To install the Microsoft BizTalk Accelerator for RosettaNet 2.0 hotfix
rollup, visit the following Microsoft Web site:
The BizTalk Accelerator for RosettaNet 2.0 hotfix rollup contains an updated
Rnmsgtoackall.xml map file that derives the
GlobalBusinessIdentifier value from the "ServiceHeader" section of the document instead of from the "ServiceContent" section. The location of the
GlobalBusinessIdentifier attribute in the "ServiceHeader" section is consistent for all RNIF 1.1 document schemas.