Issue with 'Enroll in Default Benefits' Process When Using Enrollment Coverage Start FF
Last updated on AUGUST 20, 2015
Applies to:Oracle Fusion Benefits Cloud Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Manage Benefits
Coverage start date for the program is based on fast formula which is as below:
• If effective date of enrollment is < 10 of the month, then enrollment coverage start is 1st of the same month
• If effective date of enrollment is >=10 of the month, then enrollment coverage start is 1st of the next month
While this formula is working fine at all times, it is not working well when ‘Enroll in Default benefits’ process is run.
This process increases the enrollment coverage start date by 1 extra month for all plans where defaults are applicable i.e. if the formula was supposed to return 1-May-2014 as enrollment coverage start date, this process makes it return 1-Jun-2014.
Enroll in Default benefits process should not increase the enrollment coverage start date by 1 extra month
The issue can be reproduced at will with the following steps:
Process ‘Evaluate Life Event participation’ with effective date to 11/4/2014
Apply Defaults’ was set to "YES
Log for ‘Evaluate Life Event Participation’ process shows the fast formula has returned 1/5/2014 (1-May-2014) as the coverage start date for all plans, correctly.
However, the coverage start date returned for the plans already enrolled in, for the ‘Enroll in Default Benefits’ process is returned as 1/6/2014 (1-Jun-2014) instead of 1/5/2014.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms