Able To Save MPP Pricing Rule Without Specifying MAP Value When No MAP Is Specified On PG Level
(Doc ID 3049356.1)
Last updated on OCTOBER 02, 2024
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 5.1.0.0.0 to 5.1.0.0.0 [Release 5.0]Information in this document applies to any platform.
Symptoms
On RMB v5.1.0.0.0, Able to save multi-period pricing (MPP) rule without specifying MAP value when no MAP is specified on Pricing Group (PG) level.
User can save MPP pricing without MAP value (i.e., Able to remove and save MPP with default value 0.00) when* NO MAP* type is selected at Parent MPP pricing rule. No warning message displays. When group is setup in such a way, there are no entries getting created for the group.
Product team provided <Patch 36857097> to correct this behavior.
This patch was applied and now an error is thrown when adding a new record without MAP Value on Add Pricing Rule Window.
As expected, it does not allow saving such records. But for existing records (with Edit Pricing Rule window), it does not have any such validation and allows to save the edited pricing rule by removing MAP value on MIN PREM Pricing Rule. This should be restricted as well.
ACTUAL BEHAVIOR
----------------
Able to save MPP Rule without specifying MAP value Minimum Premium Attachment Point Value.
EXPECTED BEHAVIOR
------------------
The MPP Rule should give warning message while saving the Rule with blank MAP value.
STEPS
--------
1. Set up ASO data.
2. Add MPP pricing rule on parent.
3. Edit MPP pricing rule on parent customer.
4. Save MPP pricing rule with blank Minimum Premium Attachment Point Value for existing records.
Cause
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
Symptoms |
Cause |
Solution |
References |