3636810 - No Payload Data Visible In Web Service Message Monitoring in C4C

Payload Data is not Visible in Web Service Monitoring view in C4C.

SAP Cloud For Customer

1. 1. Login to C4C.
2. 2. Navigate to Administrator.
3. 3. Click on Web service monitoring -> Enable the trace.
4. 4. Perform the calls.
5. 5. Navigate back to web service monitoring screen.
6. 6. Notice the service interface name.
7. 7. Click on the service and check the payload.
8. 8. Notice that the payload is empty.

In case of synchronous web service calls, successful calls of this type are not recorded by default in web service message monitoring for the primary reason that the source system will get an instant response with the result of the transaction. Failed calls will be logged on web service message monitoring which are raised by SOAP Run-time, but the payload contents are not stored.

This is an expected system behaviour.

Kindly note - To capture the internal trace for the standard service interfaces, the trace should be active when the request payload is triggered in order to save the payload contents. To activate it, Go to Web Service Message Monitoring, click "Start Trace" button, then perform your calls. The payload contents will then be visible in the monitor after that the request was triggered.

For custom service interfaces (workaround) you can follow the steps in your chrome browser to go 3 dots -> More tools -> developers tool - > network trace, you can see all the calls including the custom solution.

Payload for synchronous calls , No payload data in Web Service Message Monitoring , empty payload , c4c  , KBA , LOD-CRM-INT-ERP , Integration of C4C with ERP , Problem

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions