Re-activating Service Legacy Accounts Are Being Charged In Full When Rate Is Set To Not Prorate
Last updated on JULY 02, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
The user has accounts that have been inactivated in 7.2. These accounts have products that are set to not to pro-rate last (pro-rate first and last are set to 701). When re-activating these services, there is a full fee being charged.
It is observed that these types of products look different in 7.5.
In 7.2, the charged_to date set to the date of the inactivation of the service.
Has BRM changed the nature of how PRORATE_LAST flag was implemented in 7.5?
It seems to be managed by the dates (that is to say, not modifying the CHARGED_TO_T upon inact with PRORATE_LAST set to 701). In 7.2, there was some other way the behavior has been implemented while the dates themselves look just like how the dates with PRORATE_LAST on 702 are managed.
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