My Oracle Support Banner

Pin_rerate Does Not Give Expected Result In Case Of Quarterly Cycle Forward (Doc ID 2615774.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On Billing and Revenue Management (BRM) version, it was observed that pin_rerate does not give expected result in the scenario below where quarterly cycle forward is used in a back dated purchase scenario.


Note: There were also inconsistencies observed while rerating in other scenarios involving product cancellation followed by back dated repurchase and rerating, clubbed with the fact that multiple cycle events are configured in same product. These were however addressed by following general recommendations while rerating in such scenarios. One recommendation is not to configure two cycle events of the same frequency in the same charge offer in Pricing Design Center (PDC). Though PDC does not restrict us from having such configuration, it is not a valid business case to have two cycles of the same frequency (example, Monthly Cycle forward and Monthly Cycle Arrear). It is ok to have cycle fees of different frequency (example, Monthly Cycle Forward, Quarterly Cycle Forward, Annual Cycle Forward). In addition to this, it is recommended to perform rerating with start date as the product purchase date (that is, from the date when the new charges will be effective).




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.