-
Type:
Bug
-
Status: Closed
-
Priority:
Medium
-
Resolution: Bug Fixed
-
Labels:
-
Environment:Production, Stage, QA
-
Categories:Export
-
Company:All Clients/Multiple Clients
-
Reported by:Harbinger
-
Level:Partner
-
Browser:Google Chrome
Hi Vinayak Kulkarni,
Found a scenario where future effective and future dead election is exporting wrong election on file
1) Employee Enrolled in Med 1 from 1/1/2016
2) Changes to Med 2 on 10/1/2017
3) New election of Med 2 exported on file with eff date 10/1/2017
4) Med 2 becomes dead termed as never effective and file is exported
Result : Med 1 plan with effective date as 1/1/2016 and Termination date as 09/30/2017 exported on file
Can you please check and update accordingly ?
Hi Amit,
Can you guide us here, I believe this is not an issue as we never face such issue into production, However wanted you confirmation?
Vinayak Kulkarni Is Med 2 is exported on file with 10/1/2017 date and then if it becomes dead then on next file the dead enrollment should roll out.
We can discuss it with Aniruddha Dev today.
Files affected: dbo.OES_UDF_Export_GetExportedDeadEnrollmentIDs.UserDefinedFunction
Satya Vinayak Kulkarni I am not sure if I am understanding what is going on here..and what do we mean by the term "dead"? Does this mean inactive?
Jennifer Reed (Inactive)
added a comment - Satya Vinayak Kulkarni I am not sure if I am understanding what is going on here..and what do we mean by the term "dead"? Does this mean inactive? Hi Jennifer,
"dead" means "terminated as never effective".
When a enrollment gets added in system, we report it on export file. However later on due to any data change event if that enrollment is terminated as never effective then we again report this termed as never effective on export file.
We have to report this termed as never effective to stop payroll deduction if we sent active deduction earlier.
This ticket is for one specific scenario where "termed as never effective" enrollment is not getting reported on export file. That scenario is mentioned on description of ticket. Let us know if you have any questions on this, Thanks.
Verified all scenarios ,It is working as expected.
Ready for pre-production deployment.
Verified this on pre-production ,It is working as expected.
Ready for prodution deployment.
Verified this on production,It is working as expected.
Hence closing this ticket.
Hi Amit Thorve
Can you please go through this scenario and let us know whether it needs to be handled?
This is for column-wise file. Let us know if we need to discuss this. Thanks.