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

Last updated on JULY 28, 2017

Applies to:

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

Symptoms

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.

Changes

 

Cause

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