on 2024 Apr 01 2:52 PM
Hi,
Scenario:
We are trying to post data to S4 OData api from sap CI and we want to test the exception handling part whenever there is failure in data posting to S4 . The error has to be captured and sent as a mail alert.
I can see that CamelExceptionCaught contains error message as "Bad Request 400", but I need the actual error message, like "No delivery available for update".
In the OData Response body attachments i can see the actual error reason, but its not getting stored anywhere in the header or properties.
You get the response body from the exception. There is no need to read MPL. There is sample for the script to do this in the documentation.
https://help.sap.com/docs/integration-suite/sap-integration-suite/handle-exceptions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dinu, thanks for the reply. i tried this before but it didnt work.
I tried with the 2nd script in link, odata v2 receiver adapter script. it logs three additional attachments in CI, as shown below. It was logging odata post url, previous step payload, http status code. And there are no headers or poperties which actually specifies the reason for bad request.
Property:
Header:
User | Count |
---|---|
112 | |
9 | |
8 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.