Initiate Stop Process For NBB SA Does Not Work Properly When An Overpayment Is Involved
(Doc ID 1939127.1)
Last updated on MAY 04, 2022
Applies to:Oracle Utilities Customer Care and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
CCB/CC&B - Oracle Utilities Customer Care and Billing
SA - Service Agreement
NBB - Non-Billed Budget
CCB v.220.127.116.11 / Linux x86
Create a CC&B account with 1 Utility SA (Electricity) for which create 1 bill of about 20 GBP.
Then create and activate 1 monitored NBB SA to cover the Utility SA.
Then setup the NBB to collect around 500 GBP and proceed with the payment against the NBB SA.
At that point, the balances are all correct and everything is normal.
Then initiate the NBB SA stop.
Expected the following main steps to happen:
1) Covered SA to be paid entirely as I have an excess of credit pending on the NBB SA.
2) Remaining Credit on the NBB SA to be moved on a automatically created Overpayment SA
3) NBB SA current balance to be synced with the NBB SA payoff balance so the NBB SA can be automatically closed as payoff would equal the current balance.
Above steps 1 and 2 are run correctly but the NBB SA stays in an ACTIVE status while having an end date populated and greyed out.
Clicking again on the Initiate stop and providing the same date actually synced the NBB SA balances and then properly stops the NBB SA - which also closes as all balances are null.
It looks like all the BASE initiate stop and stop algorithms plugged on the NBB SA Type have been called properly (to move the money on the utility sa/to create the overpayment SA/to move the excess of credit from the NBB SA to the
Overpayment SA) except that the system rolls back the NBB status from STOP to ACTIVE for an unknown reason.
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