PCM_OP_PYMT_COLLECT Returns Error "Service Unavailable" But BRM Creates Payment In Database

(Doc ID 1303193.1)

Last updated on DECEMBER 13, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.


In an End-to-End context (Siebel->AIA->BRM) when a payment is created, sometimes,  the following BRM behavior was detected:

1. AIA called PCM_OP_PYMT_COLLECT opcode to create a payment;
2. BRM returned error: "Service Unavailable";
3. But BRM created the payment, i.e. /item/payment object was created and related event objects: XXX/cash. The transfer event object isn't created and, of course, the payment allocation isn't performed.

Business impact :
After the Siebel users get this error, they are retrying to create the payment again and again and the result is that, multiple payments(items and events) are created when the expected result (for end user perspective)
should be just once. So the expectation in this situation is that, when such an error is raised, no payment information should get stored in database.

It looks like BRM doesn't rollback entire transaction and the payment stays created on BRM database, even though there is an error.

Note: Here the payment batch contains only single payment.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms