Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Losing Dependent Changes during Reprocess of Backout Life Event
Summary
Losing Dependent Changes during Reprocess of Backout Life EventContent
Reprocessing a Backed Out life event reinstates the Addition of Dependents but does not reinstate the Removal of Dependents. This occurs when a participant does not change the plan/option, but only changes who is covered. Oracle Support has confirmed this is per design.
Example:
On 6/5, Life Event 'Drop a Dependent' is processed and participant Removes child 1 from 'Medical Family' plan/option. The participant did not change plan/option because he has other dependent children which will not be dropped. Life Event 'Salary Adjustment' is detected on 7/1 with effective date of 6/1. This second life event backs out the first 'Drop a Dependent' life event. When 'Drop a Dependent' is reprocessed, child 1 is added back.
Tagged:
0