Maintain Relationship Business Rule Not Working Correctly if Processed Twice on the Same Day
(Doc ID 2452699.1)
Last updated on OCTOBER 01, 2018
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.26 and later
Information in this document applies to any platform.
Maintain relationship attached business rule is not acting as expected when a transaction that uses that rule is processed twice on the same day.
A relationship was originally set up manually with an effective date of 1/1/2010.
On 5/5/2011 a transaction was processed to update some fields within that relationship.
When that transaction was processed it expired the first timeslice effective from 1/1/201 on 5/4/2011 and created new slice effective from 5/5/2011 as expected.
User then processed second transaction on 5/5/2011 to update additional fields on the relationship.
It did expire the first slice created on 5/5 and create a second slice with effective date of 5/5.
On the UI display the slice created and expired on 5/5 was on top of the active timeslice with only effective date of 5/5.
This is different then if you had just processed these timeslices directly on screen.
In that case it shadows the first instance of the timeslice on 5/5/2011 and creates a new active timeslice with the updates from both manually created ones on 5/5/2011 so that there is only 1 active record with an effective date of 5/5/2011.
To take the scenario a step further, processing an additional transaction on 10/31/2011 it updated the expiration of the top record that already had an expiration date vs updating the current timeslice and created a new timeslice as of 10/31.
As a result there are now two timeslices without expiration and above it appears as if there are two relationships, but both represent all the same slices from the same relationship.
The expected behavior is the Maintain Relationships rule should be able to handle multiple updates in a day (behave the same as the UI.)
Because of this issue, users are unable to accurately maintain several relationships through the use of activities.
The workaround is to manually process on screen, which is not feasible in all cases.
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