Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.1 [Release 7.3.0]
Information in this document applies to any platform.
Checked for relevance on 11th March 2011
Checked for relevance on 12-June-2013.
The user has a number of rateplans in Pipeline. The way it has been structured is that there is a basic rateplan called VCOM which has all the rates which are common for all
the destinations. Then there are additional/delta rateplans like EVE_WEND, ANYTIME, 30FREEINT which define only the delta rates and use VCOM version 2 as the basic rateplan.
The end-user is registered with these delta plans and not the VCOM rateplan.
There is the requirement to change some rates to the common destinations like PR1, PR3 rates for which are defined in VCOM. To achieve this, the user created a new version of VCOM as version 3 with a specific “Valid From” date.
The user defines only the changed rates e.g., for PR1, PR3 etc in this version and use VCOM version 2 as the base rateplan for VCOM version 3. This is done so that it does not have to redefine all the rates that were already defined in VCOM version 2.
The user wants these changes done in VCOM version 3 to be available on all the delta plans so that the end-user on these delta plans are affected by these changes. To achieve this, the user is planing to change the basic rateplan defined for these delta plans to be VCOM version 3. But looks like it has to be re-defined the rates in delta rateplans again.
Otherwise, the CDR get rejected or it uses the rate defined in VCOM v3 instead of the rate that we want to be used for delta.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms