Error The service request could not be processed When Invoking Siebel Inbound Web Service (Doc ID 2817917.1)

Last updated on JULY 17, 2023

Applies to:

Symptoms

When sending an inbound web service request from an external system into Siebel application, the webservice is getting consumed by Siebel, but the response is not generated properly.

Additionally, the following error messages are returned to the external system:

The behaviour occurs as follows:

1. Create a custom Siebel business service called 'XXX Product Syncronization BS' with a method 'SyncBenefitChange'.

2. Create an Inbound Web Service that invokes this custom business service 'XXX Product Syncronization BS' with a method 'SyncBenefitChange'.

For more information on this step, please refer to Siebel Bookshelf > Integration Platform Technologies: Siebel Enterprise Application Integration Guide > 5 Web Services > Invoking Siebel Web Services Using an External System

3. Generate the WSDL file for this Siebel Web Service.

4. Start up a 3rd party tool called SoapUI and import this WSDL file.

For more information on this step, please refer to Siebel Bookshelf > Integration Platform Technologies: Siebel Enterprise Application Integration Guide > 5 Web Services > Invoking Siebel Web Services Using an External System > Generating a WSDL File

5. Using the soapui tool to send a request for this web service request.

6. The reported error will occur.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.