Error in Receive Response process starter when receiving a response from the BC EDI protocol.

Error in Receive Response process starter when receiving a response from the BC EDI protocol.

book

Article ID: KB0093615

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream -
Not Applicable -

Description

Description:
When processing an INITIATOR.RESPONSE message from BC after sending an outbound X12 transaction, the BW process starter throws an exception as follows:



s0:ErrorReport xmlns:ns0 = "http://www.tibco.com/pe/EngineTypes">
<StackTrace>Job-60000 Error in [BusinessProcesses/Interfaces/Receive X12 855.process/ReceiveResponse] Output data invalid  at com.tibco.pe.core.ProcessGroup.a(Unknown Source)  at com.tibco.pe.core.ProcessGroup.eval(Unknown Source)  at com.tibco.pe.plugin.Activity.eval(Unknown Source)  at com.tibco.pe.core.TaskImpl.eval(Unknown Source)  at com.tibco.pe.core.Job.a(Unknown Source)  at com.tibco.pe.core.Job.k(Unknown Source)  at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source)  at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source) caused by: org.xml.sax.SAXException: validation error: Resolution problem: Element '{http://www.tibco.com/ns/ax/bc/EDI/2002/10/nonAeschema}notificationResult' defined in at least two fragments ('997/notificationResult.xsd' and '850/notificationResult.xsd')   ({com.tibco.xml.validation}InvalidComponentResolution) at /{http://www.tibco.com/ns/ax/bc/EDI/2002/10/aeschema}ReceiveResponseOutput[1]/{http://www.tibco.com/ns/ax/bc/EDI/2002/10/aeschema}body[1]/tns:notificationResult[1] com.tibco.xml.validation.exception.InvalidComponentException: Resolution problem: Element '{http://www.tibco.com/ns/ax/bc/EDI/2002/10/nonAeschema}notificationResult' defined in at least two fragments ('997/notificationResult.xsd' and '850/notificationResult.xsd')  at com.tibco.xml.validation.state.driver.ValidationJazz.a(ValidationJazz.java:1495)  at com.tibco.xml.validation.state.driver.ValidationJazz.startElement(ValidationJazz.java:326)  at com.tibco.xml.validation.state.glue.XmlTreeNodeValidationDriver.xmlTreeNode(XmlTreeNodeValidationDriver.java:72)  at 

. 
.
.
.


Symptoms:
As described above.
Cause:
The payload in the INITIATOR.RESPONSE message does not conform to the schema configured for the configured transaction. The payload returned is usually an abbreviated status message such as:

<tns:notificationResult xmlns:tns = "http://www.tibco.com/ns/ax/bc/EDI/2002/10/nonAeschema">
<tp>
<tpName>ExampleTradingPartner</tpName>
<statusCode>200</statusCode>
<statusMsg>EDI Document has been sent to the Trading Partner successfully.. Raw EDI File is stored in location: /usr/tmp/testEDI/arch/Out/ExampleTradingPartner/us1-esbapp-d01.corp.xxx.org-Interior-Server-ExampleTradingPartner-2015-10-23--12-h-01-m-02-s-629-ms.edi</statusMsg>
</tp>
</tns:notificationResult>

Resolution

Uncheck the "Parse XML payload" checkbox on the Receive Request process starter. This will allow the payload to be passed to BW unparsed.

Issue/Introduction

Error in Receive Response process starter when receiving a response from the BC EDI protocol.

Additional Information

BusinessConnect EDI Protocol Users' Guide.
Powered by Wolken Software