Event_billing_charge_t.bill_obj Has the Wrong Bill Reference
(Doc ID 3006764.1)
Last updated on MARCH 06, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
event_billing_charge_t's bill_obj has the wrong bill reference while handling the transactions.
The table event_billing_charge_t's bill_obj reference doesn't link to the bill object which opens while using the transaction handling. The pymt_collect opcode takes the last bill object instead of the open bill object.
Steps to reproduce the issue:
The Account has a dispute item and is trying the payment while doing the settlement.
- Open RW transaction
- Apply for settlement.
- Try Auth payment
- Abort/Commit
After payment, the event_billing_charge_t has the wrong bill object reference (last billed bill obj) but we expected the bill object which got settled (open)
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 |