Please see attached document.

This client is in Production and has just completed an Open Enrollment

Hi Yashau MacShate,
We are working on this and during our initial analysis we found that Child Voluntary Life rate has been allocated to the mentioned employee and again somehow the rate got dead for the mentioned employee.

We are working on this and will update you ASAP.

CC-Umesh Kadam, Suraj Sokasane, Amruta Lohiya, Satya

Hi Yashau MacShate,

Please find below details of data correction:

Below EE's have proper rate so there is no need of correction:

We have done correction for below EEs:

We scanned all EEs and found below EE's whose correction is also done, those are :

Hi Prasanna Karlekar, we have done rates correction.Please confirm it on report.

Thanks,
Shailendra Honrao

Cc: Prasanna Karlekar,Jyoti Mayne, Amruta Lohiya

Hi Rashmita Dudhe,

Problem Statement: Child Voluntary Life rate has been allocated to the mentioned employee and somehow the rate got dead.

Analysis:

• 2 rates 'Child Voluntary ADD' & 'Child Voluntary Life' are mapped with 'Child Voluntary Life Plan'. Both having effective start date as 2016-11-01 and effective end date as 2018-10-31.
  *We observed data for EE JACKSON NIKKAA, initially rate entries are like this:

  Sr.No.	Effective Date	Termination Date	Rate Name
  1	2016-11-01	2017-10-31	Child Voluntary ADD
  2	2016-11-01	2017-10-31	Child Voluntary Life

• We have observed on view history page only employee data change was happened with effective date 11/01/2017.
• Child Voluntary ADD rate inserted properly with 11/01/2017 to 10/31/2018.
• But Child Voluntary Life rate inserted with 11/01/2017 to 10/31/2017 (Dead entry).

  Sr.No.	Effective Date	Termination Date	Rate Name
  1	2017-11-01	2018-10-31	Child Voluntary ADD
  2	2017-11-01	2017-10-31	Child Voluntary Life

• Enrollment is added through OE mode with effective date 11/01/2017.
• We have observed rates eligibility, and Child Voluntary Life rate is having All status rule and it never changed.

We are tried following steps to reproduce an issue,

• Start OE on company
• Login with EE and did employee data change with effective date 11/01/2017 through employee workflow.
• But when we have observed from back end, Child Voluntary Life rate has inserted properly with 11/01/2017 to 10/31/2018.

Can you please help us to reproduce this?

Thanks,
Shailendra Honrao

Hi Yashau MacShate,

Following is the update for incorrect cost appearing on Enrollment Report:
Employee Name : JACKSON NIKKAA
Plan Name : Child Voluntary Life Plan
2 Rates are mapped to this plan : Child Voluntary Life and Child Voluntary ADD
As per data in the system:

Regarding Report -
Report was being pulled for span 11/1/2017 - 11/30/2017.
During this span, from above table, rates effective with 11/1/2017 were being referred. Out of the 2 rates effective from 11/01/2017, rate with cost $0.2 is active. One with $1.8 is termed as never effective. Hence, while processing the report, only $0.2 cost was getting considered. As per semimonthly payroll schedule, $0.1 was appearing on the report. Cost appearing on report was as per the cost stored in system for given date span.
We tried extracting the enrollment report with date span 10/01/2017 to 10/31/2017 for which proper cost $1 appeared. For this span, rates effective with 11/01/2016 were considered and both are active.

Regarding cost on screen -
Cost on Enrollment Summary or Confirmation statement appeared as per data based on today's date.
We did check the enrollment summary of this employee where cost appearing was $1. If we check above table, then as per today's date 10/24/2017, rates effective with 11/1/2016 are considered. Both rates effective with 11/01/2016 are active rates. Hence for enrollment summary proper cost appeared.
If we raise a QE effective from 11/1/2017, we may have got the discrepancy on Enrollment Summary too.

Now as enrollment team has done the data correction proper cost should appear on enrollment report for span 11/01/2017 - 11/30/2017.

Thank you!

cc: Gaurav Sodani

Gaurav Sodani -

As enrollment team has done the data correction, QA verification will be required for reports.
Please schedule the same.

Thank you!

Do we need to do anything on our end? Please advise.

Yashau

[~meghana joshi]

Please check reports.

Hi Rashmita Dudhe

I have verified these below mentioned Reports

1) Child Voluntary Life
2) Employee Voluntary Life
3) Spouse Voluntary

For Child Voluntary Life , I have verified cost with Employee Erin Meyer
Child Voluntary Life.xls

Employee Cost ( Calculated =1 and Appearing= 1 )

