PCM_OP_DEPOSIT_REVERSE_DEPOSIT - Unallocated Payment
(Doc ID 3038555.1)
Last updated on JULY 31, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Symptoms
The scenario is with reversal of the deposit amount.We call PCM_OP_DEPOSIT_REVERSE_DEPOSIT, then the original payment made during the PURCHASE_DEPOSIT will remain unallocated. Further we are calling the DEPOSIT_UPDATE_REFUND_REQUEST. Further using PCM_OP_BILL_REVERSE opcode used to reverse the payment manually - Item transfer is created , but the payment will remain unallocated(Item status -2 along with DUE).
Steps to re-create the scenario
1. Create the deposit with payment information - BRM will generate the Bill and allocate the payment to bill.
2. Call the reverse deposit opcode or use billing care to reverse the deposit.
3. We can see the payment made in step1 will move to unallocated.
4. When we revert the payment using opcode PCM_OP_BILL_REVERSE, there will be item transfer created, but the payment still be shown as unallocated in billing care.
1. Create the deposit with payment information - BRM will generate the Bill and allocate the payment to bill.
2. Call the reverse deposit opcode or use billing care to reverse the deposit.
3. We can see the payment made in step1 will move to unallocated.
4. When we revert the payment using opcode PCM_OP_BILL_REVERSE, there will be item transfer created, but the payment still be shown as unallocated in billing care.
Cause
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
Symptoms |
Cause |
Solution |
References |