Hello!
We've been running into an issue with one of our clients who is utilizing the stock EBS / OTM integration provided by Oracle. After applying certain EBS patches, we get the following error while trying to send deliveries to OTM:
Code:
+---------------------------------------------------------------------------+
Shipping Execution: Version : 11.5.0 - PROD
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
WSHOOCHL module: Shipping-Transportation outbound interface - Child
+---------------------------------------------------------------------------+
Current system time is 01-JUN-2007 12:01:01
+---------------------------------------------------------------------------+
Id Low : 122893426088
Id High : 122893426088
Entity Name : DELIVERY
Batch size : 50
IdList Query select delivery_id id , name from wsh_new_deliveries where tms_interface_flag in ('CP','UP','DP') and delivery_id between :1 and :2
Ids Picked up 1
122893426088 Hash Table Entry 122893426088
Launching Bpel process for batch 1
DELIVERY processed in this batch
122893426088
In the method getDBToken
In the method buildPayload
Input XML to be passed to the BPEL process
Calling SoapBpelInvoker.callWebService
Endpoint http://bpel.company.com:7777/orabpel/default/WshSendTxnToOtmService
Response XML<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>org.xml.sax.SAXParseException: Element or attribute do not match QName production: QName::=(NCName':')?NCName. </faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">bpel.company.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
authenticated null
OTM Transmission Id null
ReturnStatus from BPEL process: null
java.lang.NullPointerException
at oracle.apps.wsh.outbound.cp.request.OutboundChild.runProgram(OutboundChild.java:238)
at oracle.apps.fnd.cp.request.Run.main(Run.java:148)
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
Entering WSH_OTM_HTTP_UTL.GET_SECURE_TICKET_DETAILS (WSHGLHUB.pls 115.0.11510.7) (06/01/2007 12:01:01 AM)
l_operation=WSH_SEND_TO_OTM_OUTBOUND ==>
l_argument=OUTBOUND_POST ==>
l_edate=01-JUN-07 12.01.01.000000 PM ==>
Ticket Exists. Valid and not expired ==>
x_return_status ==> S
Exiting WSH_OTM_HTTP_UTL.GET_SECURE_TICKET_DETAILS (06/01/2007 12:01:01 AM, .02 seconds)
************Summary of Shipping API Calls************
WSH_OTM_HTTP_UTL.GET_SECURE_TICKET_DETAILS : 1 calls : .02 seconds
*****************************************************
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 01-JUN-2007 12:01:01 AM
+---------------------------------------------------------------------------+ From the error, we can tell that EBS is trying to post to BPEL, but is encountering an XML parsing error.
Strangely enough - this isn't happening with the other clients who are also using this integration, so it may be related to a custom patch.
To resolve the issue, we needed to open an SR with Oracle and gain access to internal copies of the appsborg.zip and appsborg2.zip libraries which are known to work with the EBS / OTM integration. Each time these are overwritten, we need to copy these particular libraries into place ($COMMON_TOP/java) and overwrite the updated versions.
Sometimes EBS needs to be restarted, but usually it doesn't.
Hope this helps!
--Chris