BillingCare REST APIs Returning Same HTTPS Response and Error Code
(Doc ID 2751850.1)
Last updated on FEBRUARY 15, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
One user noticed the BillingCare REST APIs are returning the same HTTPS response (500) and error code "10001" message "The system is unable to complete the task. Contact your supervisor." on many occasions, whether it is actually an internal server error or a business error.
For example, the "Get Account Info" API returns the same set of errors when the account does not exist also when CM is down on the server, which is very confusing when trying to parse the response and take actions based on it. If CM is down, one would attempt to retry the request; but if the customer does not exist, no need retry the request.
Another example for changeServiceStatus and changeOfferStatus, when one is trying to cancel and offer or close a service while it is already cancelled/closed, there was also HTTP 500 response and the below payload:
<?xml version="1.0" encoding="UTF-8"?>
<errorMessage>Unable to change the status !</errorMessage>
Despite that there is not actual failure in BRM as the service is already closed or the deal is already cancelled. One would expecting to get something like "Service already closed" or "Deal already cancelled" and so no need to return the request again.
The documentation does not specify a list of error codes/responses expected from each API, and one would like to have more visibility on what to expect for the error handling design.
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