My Oracle Support Banner

Errored Out Outbound Message Missing XML Raw Response (Doc ID 2762126.1)

Last updated on MARCH 26, 2021

Applies to:

Oracle Financial Services Revenue Management and Billing Cloud Service - Version NA and later
Information in this document applies to any platform.


On RMB v2., Errored out outbound message is missing XML Raw Response.

We have a requirement to display the actual error message when processing a outbound message.
It is noted that we do not get the XML Raw Response if the outbound message is errored out.
Outbound messages when failing with HTTP Response code 500, may still contain failure reason. In the current approach, when HTTP Response code of 500 is received by the application (Framework), it does not store the response text and only keeps the Outbound message in 'Error' status with a generic error message. This restricts the business users from understanding the reason for failure.

Ex: For Tax calculation we use Vertex API calls which calculates Tax based on customer's location (Country/Postal/State/County). In case the address is missing a required field or an invalid value is sent in the request, API sends a response with HTTP Response code 500 and response text contains reason for error which Business users can use to fix the customer address.

So the requirement is to store the xml raw response even if the outbound message is in Error status. So we can retrieve the error details from XML Raw Response of the outbound message.
This option will help to retrieve the error details from XML Raw Response of the outbound message.

Currently Outbound message fails with status error but the error details sent by external system are discarded and only a generic error is stored on error message column.
"Problems invoking sender : Internal Server Error, status code (500)."

1. Create a Message Sender using RTHTTPSNDR.
2. Configure this Message sender on an Outbound message type of a external system .
3. Call external API by creating an Outbound Message using this External system and outbound message type.
4. External API should fail with a HTTP Status code of 500 and should also contain error details.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.