-
Type:
Bug
-
Status: Production Complete
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Bug Type:Functional
-
Bug Severity:Critical
-
Module:BenAdmin - Enrollment
-
Reported by:Client
-
Company:Mesto
-
Item State:Production Complete - Closed
The METSO Liberty Mutual file exported on 7/19 contained 2 employee records with blank status code for Product 2 column (column no. 121). Both these employees are terminated 3-4 months back then why there records appeared on 7/19 file?
The product 2 status code is populated with conditional rule and Product Code and Effective dates columns are direct fields mapping. The columns where rule engine is used blank value appeared on file.
We need to check this ASAP.
Hi Amit,
Please find below details for this issue.
Concern:
Employees whose elections were terminated previously, these records re-appeared on 7/19 file.
Cause:
This issue occurred due to one Enhancement got deployed on Production 'WT-8417: Moving dead enrollment (enrollment which were terminated as never effective in Intermediate table) through effective date service'. It was deployed on production on 07/19. In this process we have removed all dead elections prior to 01/01/2016, however dead enrollments after this date got moved through Effective date service.
During this execution, plans for which dead enrollment were moving and in case employee had enrollment into that specific plan in main table - latest Enrollment IDs of main table got assigned in Employee_Enrollment_Coverage table for dead moved enrollments. This caused issue in re-appearing those records on file.
Correction:
We have scanned all affected companies today and corrected this for Employee_Enrollment_Coverage table. Along with this we have also scanned RateChanges_Log & Invoice tables,. There are no impact found in these routines however in Policy number table there is some correction required, which we are doing it now.
We will keep on monitoring this for next 1 week and correct records if any found.
This enhancement patch has been reverted from production today and we will deploy that after verifying all impacted scenario.
Note:- We had stopped Export scheduler today (07/27) to do this correction, so today's morning scheduled feeds got delayed by couple of hours.
Regards,
Satya Prakash
Cc: Samir Jyoti Mayne Vinayak Kulkarni Vijay Siddha Amruta Lohiya Nandkumar Prabhakar Karlekar Rachel Baker Damion M Velasquez Abhay PatilRakesh Roy
Hello Satya,
We were also made aware for the JE Dunn_Medtrack File on 7/21/2017; carrier received several duplicate records in the weekly file. I ran a new file today and do not see any additional duplicated records. Do we know all clients that were impacted by this change?Enhancement got deployed on Production 'WT-8417
Thank you
Enhancement WT-8417 got deployed on production on 07/17 and all records have been corrected yesterday 07/28. Some of the other customers on which we observed same issue is - Groendyke, TIBCO, LHP, Metso & JEDunn. Correction have been completed across all companies, however we are verifying whether duplicated records have been rolled out on file.
This patch had been reverted from production, so going forward, any inconsistent data will not be observed due to this issue. We will update you on final list.
Regards,
Satya Prakash
Cc: Abhay Patil Tracy Kot Samir Vijay Siddha Vinayak Kulkarni Jyoti Mayne
Hi Amit,
We are working on this and update you on this by tomorrow.
As of now, we found two coverage entries for single member for an affected employee and only one coverage was considered for export earlier.
But when we saved template information on 07/19 before exporting file ( to omit rehires ), new coverage also added for export.
We suspect that this is corrupted coverage data but we need to talk to enrollment team before conclusion. We would have all details by tomorrow EOD. thanks.
Jyoti Mayne We need to discuss this tomorrow. Thanks.