Patch 25831084 did not solve the issue, Customer is still billed from SA start date when billing batch is run even if there is frozen bill exists.
(Doc ID 2290934.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Utilities Customer Care and Billing - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 2.5]
Information in this document applies to any platform.
If the last bill is system estimate and latest read is regular and when billing batch is run for the latest read then
Bill segment creates start date as SA start date instead of last frozen bill segment end date.
As suggested patch has been installed: "Customer Over-billed To The Original Service Agreement Activation Date (Doc ID 2269470.1)"
But still it is billing in the similar way.
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