Fusion Benefits:Participant Coverage Start Date Is Coming Incorrect as Processing date when Dependent Designation Requirement is Used with Suspend Enrollments
(Doc ID 2404009.1)
Last updated on MAY 28, 2018
Applies to:Oracle Fusion Benefits Cloud Service - Version 11.13.18.02.0 and later
Information in this document applies to any platform.
Participants Coverage start date is coming incorrect for Vision and Dental plans , after the Death of dependent Life event is processed
This Life event was added at Plan type in Program level with the following setup:
Life event tab:
Coverage start date as : First of month on or after event
Rate start date : First of month on or after event
Coverage end date : 1 day prior or month end
Rate end date : 1 day prior or month end
Program Designation Requirement tab :
For medical Plan type,Dental Plan Type,Vision Plan type> Life event > Coverage start date rule is first of next month
Dependent designation requirement setup has Suspend enrollments checked for all 3 plan types.
For medical Plan type,Dental Plan Type,Vision Plan type> Life event > Coverage start date rule should be first of next month, as per designation requirements
The issue can be reproduced at will with the following steps:
1. Employee1 has Life event Death of Dependent added on : 10-October-2018
2. Process the life event on 10th October 2018
3. Enroll into one medical plan,Dental Plan,Vision Plan
4. The coverage start date should
be : 1 Nov 2018
Rate start date :
5. For Dental and Vision plans: The coverage start date is currently showing as 10-oct-2018(showing wrong it should be 1-Nov-2018)
Previous coverage start date is: 1-Nov-2018
Rate start date:
For medical it is coming correctly but for Vision and Dental it is wrong.
The issue has the following business impact:
Due to this issue, users see a wrong coverage start date for these plans.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!