For Employee Voluntary Life , I have verifed cost with Employee Fawn Beck
Employee Voluntary Life.xls

Employee Cost (Calculated =47.875 ,Appearing = 50.38)

And For Spouse Voluntary Life , I have verified cost with Shelia Hardy
Spouse Voluntary Life.xls

Employee Cost (Calculated =4.15 ,Appearing = 4.65)

cc: Sachin Hingole Rakesh Roy Prasad Pise Hrishikesh Deshpande

Thank you !

Hi Prasanna Karlekar

Please refer reports as disscused

Child Voluntary Lifeone.xls
Employee Voluntary Lifeone.xls
Spouse Voluntary Lifeone.xls

cc: Sachin Hingole Prasad Pise Rakesh Roy Hrishikesh Deshpande

Thank You !

Hi Shailendra Honrao,

CC:Jyoti Mayne, Hrishikesh Deshpande,Rakesh Roy,Prasanna Karlekar, Amruta Lohiya, Satya

This issue is getting reproduced follow Below Steps:

Child Voluntary Life Rate: All status rule.

1]Added New employee with class Nonunion 1 and effective date 11/1/2016
2]Enrolled into the Employee Voluntary Life Plan as child life plan is contingent on this plan Effective date 11/1/2016
3]Added child to employee 11/1/2016
4]Enrolled into the Child Voluntary Life with Effective date 11/01/2016
5]Start OE which is effective from 11/1/2017

6]Change employee status incomplete to compete with effective date 10/25/2017
7]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017
It showing dead entry refer below screenshots

1]Before dead entry

2]After dead entry

3]changes done on employee view history:

Thanks,
Rashmita

Hi Yashau MacShate,

We have provided the updates. Also data has been corrected by enrollment team for impacted employees.
No action is required from your side.

Thank you!

cc: Jyoti Mayne, Gaurav Sodani

Priya Handepatil,

You have mentioned discrepancy in calculated and cost appearing on reports for Employee and Spouse voluntary life plans. Verified the cost for mentioned employees "Fawn Beck" and "Shelia Hardy" from back end. Cost for these employees appearing on report is as per data stored in the system.
Could you please confirm the calculated cost as there is lot of difference?

Thank you!

cc: Rashmita Dudhe, [~meghana joshi], Jyoti Agrawal

Hi Amruta Lohiya,

Please find below details-

Concern: Child Voluntary Life rate has been allocated to the mentioned employee and somehow the rate got dead.

Cause: Initially 'Child Voluntary Life' and 'Child Voluntary ADD' rates having

Then rates end date was changed to 10/31/2018

When rates are extend & recalculated through SA Utility, rates are not extended properly.

We have scanned data then rates are extended properly for some EE they got rate as:

But some rates are not extended properly for some EE they got rate as:

So, when enrollment done through OE mode, that time 'Child Voluntary Life' rate becomes dead.

When we debug the code for root cause then we come to know that there is a update query written due to which 'Child Voluntary Life' rate becomes dead.

Correction: We have done code fix for this.

Thanks,
Shailendra Honrao

Cc:Jyoti Mayne,Rashmita Dudhe,Satya,Hrishikesh Deshpande

Awesome!!

Hi Yashau MacShate,

I am working on code fix and will update you.

Thanks,
Shailendra Honrao

Cc:Amruta Lohiya,Jyoti Mayne

Verified in Lb environment consider scenarios

Rate Name --------- Effective Date ------- Termination Date
Child Voluntary Life --------- 11/01/2016 ------ 10/31/2018
Child Voluntary ADD ---------- 11/01/2016 ------- 10/31/2018

• 1. Scenario 1*
     1]Add new employee with effective date 11/1/2016
     2]Enrolled in the Child Voluntary Life with Effective date 11/01/2016
     3]Start OE which is effective from 11/1/2017
     4]Change employee status incomplete to compete with effective date 10/25/2017
     5]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017

The rate is not dead verified by the back-end and sa utility

• 1. Scenario 2*
     1] Change employee status through the import
     2]Change Employee class through the import

The rate is not dead verified by the back-end and sa utility

• 1. Scenario 3*
     Create New plan and Rate

Rate Name ---------- Effective Date ----- Termination Date
Child Voluntary Life ------ 01/01/2017 ------- 12/31/2018
Child Voluntary ADD ------ 01/01/2017 ------- 12/31/2018

1]Add a new employee to effective date 01/1/2017
2]Enrolled in the Child Voluntary Life with Effective date 01/1/2017
3]Start OE which is effective from 1/1/2018
4]Change employee status incomplete to compete with effective date 10/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017

The rate is not dead verified by the back-end and sa utility

