Changing customization of benefit type order to ALL will pull out value, let us know if it doesn't, Thanks.

It works now, thank you.

Hi Cindy Wibbing and Vinayak Kulkarni,

I am reopening this ticket as a bug, because there needs to be a global update to accommodate column-wise feeds.

While the Benefit Option was updated from EE Critical Illness to All on these templates, the Transaction Type is not populating a Change transaction for the 3 combined benefits when a dependent critical illness plan gets added.

cc - Yamilka Coca, Amit Thorve, Abhay Patil

Hi Amit Thorve

Yes, we will discuss this in detail tomorrow. Is 2pm IST okay with you?

Let me know if you'd like me to open up a bug ticket for this instead.

This is converted to Bug as per discussion with Vinayak K and Analysis is planned in Sprint 43.
____________________________________
Vinayak Kulkarni Satya

Hi All,

Below are initial details,

We have a payroll export template named Payroll_Critical Illness to report critical Illness deduction.

In WT, we have three CI plans
1] Employee Critical Illness
2] Spouse Critical Illness
3] Child Critical Illness

However, we report deduction from all these three plans in one row with code "VOLCRI"

For example, consider $10 cost for each plan.

If employee is enrolled into all three then we send employee with $30 for VOLCRI deduction.
and if employee is enrolled into employee and spouse critical Illness then we send $20 for VOLCRI deduction.

In short, For payroll vendor, it single benefit but in WT its divided into 3 three benefits.

Now, problem occurring with Transaction type field on payroll file. client needs transaction type as New, Change and Term.

So in WT, if someone enrolls in Employee critical Illness then we send transaction type as New with $10 cost, which is fine.

However, if same employee adds spouse critical Illness later on in WT,
then we send it as new transaction with $20 cost, as spouse critical illness is new in system.
This is a problem, because for client its a change from $10 to $20 in same benefit.

We are finalizing all the scenarios which are working fine and which are not working fine.
Once we are done this we can proceed finalizing approach.

Hi Amit Thorve

We are ready with our analysis.
We will discuss this tomorrow , 11am IST, will send calendar invite. Thanks.

Attaching Enrollment Change Type For Multiple Benefit(s).doc analysis document.

Add WBS WT-13087_WBS.xls document. Thanks.

Hi All,

Reason for having multiple benefit in WT is that spouse CI should have max coverage capped at 50% of employee's coverage, and child CI has offered amounts.

Please find 3C's as below.
Concern: Transaction type is not reflecting properly on critical illness records

Cause: For exports, We report deductions from all three type of Critical Illness plans in one row. Payroll vendors have it as 1 benefit, While in WT we have it has 3 benefits. This inconsistency is causing issues when we send transaction types on payroll files.

Correction: We are introducing new field i.e Enrollment TransactionType type for all selected benefits Which will look across multiple benefits and send correct transaction type.

CC-Ganesh Sadawarte, Vinayak Kulkarni

Attaching the list of template having same customization.TemplateListWithSameCustomization.xls

Attaching Test Cases TestCases_WT-13082.xls

CC-Hrishikesh DeshpandeRakesh Roy

Verified following scenarios on Columnswise(Changes Only File) template :-

1.Selected Benefits enrollments are Terminated
2.Benefits enrollments are Added by raising qualifying event
3.Benefits enrollments are Added by New Hire mode
4.Only one enrollment is terminated after last exported Date
5.Enrollments are terminated by Terminate as never effective(Dead Enrollment)
6.Spouse or Child benefits enrollments are added after last exported date.

Observation - For Full file All records will be termed as CHANGE

Testing is in process for other scenarios .

CC-Hrishikesh DeshpandeVinayak KulkarniRakesh Roy

Verified all scenarios mentioned in TestCases_WT-13082.xls , It is working as expected.
Ready for stage deployment.

CC-Hrishikesh DeshpandeRakesh RoyVinayak Kulkarni

Verified all following scenarios on Stage
1.Selected Benefits enrollments are Terminated - Pass
2.Benefits enrollments are Added by raising qualifying event - Pass
3.Benefits enrollments are Added by New Hire mode - Pass
4.Only one enrollment is terminated after last exported Date - Pass
5.Enrollments are terminated by Terminate as never effective(Dead Enrollment) - Pass
6.Spouse or Child benefits enrollments are added after last exported date. - Pass
7.Employee,Spouse,Child termination. - Pass
8.Spouse and child terminated by terminate dependent benefits - Pass
9.New Benefits Enrollment added in OE - Pass

It is working as expected.Ready for production deployment.

CC-Hrishikesh DeshpandeRakesh RoyVinayak Kulkarni

Hi Van Nguyen,

This is deployed and verified on production with all scenarios.
It is wokring as expected,please verify at your end and confirm it.
and let me know,if there is any query.

Thanks,
Swapnil Eksambekar

CC-Hrishikesh DeshpandeRakesh Roy

Hi Van,

We have introduced new mapping field "Enrollment transaction type for multiple Benefit" to get correction transaction type on column-wise file in case we are sending multiple WT benefits into one row in file.

Please go through analysis doc Enrollment Change Type For Multiple Benefit(s).doc
You can map this new field on file and test it, if it goes fine then we have to replace existing mapping with new mapping on production for attached template list. TemplateListWithSameCustomization.xls

Let us know if you have any questions on this. Thanks.