Wrong TOTAL_DUE Calculation During Bill Suppression
(Doc ID 2614200.1)
Last updated on DECEMBER 02, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
For Open Item Accounts, it was observed that TOTAL_DUE calculation is wrong while running bill suppression. TOTAL_DUE is set as a cumulative value for all the previous unpaid bills which is wrong.
According to Billing and Revenue Management (BRM) documentation (Oracle® Communications Billing and Revenue Management - Concepts (Paragraph - "About Accounting Types")), the TOTAL_DUE should be equal to bill's DUE, not cumulative:
With open item accounting, a customer is billed only for charges from the bill items in the current bill. If a customer does not pay a bill, the next bill does not include charges for the bill that the customer did not pay.
With balance forward accounting, a customer’s bill includes all the charges that a customer owes, including those from previous billing cycles. If a customer does not pay a bill, the next bill includes the charges from the previous bill.
Suppression opcode PCM_OP_BILL_POL_CHECK_SUPPRESSION is using TOTAL_DUE to compare with the minimum balance amount configured in pin_bill_suppression.xml file. Because TOTAL_DUE is not correctly calculated, the suppression rule about bill minimum amount is failing validation.
See below some billing data along with snippet from the cm log file for a better understanding:
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