• 1. Scenario 4*
     1]Add a new employee to effective date 01/1/2017
     2]Enrolled in the Child Voluntary Life with Effective date 01/1/2018
     3]Start OE which is effective from 1/1/2018
     4]Change employee status incomplete to compete with effective date 11/25/2017
     5]Change employee Class Non-union1 to Nonunion2 with effective date 11/25/2017

The rate is not dead verified by the back-end and sa utility

• 1. scenario 5
     *
     1] Change employee status through the import by future effective date 12/25/2017
     2]Change Employee class through the import by future effective date 12/25/2017

The rate is not dead verified by the back-end and sa utility

working fine as expected

Verified in Stage environment Consider below scenarios:

Rate Name --------- Effective Date ------- Termination Date
Child Voluntary Life --------- 11/01/2016 ------ 10/31/2018
Child Voluntary ADD ---------- 11/01/2016 ------- 10/31/2018
Scenario 1
1]Add new employee with effective date 11/1/2016
2]Enrolled in the Child Voluntary Life with Effective date 11/01/2016
3]Start OE which is effective from 11/1/2017
4]Change employee status incomplete to compete with effective date 10/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017
The rate is not dead verified by the back-end and Sa utility

Scenario 2
1] Change employee status through the import
2]Change Employee class through the import
The rate is not dead verified by the back-end and Sa utility

Scenario 3
Create New plan and Rate
Rate Name ---------- Effective Date ----- Termination Date
Child Voluntary Life ------ 01/01/2017 ------- 12/31/2018
Child Voluntary ADD ------ 01/01/2017 ------- 12/31/2018
1]Add a new employee to effective date 01/1/2017
2]Enrolled in the Child Voluntary Life with Effective date 01/1/2017
3]Start OE which is effective from 1/1/2018
4]Change employee status incomplete to compete with effective date 10/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017
The rate is not dead verified by the back-end and Sa utility

Scenario 4
1]Add a new employee to effective date 01/1/2017
2]Enrolled in the Child Voluntary Life with Effective date 01/1/2018
3]Start OE which is effective from 1/1/2018
4]Change employee status incomplete to compete with effective date 11/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 11/25/2017
The rate is not dead verified by the back-end and Sa utility

scenario 5
1] Change employee status through the import by future effective date 12/25/2017
2]Change Employee class through the import by future effective date 12/25/2017
The rate is not dead verified by the back-end and Sa utility
working fine as expected

CC:Rakesh Roy, Hrishikesh Deshpande

As discussed with Gaurav Sodani and Jaideep Vinchurkar moved this ticket from WT to NF project

As discussed in Stand-up meeting, covert back this ticket from NF to WT.

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Verified in Production environment Consider below scenarios:
Rate Name --------- Effective Date ------- Termination Date
Child Voluntary Life --------- 11/01/2016 ------ 10/31/2018
Child Voluntary ADD ---------- 11/01/2016 ------- 10/31/2018
Scenario 1
1]Add new employee with effective date 11/1/2016
2]Enrolled in the Child Voluntary Life with Effective date 11/01/2016
3]Start OE which is effective from 11/1/2017
4]Change employee status incomplete to compete with effective date 10/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017
The rate is not dead verified by the back-end and Sa utility
Scenario 2
1] Change employee status through the import
2]Change Employee class through the import
The rate is not dead verified by the back-end and Sa utility
Scenario 3
Create New plan and Rate
Rate Name ---------- Effective Date ----- Termination Date
Child Voluntary Life ------ 01/01/2017 ------- 12/31/2018
Child Voluntary ADD ------ 01/01/2017 ------- 12/31/2018
1]Add a new employee to effective date 01/1/2017
2]Enrolled in the Child Voluntary Life with Effective date 01/1/2017
3]Start OE which is effective from 1/1/2018
4]Change employee status incomplete to compete with effective date 10/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 10/25/2017
The rate is not dead verified by the back-end and Sa utility
Scenario 4
1]Add a new employee to effective date 01/1/2017
2]Enrolled in the Child Voluntary Life with Effective date 01/1/2018
3]Start OE which is effective from 1/1/2018
4]Change employee status incomplete to compete with effective date 11/25/2017
5]Change employee Class Non-union1 to Nonunion2 with effective date 11/25/2017
The rate is not dead verified by the back-end and Sa utility
scenario 5
1] Change employee status through the import by future effective date 12/25/2017
2]Change Employee class through the import by future effective date 12/25/2017
The rate is not dead verified by the back-end and Sa utility
working fine as expected

This is deployed and verified on Production.
Kindly, Update jira accordingly.