Empty Soap Message In Outbound We Service due to input argument name containing a dot

(Doc ID 2299665.1)

Last updated on AUGUST 22, 2017

Applies to:

Siebel CRM - Version 8.1.1.14.14 [IP2014] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.14.14 [IP2014] version, Siebel EAI

ACTUAL BEHAVIOR
---------------
A newly developed outbound web service is failing unit tests because the SOAP request leaving siebel has an empty SOAP body.

EXPECTED BEHAVIOR
-----------------------
SOAP Body should have the data required by the external system.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. import LN_IN_STOCK_AVAIL.1.wsdl in Siebel Tools to generate business service 'LN_IN_STOCK_AVAIL_PortType'
2. < create a custom workflow process named 'LN Stock Inventory Search Process'
3. Add a step to invoke business service 'LN_IN_STOCK_AVAIL_PortType'
4. pass as input an instance of integration object named StockAvailability, having
ProductPguid = urn:product:9999999
LineOfBusiness=New Zealand
transId=12313*
SourceAppName=XXXXX
5. change param enableserviceargtracing=true for comp eMediaObjMgrOUI_enu
6. Notice OutboundDispatcher_output_args_0_018_.dmp, which contains the SOAP request from Siebel, has an empty soap body.
The data in #4 above is not present there.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot complete the development of this new outbound web service.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms