LoadIfwConfig Generated Xml With Incorrect IFW_RATEPLAN_VER Order
Last updated on SEPTEMBER 02, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
The Billing and Revenue Manger (BRM) Pipeline application allows Rate Plans to be hierarchically defined : one Rate Plan, the "delta" Rate Plan, inherits attributes from another Rate Plan, the "basic" Rate Plan and only defines those attributes different from it.
BRM Documentation - Setting Up Pricing and Rating - Pricing Center Help - Pipeline rate plans - Working with pipeline rate plans
The "LoadIfwConfig" is a utility that extracts from or imports data into the BRM Pipeline Manager database. Among other configuration information, the Rate Plan configuration information can be transferred.
BRM Documentation - Reference - Utilities and scripts - Pipeline Manager scripts and utilities - LoadIfwConfig
BRM Documentation - Setting Up Pricing and Rating - Transferring data between Pipeline Manager databases
Given the following Pipeline Rate Plan structure:
RatePlan_1 is a basic Rate Plan
RatePlan_2 is a delta Rate Plan inheriting from a basic Rate Plan RatePlan_1
RatePlan_3 is a delta Rate Plan inheriting from a delta Rate Plan RatePlan_2
This problem happens when the LoadIfwConfig tool is used to import an xml file which defines the Rate Plans in a different order than the the order that respects the Rate Plan basic-delta hierarchy.
According to the "RatePlan_1, RatePlan_2, RatePlan_3" structure above, the following xml Rate Plan definitions is naturally expected :
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