BusinessConnect (BC) EDI protocol is throwing Outbound XML to EDI Validation Errors.
Article ID: KB0093692
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Description:
When processing an outbound transaction, the BC engine throws an error indicating that a map is missing when processing an outbound transaction. This happens when the transaction has a map configured in the BusinessAgreement for a trading partner.
Symptoms:
Cause:
The BusinessAgreement settings get cached inside the BC engine and the cache is not always updated correctly when updating the BusinessAgreement with a new map. The issue can be addressed by stopping and starting the BC engines.
When processing an outbound transaction, the BC engine throws an error indicating that a map is missing when processing an outbound transaction. This happens when the transaction has a map configured in the BusinessAgreement for a trading partner.
Symptoms:
The error manifests itself as follows:
2014 Apr 28 16:06:15:200 GMT -4 BW.BusinessConnect-OutBatch-08 Debug [bw.logger] BW-EXT-LOG-300002 Job-79105454.79105454 {statusCode=699, tpName=FACETS, closure=null, extraInfo= <statusDetail>
<description>XML to EDI conversion error. Error code : 174. Message is : Missing Map.</description>
it l
Cause:
The BusinessAgreement settings get cached inside the BC engine and the cache is not always updated correctly when updating the BusinessAgreement with a new map. The issue can be addressed by stopping and starting the BC engines.
Issue/Introduction
BusinessConnect (BC) EDI protocol is throwing Outbound XML to EDI Validation Errors.
Resolution
A defect has been filed against BusinessConnect, and this issue is expected to be resolved in a future version of BC.
Feedback
Yes
No
Powered by
