Stopped SA With Billable Charge Did Not Create Closing Bill
(Doc ID 2988415.1)
Last updated on NOVEMBER 21, 2023
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.5.0.2.0 and laterInformation in this document applies to any platform.
Goal
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
CCB - Oracle Utilities Customer Care and Billing
BC - Blanket Contract
SA - Service Agreement
On : 2.5.0.2.0 version, ENV - Environment
Stopped SA with Billable Charge did not create Closing Bill
When generating a bill for a stopped SA, the bill segment "Closing" flag is not being ticked indicating that the bill was not a Closing Bill. The understanding is that CCB automatically sets the Closing flag whenever the Bill Segments SA was already stopped for the bill period. Below are the steps to recreate the issue:
1. Created Billable Charge for the SA with period 01-06-2023 to 30-06-2023
2. Stopped the utility SA with an end date same as the end date of the Billable Charge which is 30-06-2023
3. Generated the bill with cut-off date of 30-06-2023.
4. Freeze the bill.
Validating the results. the frozen bill segment shows that the Closing flag is not ticked. Expected result is that the Closing flag should have been ticked.
Solution
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
| Goal |
| Solution |
| References |