Step Tier Algorithm C1_RATE_STEP Does Not Consider Pricing Parameters While Stacking Quantities
(Doc ID 2809762.1)
Last updated on JANUARY 10, 2023
Applies to:Oracle Financial Services Revenue Management and Billing - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version
Step tier algorithm C1_RATE_STEP does not consider pricing parameters while stacking quantities.
Client has pricing scenarios (on price points defined on a price list), where a price item with different combinations of pricing parameters can be used to calculate different types of fees.
As an example, Price Item - ABC can have parameter 1 with pricing calculated as P*Q with Qty = SQI Volume. Similarly the same Price Item ABC can have parameter 2 with pricing calculated as STEP TIER Stacking with QTY = Market Value.
ORMB creates two different billable charges for each price assignment. Both charges will have Volume and Value amounts on it as SQI values. However for stacking it must use only the SQI for those charges that are associated to the price assignment with STEP TIER stacking.
In the current state, it pulls in additional quantities from the segments created using charges that are not associated to the same price assignment.
We are looking to see what if any is the solution to this scenario.
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