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.
Last updated on JULY 27, 2017
Applies to:Oracle Utilities Customer Care and Billing - Version 22.214.171.124.0 to 126.96.36.199.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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms