-
Type:
Bug
-
Status: Production Complete
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Module:BenAdmin - Import
-
Reported by:Support
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
When we import election data if there is a bad file with spouse/children on bad (employee record is imported) and then we correct that bad file and re-import the data that time the original election record is getting overwritten and new record with only spouse or children (or both) come into effect. This is a big data discrepancy and it take lot of time for correction.
we have to provide workaround for this issue otherwise data load will because a time consuming job in case of large number of bad records.
I already discussed this Jaideep couple of times but as per him there is no resolution to this issue as of now.
CC - Samir, David Rhodes
[~meghana.kulkarni] Are the scenario mentioned in the description tested?
Verified below Scenarios for other benefit types on LB:
1) Verified election for Employee life plan with retro date , Current Date and Future Date
2) Verified election for Spouse life plan with retro date , Current Date and Future Date directly through import and bad files.
3) Verified election for Child life plan with retro date , Current Date and Future Date directly through import and bad files.
4) Verified election for LTD Benefit Type
5) Verified election for HSA Plan dependent upon any other plan for retro date , Current Date and Future Date by changing tier
6) Verified election for HSA Plan
7) Verified election for service based plan
8) Verified multiple plan enrollment within same template
Working Fine.
CC - Sachin Hingole
Yes, Above mentioned scenarios are tested on Production.