Error log in API log

[EtienneJacquet]

Hello,

When using the API to post activity allocation, we cannot use the error message as it refers to additional message in backend. For example, the following message is available in the log:

  LastError           = org.apache.cxf.binding.soap.SoapFault: Web service processing error; more details in the web service error log on provider side (UTC timestamp 20190301124225; Transaction ID 5b5ef394aa3a4de2b3548a4cc2bf9723) The error log can be accessed by service provider from SAP backend

Is there any way to view the error log, without the access to the SAP Backend?

Kind regards,

Etienne

[Amith_Nair · Accepted solution]

Hi Etienne,

In addition, we have a second option, which is the most preferred method since you get the details within S4HCloud tenant itself.

We have an app for tracking all asynchronous messages(SOAP API's) called Message Dashboard. With Message Dashboard, you can track error logs, a replica of most of what we see in the back end to identify the cause of the issue.

You can check the details on its availability for the specific service in question by going into api.sap.com and identify your SOAP API and click the business documentation. Here, you will find a section called 'Message Monitoring and Error Handling'- refer Fig 1 . Attached is the use case for Service Order API. To set up this service in the message dashbaord- you can review this blog on how to set up Message Dashboard for monitoring your service.

https://blogs.sap.com/2018/11/07/how-to-enable-users-to-work-with-the-message-dashboard/

Once you have set this up you will find the list of failed and successful messages along with root cause as to why it failed against the respective dates(when you triggered them). you can refer to fig 2

Hope this insight helps.

Thank you! Amith Nair

[Amith_Nair]

Hi Etienne,

Yes, it is possible if you can call the service in a middleware platform, that way you’ll be able to know what is missing in the payload. I can basically explain this using SAP’s preferred middle Platform- Cloud Platform Integration (CPI) as a use case.

In CPI

Develop a simple iFlow by passing the SOAP API into a ‘Content Modifier’ and connect that to Groovy Script that way you can review the SOAP payload that was sent. Deploy and make a note of the end point URL as depicted in Fig 1 and Fig 2

In S4HANA Cloud Tenant

Now, go to the Communication Arrangement(CA) for the service you have defined in your S4HANA Cloud tenant.

Edit the Communication arrangement and provide the end point service URL that you made a note from the CPI (Fig 2) and save your changes.

Please refer to Fig 3

I am assuming you’re using SOAP UI/Postman to trigger the API. After triggering the API, you can review the logs in the Message Monitoring tile in CPI for the respective iFlow that you deployed.

The logs will help you determine if there are any disconnect/discrepancy with the input data you have provided.

Hope this helps!

Thank you! Amith Nair