Two Dimensional Pricing Should Have Configurable Validation For RC-Rate Definition
(Doc ID 2523879.1)
Last updated on SEPTEMBER 25, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, ENV - Environment
18.104.22.168 : Two dimensional pricing should have configurable validation for RC-Rate definition.
As per current design, in two dimensional price assignment it is mandatory to have RATE DEFINITION -Tiering Type of all RCs of selected Rate schedule = STEP.
This validation is hard coded validation (BS: PriceAssignmentService, method: validateRsForGrid).
If any of the RC has rate definition other than STEP then there will be an error thrown during price assignment : The tiering type of all rate components in the NEWTEST rate schedule is not set to STEP.
Issue (Problem Statement) :
This hard coded validation is blocking a requirement as it will be required to maintain Discount% as FLAT / Threshold Based during Price assignment, which is currently not possible due to the above mentioned validation.
Instead of putting this as hard coded validation, we will need it as Configurable Validation which will give more flexibility in using Two Dimensional pricing and to meet actual business requirements.
Can an Enhancement be opened to have Configurable Validation?
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