My Oracle Support Banner

Execution Of Pcm_op_pymt_topup Leads To Data Inconsistency In Case Of Error (Doc ID 738692.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
Information in this document applies to any platform.
This problem can occur on any platform.


There are two separate transactions opened during the process. The flow of PCM_OP_PYMT_TOPUP
opcode is:

1. open transaction for device/voucher update
2. close transaction for device/voucher update
3. open transaction for payment update
4. close transaction for payment update

If there is any type of error during payment processing, we face data inconsistency issue - device
is marked as used, but the money doesn't get to the subscriber balance.

-- Steps To Reproduce:
Produce an error during topup processing.

-- Business Impact:
A transaction rollaback could leave some data inconsistency behind.




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.