Skip to Content

Hi everyone,

Are you developing against any of SAP Cloud for Customer’s SOAP inbound endpoints with SOAPUI? Are those asynchronous endpoints? Then you know the feeling when you encounter this message:

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
   <soap-env:Header/>
   <soap-env:Body>
      <soap-env:Fault>
         <faultcode>soap-env:Server</faultcode>
         <faultstring xml:lang="en">Web service processing error; more details in the web service error log on provider side
         (UTC timestamp 20180723070831; Transaction ID 00163E62DDE81EE8A3C8E6A1EFF2DB89)</faultstring>
         <detail/>
      </soap-env:Fault>
   </soap-env:Body>
</soap-env:Envelope>

On top of that C4C’s web service monitor shows no message error. So it is basically impossible to develop a request like that.

But worry no more, I am going to share a secret with you today. You need to alter your request URL in SOAPUI slightly and watch the magic unravel.

https://<serverId>.crm.ondemand.com/sap/bc/srt/scs/sap/<serviceName>?MessageId=${=java.util.UUID.randomUUID()}

Just replace the URL parameter “sap-vhost=<serverId>.crm.ondemand.com” with “MessageId=${=java.util.UUID.randomUUID()}” and you are good to go. Your request-responses however won’t show up on SOAPUI anymore since they are asynchronous. But C4C’s web service monitor will finally tell you if there is something wrong with your payload.

Actually there are several other blog posts that tell you about the solution but not in the context of the error message I provided earlier. Have a look here for example:

https://blogs.sap.com/2016/08/05/blog-post-general-issue-with-integration/

Once you know where to look it is obvious 😀 I hope this gets you up to speed with C4C’s asynchronous services.

Do you have any more SOAPUI tweaks to share? I’d love to hear about them.

 

Until next time – Thanks

Martin

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply