SAP Knowledge Base Article - Public

2726983 - Unexpected Failure in SOAP Processing Occurred: No Web Service Configuration for This Access Path


You observe the following error message, or similar, while testing your custom created web service in SOAP UI:

Unexpected failure in SOAP processing occurred: "No Web service configuration for this access path: /sap/bc/srt/scs/sap/ABC (ABC relates to the service URL configured for Inbound/Outbound Communication)


  • SAP Cloud for Customer
  • SAP Business ByDesign
  • SAP Cloud Application Studio

Reproducing the Issue

  1. In C4C navigate to the Administrator WoC.
  2. Open the Communication Arrengement View
  3. Select the relevant communication arrengement.
  4. Click on the web service in question.
  5. Click on dowbload wsdl button.
  6. Open SOAP UI.
  7. Click File and choose New SOAP Project.
  8. Input the initial wsdl which you have downloaded in step 5.
  9. Configure Authentication tab, use basic authentication, enter user ID and Password for technical user present on your C4C system. This user must have needed privilages to alter the BO in question.
  10. Open WS-A tab and flag checkbox for "Enable WS-A addressing" as well as checkbox for "Randomly generate MessageId".
  11. Open WS-RM and flag the checkbox "Enable WS-Reliable Messaging, also change WS-RM Version to 1.1.
  12. Insert Payload into the request you have configured.
  13. Click send.

If the message has been succesfully send to C4C the response XML will be blank if you have an asynchronous web service.

In this case however you observe the following error message in the Raw tab of SOAP UI:

No Web service configuration for this access path: /sap/bc/srt/scs/sap/ABC



This issue may occur after the deployment of the solution as communication arrengement and communication scenarios may not be in sync anymore.



Communication arrengement has been created in the UI but all corresponsing communication scenarios have been created/altered in the SDK. To synchronised both,communication corresponding arrengement needs to be reactivated in the UI. This can be performed in the following way:

  1. Navigate to the Adminitrator WoC.
  2. Under General Settings choose Integration, and Communication Arrengements.
  3. Highlight Communication Arrengement in question and hit Reactivate button.

Perform this action after each deployment to avoide the issue.


No Web service configuration for this access path: /sap/bc/srt/scs/sap, SOAP UI, Custom web service, Inbound Service Interface , KBA , AP-RC-BDS-WS , ByDesign Studio Web Services , Problem


SAP Business ByDesign all versions ; SAP Cloud Applications Studio all versions ; SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions