-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: System Behaviour
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Import
-
Reported by:White Label
-
Company:CSE
We have a couple issues with the data load for CSE. Please correct asap
1. The contingent EE AD&D and the Contingent Spouse AD&D are supposed to exactly match the EE and Sp life plans. When the data was loaded it the system enrolled the employee and spouse AD&D at the minimum coverage instead of matching the coverage amount of the life
2. The basic Life, AD&D and LTD for employees hired before 1/1/2017 should have an effective date of 1/1/2017. When the data was loaded the system gave those benefits a 2/1/2017 effective date.
Hi Debbie Kulling,
Please find below details for #1 :
| Concern | When the data was loaded in, the system enrolled the employees in "Employee Voluntary AD&D" and "Spouse Voluntary AD&D" plans with the minimum coverage instead of matching the coverage amount with respective Voluntary Life Plan |
| Cause | Through import, the functionality of matching the Coverage Contingency is not implemented yet. |
| Correction | We have done data correction as of now. Development team will work to implement matching of Coverage Contingency in Import Module |
Thanks and Regards,
:: Umesh Kadam
CC : Samir, Satya, Amruta Lohiya, Swapnil Pandhare, Ganesh Sadawarte, Jaideep Vinchurkar
Hi Debbie Kulling,
Please find below details for #2 :
| Concern | When the data was loaded, the system allocated enrollments in Basic Life, LTD and AD & D plans with effective date 02/01/2017 instead of 01/01/2017 |
| Cause | While allocating Core Plan during import, System uses "Effective Date Rule for Newly Eligible Core Elections" flag set on "General Plan Design" tab of a plan. Currently this flag has been set as "First of Month following 30 days" due to which system allocated core plans with effective date 02/01/2017. Please find below screenshot for the same  |
| Correction | We have allocated core plans with effective date 01/01/2017 through back-end. |
Thanks and Regards,
:: Umesh Kadam
CC : Samir, Satya, Amruta Lohiya, Swapnil Pandhare, Ganesh Sadawarte, Jaideep Vinchurkar
Hi All,
In files that we have loaded employee effective date was 01/01/2017. Company level effective date rule is set to first of next month. Hence all employees got coverage from 02/01/2017. Please refer effective date termination date rule from company info 
Data correction is already done. No action items are pending
Data correction is already done. We are rejecting this bug as this is system behavior. Employee got effective date as per rule set on effective date termination date screen. i.e. first of next month.
CC : Samir Jaideep Vinchurkar Satya
Hi Umesh Kadam ,
Please check this as discussed.
Thanks,
Swapnil P.