问题
I am working on a BizTalk inbound process to inbound 837-p files from different trading partners. After the file is processed inbound, I am also forwarding the BizTalk auto-generated 999 file to trading partners as an acknowledgement.
For a special trading partner, BizTalk inbound the 837 file and generated a 999 file claim all records in this file are "Accepted" in its AK9 segment.
But the continue process of these records from the file shows it have some records actually failed.
I saved one of the failed message as XML and validated it with the 837-p schema shipped with BizTalk, it actually failed in validation with following error:
error BEC2004: The element 'PRV_BillingProviderSpecialtyInformation' in namespace 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006' has incomplete content. List of possible elements expected: 'PRV03_ProviderTaxonomyCode'.
The question is, if the record actually failed in schema validation, why was the 999 generated with all records as "Accept"?
Some other info:
The EDI Validation is turned on in that trading partner's agreement.
I've double verified that all the setting in agreement are matching the incoming file.
This validation is actually a HIPPA level 2 validation. But per BizTalk document, it should support level 2 validation.
The BizTalk version is BizTalk 2013 with CU3 update.
回答1:
Finally figure it out. The missing element BizTalk complains is actually holds a single space character. So it passes the inbound validation, but the space char is trimmed later on in an orchestration. Then the error is raised.
来源：https://stackoverflow.com/questions/34278669/biztalk-generated-wrong-999-file