-
Type:
Support Activity
-
Status: Closed
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Support Task Type:Configuration
-
Environment:Production
-
Reported by:EDI
-
Company:CHMC
-
Module:BenAdmin - Enrollment
-
Issue Importance:Must Have
-
Severity:Simple
-
Provider & Benefits:Sun Life Financial-LTD, Sun Life Financial-Optional Life - Child, Sun Life Financial-Optional Life - Employee, Sun Life Financial-Optional Life - Spouse, (3)
Sun Life Financial-STD, Sun Life Financial-Voluntary LTD, Sun Life Financial-Voluntary STD -
Reported by Customer:Kelly Kyle at CHMC
client: Prime Healthcare
*facility: CHMC
import template: Salary_Change_Ongoing
import date: 10/17/17
example affected: Helen Manzano and Janis Ozaki
Hi Development Team,
We did a salary update/load back in 10/17/17 around open enrollment and after the salary loaded into WT, some employees supplemental life coverages were terminated afterwards. The employees listed above were reported with the terminated coverages. There may be more out there with the same issue. So far this is the only facility from Prime Healthcare with the issue. You can find the original salary file used during the load from following location:
Y:\1.CLIENT\Prime Healthcare\0. OPEN ENROLLMENT\OE 2018\14. SALARY UPDATES\CHMC.txt
The employees coverages were supposed to roll over to 2018. Normally a salary increase or update should have increased the amounts instead of terminating the coverages. The CE already checked the plan/rule settings and couldn't find anything that is triggering the termination. Can you check in the back end to see if there's something causing the issue? I have attached screenshots of the payroll and enrollment history for review.
Client needs resolution soon if possible before the next payroll file. Let me know if you need additional info from me.
Thank you,
Alex
Hi Alex Nguyen,
Answering to your question "how can we avoid this from happening again in the future?"
This is called as "Back-end Routine failure" after Import. We monitor this under
WT-13017on daily basis. Additionally, we get an email whenever back-end routine fails. So we do the corrections if required and re-execute the routines.