AddRoles Built-in Validation Fails in Scenarios where Validation Should be Successful
(Doc ID 2465921.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.29 and later
Information in this document applies to any platform.
On : 10.2.0.29 version, Policy information
The AddRoles APE has a built-in validation to ensure the total percentage of the existing and newly added roles should match the required percent total.
With the existing logic, the total is calculated as the role percents values from database plus the new Roles being added. This usually will result in a total which will fail the validation.
Scenario 1: Replace existing client with another: Client A for role R already exists at 100%. Now you add client B at 100% while removing A – we will end up with a 100 + 100 = 200% which will be greater than the required percent total of 100.
Scenario 2: Adding a client while updating percent on existing: Client A for role R exists at 100%. Add client B at 60% while reducing A to 40% - this will lead to 100 + 60 = 160%, again failing validation.
In both Scenarios above the system should always get the latest from memory – which would be updated by the CopyToRoleFields APE.
The issue has the following business impact:
Certain business scenarios such as those described above will result in key activities failing..
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