Benefits Administration Terminates Unrelated Plans When Events Are Force Finalized With Cross Plan Errors
(Doc ID 1957318.1)
Last updated on AUGUST 28, 2023
Applies to:
PeopleSoft Enterprise HCM Benefits Administration - Version 9 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
When Simple and HSA Benefit Plans are in error as requiring an election in medical (10) via Cross Plan Validation and Force Finalize is used, the employees' elections are terminated rather than maintaining current elections.
This includes unrelated plans where elections were not prepared with the event. The Event rules configuration includes Pre-enter and Select Allowed is None.
The scenario is the following:
1. A benefits event that allows the employee to make changes only in Optional Life and Spouse Life is created.
2. The employee is enrolled on Simple Benefit plans (A2, A3, and A5) as well as HSA (67). The plans are flagged as requiring an election in medical (10) via Cross Plan Validation.
3. None of these plans (A2, A3, A5 and 67) are included in our Life Insurance event.
4. When the Life Insurance event was force finalized, termination rows were written to plans A2, A3, A5 and 67.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |