QE being tested in Stage. Once client signs off, we will request DEV move templates to PROD, and this will replace the pre-existing Banner Feeds that exports Daily @ 5pm

Great news Mary,

As soon as we have your approval I will need to have this Staging Export moved into our Production Environment, and this will replace the existing banner export that goes daily. This exercise may take 24/hrs to turn around.

Thanks again!

Damion Velasquez | EDI, WORKTERRA
Employee Benefit Specialists, Inc.
PO Box 11657, Pleasanton, CA 94588
PH: 925-469-5223 | FAX: 925-460-3920 | damion.velasquez@ebsbenefits.com

_______________________________________________________________________________________________________________________________________

Total Enrollment Services l Employer & Employee Member Portals l Flexible Spending Accounts l Commuter Benefits
Employer Flex Benefit Card l COBRA & Retiree Administration l Invoice Reconciliation l Voluntary Benefits

www.ebsbenefits.com www.workterra.com

DISCLAIMER
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately.

From: Mary Kocks mkocks@nd.edu
Sent: Tuesday, February 09, 2016 5:17 AM
To: Damion Velasquez
Cc: Ashley Marra; Phil Almeida; Cindy Wibbing; Jim Heide; Steven Cohen
Subject: Re: UND QE File name

So far the file looks good. We hope to do a deeper test by the end of the week. We'll let you know how that goes.
Amit ThorvePhil AlmeidaAshley Marra

Feedback From Client:

had a mapping for Term Date applied to Child College end date. This was left over from Stage, and I removed Damion M VelasquezAshley Marra

Damion M Velasquez Mary informed me yesterday that she will most likely be requesting a new QE file this Friday, 2/19, for a delivery date of Monday. I wanted to give you a heads up because I am not sure how long it takes you to run this template. Let me know if Monday would not work and I will tell the client. Thanks!

Damion M Velasquez Per UND's email from 2/18, can you please post another QE file? Thanks!

Ashley MarraPhil AlmeidaAmit Thorve
posted new file for Changes ONLY to UND for Stage Testing

Damion M Velasquez I have now updated all QEs except the admin QE to have the effective date rule be “first of the month following or coincident with event date”.

Damion, there are a couple of issues that will be resolved by me changing the rule on the QE to the above rule. There are a couple of other issues that we need to look at from a file perspective. We can talk about these but they are in reference to not getting a term record code back on the file for an employee who switches from employee only coverage to family coverage. Once Steve is finished entering scenarios into Stage for the new QE rules by end of day Thursday he will inform us and then if we can push out another file that would be great. Also, UND is expecting a full file and not a change file. Can we please send them a full file the next time around?

Ashley Marra Ok let me know and I can run the file. I look into the scenario above when I run it out

Damion M Velasquez I just talked to the client and they might want a QE file tonight. He will let us know but I wanted to give you a heads up. THanks!

Vinayak KulkarniAshley MarraPhil AlmeidaAmit Thorve
Hello Vinayak,

I am having an issue again with these templates. I also posted to JIRA. The client is expecting a Test File today, and they are on the east coast. Any chance this can be looked into

From_Prod_OE Illusions Banner Accident Employer Paid
From_Prod_OE Illusions Banner CI Employer
From_Prod_OE Illusions Banner HRA

Thank you

Damion M Velasquez

It was again problem with Qualifying events wrong data.
We have corrected it Stage now. Can you please check & let us know if this is working or not.

Issued Test File will wait for results to test this function

Sent test file will test what DEV fixed with the plans

Vinayak Kulkarni Hello,

First id like to thank you for your patience. This file has been a monster.

For all templates in Stage that begin with From_Prod_OE Illusions Banner: We have two new columns in this File layout. Qualifying Event fields aren't populating properly. I am going to send you an email with the PHI for an example.

Thank you

Vinayak KulkarniAshley MarraAmit Thorve

Hello Vinayak,

Can you provide a status? Apologies but the client in this case wants daily follow ups.

Thank you

Vinanti YadavAmit ThorveCindy WibbingAshley MarraSteve Allison

Hello Vinayak.

Can you provide a status for this? Please refer to the email I sent with the examples where this issue is happening. The client is following up on a daily basis.
Please advise

Thank you

Hey Damion,

Per our discussion today, we need confirm that whether first file needs QE code on all records or is it ok if few comes with blank QE codes.

Also, we need to transform every mode by which changes could happen in the system.

Thanks,
Vinayak

This issue for ND has been escalated to me. We have a call today with the client at 11:30am PST. I have asked Ashley and Cindy to get with Damion and Vinayak first thing this morning to prep for the call with the client and problem solve. Then Cindy will be on the call with the client at 11:30 to talk through the limitations and possible solutions.

Thanks everyone.

Steve

Hi Damion,

We just created company on production with name "UND For Banner Payroll Testing", please verify you have access to it.
Also we need to make sure all export templates are set-up properly with QE codes & dates.

Let us know if you face any issues with it.

Hi Damion,

See attached, Enrollments terminated due to employee data change Event and this is not transformed.

The changes you did through QE to employee/dependet data which changed enrollments will fall under Employee Data Change Event.

If you do enrollment changes directly with QE then that QE will come on file.

Hi Damion,

To get Qualifying event for enrollment changes instead of Employee Data Change, I have forwarded this to development team to analyze further.
It seems to be big & generic change in system. We would expect more updates by Monday.

Thanks,
Vinayak

Vinayak KulkarniPlease update if you have any. Also could you please let me know that person name who is working to follow-up?

Hi Rakesh,

Scenario testing is going on, Damion & Ashley are working on this.

Vinayak Kulkarni
I have another Client Inquiry:
We have created a Deceased QE, and only the terminations records passed properly. All of the active records that passed with a new effective date did not get the QE date. Im going to send an example member via email.

Production
Client: UND For Banner Payroll Testing

email:
Hello Again,

After a call today the client asked if we could do the following.

Between the two fields Effective/Termination date and Qualifying Event Date. All of the term records passed a 3/31/2016 and the Event date however the Active records have 4/1/2016 in both positions. The QE Date field should have the QE Date
Thank you

Damion,

QE date works as follows,

For new hires = Employment date
For Rehire = Rehire date
For QE ( only QE not review change approval ) = Event date
For all other
Election Effective date.

In this case, event is review change approval, so QE date is appearing as Election effective date.

You can try election or rate change date, this will populate date on which election is changed.

Vinayak Kulkarni
I tried the MACRO you suggested but you are correct, it only gave the Action Date when Ashley entered the transactions (3/18/2016). This will not work for UND. We will need to know what it would take to
1) Get the review change approval to associate with the QE
2) When a term of plans happens for (Divorce, death, etc) the active records that come back need to associate with the Qualifying event that occurred.

We are unclear if this can be done at the client level or that it may be a system wide change that needs Higher level of approval

Hi Damion,

here is response from development team on expected change,

Requirement : As per existing functionality, Enrollments terminated due to employee data change Event are terminated with Employee data change mode(i.e. 14)
As per requirement, instead of Employee Data Change mode, Qualifying event mode is not reflected with which employee data change is done
Feasibility : If this change is done, we won't be able to identify, if employee data change caused termination or employee himself changed enrollment.
Also, this will have major impact on system and it is generic change. So, this change should not be taken as enhancement.

Same email is forwarded to you.

This is to add in the QE dates to the Active Records with QE Codes on the Banner File

Rohan J Khandave We will discuss this on Monday's call, Thanks.

Find below details about UND banner payroll.

1] Employee part

employee logs into system => does changes and elections goes for admin approvals => Admin approves them.

Problem #1: Active Records are coming up with proper QE Code but not with QE date
Solution: We have done code changes to get QE Dates proper. This will come into production by Tuesday 04/12/2016.

Problem #2: Terminated records do not have QE code & Date.
This is because of Review Change Approval due to which QE codes are not getting stored for terminated records

Solution: Our EDS team is analyzing this on Priority and We would get response by End of Monday.

2] Admin part

Sam is going to ask UND for list of QEs that Admin will do by themselves.

We are good with below Admin items,
1] If Admin does Employee status changes like Termination of employment or deceased
2] If Admin adds coverage with QE like child birth

We have problems with below,
1] If admin drops coverage through Employee Data change, like using Divorce QE.

Cause:
If Admin is changing something, it will not go for approval.
Lets say Admin changes Employee's Spouse status to Ex-spouse which will terminate spouse from coverage.
Here, Election are changed due to Employee data change, regardless of QE used to change spouse status.

So here all active & terminated records will fall under Employee Data Change and not QE.
Although you can send Employee Data change on file.

Correction: We have workaround but you need to ask UND for this.

Workaround: Admin needs to change enrollment directly with QE from enroll now screen.
Admin needs to drop spouse from coverage using QE from enroll now screen first and then make spouse to Ex-spouse.

For Terminated & deceased, please try with separate export templates as discussed.

Let us know if you have any queries on this.

Hi Priya,

Can you please look into this ?

Thanks & Regards,
Aniruddha Dev

The above concern is checked on LB with Employee and Admin part.
Problem #1: Active Records are coming up with proper QE Code but not with QE date:
Now, on exported file active records are coming with correct Qualifying date.

When the Admin approves the Employee request of qualifying event then the exported file displays the date of qualifying event.

The patch is ready for Stage.

The above concern is checked on Stage with Employee and Admin part.

Problem #1: Active Records are coming up with proper QE Code but not with QE date:
Now, on exported file active records are coming with correct Qualifying date.
When the Admin approves the Employee request of qualifying event then the exported file displays the date of qualifying event.

The patch is ready for Production.

The mentioned concern is checked on UND for HSPL. Now, the QE Date is updated as per the date of Qualifying Event.

The issue: Active Records are coming up with proper QE Code but not with QE date is tested, verified and closed on production.

Vinayak Kulkarni: can you please assign to authorized person.

Hi Damion,

We have deployed fix for Active records Event dates, please verify, Thanks

sam lindberg

sam lindbergVinayak Kulkarni
Sam will add in some scenarios to test.

Assigning to you.

Hi Satya:

Whats the eta to get the term code logic into stage? Ideally, I would like it to be in by Friday so me and the clients can test it in stage on Monday. Please make sure to regression test for the active code logic.

Tell me if you need more time.

I would like the code to move to prod by end of next week if testing goes smooth.

Thank you,
Sam

Hi Satya:

What's the progress of the termination logic build?

Can you explain the solution you came up with?

Thank you,
Sam

Please See prior notes in regards to qe code and date for term lines.

Hi

What is the progress of the term code?

Thank you,
Sam

Terminated records issue - for EDS & Enrollment

Hi Sam,

For terminated record issue there is separate ticket created WT-1766. for this point currently development is going on.

It's development is getting completed by Wednesday, 4/20/2016. We will update you on its ETA for Stage.

Thanks & Regards,
Satya Prakash

Hi Sheetal,

Please update comments in this ticket after completing development. This is parent ticket for

• WT-1766
• WT-1823

Thanks & Regards,
Satya Prakash

Hi Satya,

I have updated the WT-1823 ticket which is assigned to me.
Girija PotdarPlease update WT-1766 ticket.

Thanks,
Sheetal.

Hi sam lindberg,

This is deployed on stage today.

Thanks,
Sheetal

Verified feed on Stage. It is working proper.

Sheetal Bodhale Please deploy patch on Production.

CC; Alankar Chavan Deepali Tidke

Damion M Velasquez

Hi Damion,

This fix moved on production and working as expected.

Thanks,
Hrishikesh

Vinayak Kulkarnisam lindberg]Sent email regarding server error. Global template will not run

QE_UND_BANNER_PAYROLL

Hi Damion,

Please try now and let us know if you still get an error, Thanks.

Hi

On the latest payroll we tried to run we did not get any qe dates and codes fro the following employees.

Thomas Schaefer
Aaron Gills
Erin Camilleri

We had qe events run on them.

WE need this asap.

Thank you,
Sam

Hi Sam,

First of all, you should Re-Open closed JIRA ticket if you feel its not working, only then it will come up as Action item for us.
As of now, i have re-opened it.

About QEs, For first employee Thomas Schaefer, we can see Death QE is raised and employee status is still active, is this realistic that employee will do QE for deceased?? I think Admin has to do employee status change to Deceased and we will have separate EDI templates for deceased and terminated ones .

We will go through this together tomorrow first thing in the morning and also discussion this with Damion Thanks.

Damion M Velasquez

Hi Vin

Damion tested the the file but it did not populate the QE dates and QE codes. Can you look on the backend and see why its not pulling them?

Please look in Y:\1.CLIENT\Notre Dame\5. EDI\Structure_Specs\Banner file\2016 QE Banner\Test Files\4-27-2016

Thank you,
Sam

Vinayak Kulkarnisam lindbergCindy Wibbing

Vinayak. Since we cannot put PHI into JIRA I cant reference the members that have QEs but didn't reflect any code whether active or termed. There are a lot of rows that have values however are from 2015 OE and prior and are not valid in this file. I cloned all 9 templates and updated the status within each one. Term template status's are Deceased, Inactive, and terminated. These are omitted from the other grouped templates.

Group Template
QE_UND_Banner Payroll
Compay Level
QE Illusions Banner Employee Supp Life
QE Illusions Banner Child Dependent on Employee Life
QE Illusions Banner Spouse Dependent Life
QE Illusions Banner Accident Employee Paid
QE Illusions Banner CI Employee
QE Illusions Banner Payroll
QE Illusions Banner HRA
QE Illusions Banner Accident Employer Paid
QE Illusions Banner CI Employer

Compay Level Term templates
QE Illusions Banner Employee Supp Life_Term
QE Illusions Banner Child Dependent on Employee Life_Term
QE Illusions Banner Spouse Dependent Life_Term
QE Illusions Banner Accident Employee Paid_Term
QE Illusions Banner CI Employee_Term
QE Illusions Banner Payroll_Term
QE Illusions Banner HRA_Term
QE Illusions Banner Accident Employer Paid_Term
QE Illusions Banner CI Employer_Term

sam lindberg I dont have access to Y drive, can you please send that file to me?

Damion M Velasquez sam lindberg I will come to you to check this tomorrow morning.

What's the projected resolution on this requirement for Notre Dame? I thought Dave presented a solution for this to Development and here we are still with no final resolution.

Hi All:

We went through testing and found some issues so we are now doing more dev and also updating the templates that extract the payroll.

Dev code should be migrated to prod on Tuesday.

Thank you,
Sam

Sam,
All the code changes are deployed production, please check.

I have setup the tc.

candr5853351075107 divorce
dgump5735370817081 marriage but I termed benefits
wbren0815439683968 Birth
amani3135077197719 death of child and spouse
awilk3089886778677 Dependent spouse or child obtains insurance

Hi Sam and Damion,

Other records did not come on file because they are not approved.

And for last two records no QE code is associated that is why QE date is not populated. and date that is there would be election effective date.
This must be an employee data change event.

Also, please note that, all code and changes are in production.
So there is nothing pending from development for this file.
Please review file and changes and let us know if you feel something is not working.

Satya Sachin Khandge Rohan J Khandave

I approved the pending enrollments.

Damion can you run the payroll one more time and make sure its good.

If it runs ok and you feel its perfect, lets release it into the wild.

Thank you,
Sam

testing is complete.

testing passed.

Thanks everyone that worked on this.

it looks like the new new hire QE is not getting a code. Can we hardode this by a status or something in the back end so it doesnt have to be a major change?
Vinayak Kulkarnisam lindbergSatyaRohan J Khandave

New hire is not QE, its individual enrollment mode and fix was done for QE only.
We have "Is NewHire Employee" mapping field which is Yes/No DTS field, but this will be new column on file, now sure whether client accept new column only for new hire.

I will talk to team about this new hire scenario and get back to you.

CC Rohan J Khandave Satya

Hi Vinny:

For New hire i want it to have a qe code of 01, Also the qe dates should be the effective date of the benefits. The effective date will be populated for the event date as well. New hire is a qe event based on UND discussions.

This needs to be updated today so we can rerun the file tomorrow and send it to them for review.

thank you,
Sam

Hi Sam,

I have commented on 4th May 2016 on this JIRA that all the logic is deployed on production and do test and let us know if you feel something is not working. Now after 10 days if you are feeling new hires are not working and want to get it done over the night is incredible.

Still, I talked to Rohan J Khandave yesterday about this and we are analyzing this change. As this will be changed for all of the clients so if in future some another client wants Review change Approval instead of new hires then we would face issues again.
That is why we are planning conditional solution which will satisfy both.

Rohan will update you about ETA.

Sam when something is released for testing make sure that all scenarios are tested before moving to PROD. This appears to be a missed step in testing. Is that that the case? Or did the client request further modification? Regardless, we need all requirements and testing complete before they are moved to PROD>

Hi Steve:

I did not realize that new hire would be included in the qe code. Much of the requirements were outlined before i was on the client.

I spoke with them and asked for clarification.

Thank you,
Sam

Hi All:

What's the ETA til completion?

Thank you,
Sam

Hi sam lindberg,
We have created separate JIRA WT-2490 for this ,This will move to local Environment on 23rd May 2016 then will move to production as per the patch process .

Hrishikesh Deshpande Aniruddha Dev Please provide the Stage ETA for WT -2490.

Hi Damion M Velasquez,
CC-Hrishikesh DeshpandeVinayak Kulkarni sam lindberg

We have made changes for New hire ScenarioWT-2490 ,we need confirmation what output is expected for following scenarios.
1)In case of Rehire if Enrollment is pending for approval then after approval what should be expected output for Enrollment change in election reason field on file?
2)In case of Open Enrollment if Enrollment is pending for approval then after approval what should be expected output for Enrollment change in election reason field on file?
3)Please confirm that do you need this changes only for UND or generic for all companies?

Please note that changes are currently on local Environment and will move after confirmation of above scenarios.

Sent confirmation request to client:
Good Morning Mary,

This coding is near complete, however we wanted to insure that all possible scenarios will get 100% QE Code Coverage for new hire, Rehire, and Open Enrollment Events. Can you help with the 2 below points?

1)In case of a Rehire: if Enrollment is pending for approval then approved; what should the expected output be for QE Code field on file? Potentially map this to '01' new Hire
2)In case of Open Enrollment: if Enrollment is pending for approval then approved; what should be expected output for QE Code field on file? Potentially map to '10' Admin QE

UND Requested QE's
1) a 2 digit QE indicator with values
01 - new hire enrollment
02 - job status change
03 - child birth or adoption or granted legal guardianship
04 - dependent spouse or child loses his/her insurance coverage
05 - married
06 - death of dependent
07 - dependent child loses eligibility
08 - dependent spouse or child obtains insurance
09 - divorce
10 - admin change

Thanks Mary

Rakesh ShahaneVinayak Kulkarni[~sam.lindberg@ebsbenefits.com}

1)In case of Rehire if Enrollment is pending for approval then after approval what should be expected output for Enrollment change in election reason field on file? Rehire will follow the new hire rule. If new hire/Rehire Value 01
2)In case of Open Enrollment if Enrollment is pending for approval then after approval what should be expected output for Enrollment change in election reason field on file? Open Enrollment will be a NULL value
3)Please confirm that do you need this changes only for UND or generic for all companies? This should be treated the same as the prior Sprint. I am not aware whether it is for System Wide or at the Client.

This is a sever high priority

Thank you

From: Mary Kocks mkocks@nd.edu
Sent: Friday, May 20, 2016 11:49 AM
To: Damion Velasquez
Cc: Steven Cohen; Sam Lindberg; Jim Heide; Cindy Wibbing
Subject: Re: banner testing

Yes, new hires and re-hires would both have a '01' QE indicator.

On Fri, May 20, 2016 at 2:42 PM, Damion Velasquez <damion.velasquez@ebsbenefits.com> wrote:
Thank You Mary

Would it be safe to say that #1 is accurate. That a REHIRE would be coded the same as a NEW HIRE?
1)In case of a Rehire: if Enrollment is pending for approval then approved; what should the expected output be for QE Code field on file? Potentially map this to '01' new Hire?

Damion Velasquez | EDI, WORKTERRA
Employee Benefit Specialists, Inc.
PO Box 11657, Pleasanton, CA 94588
PH: 925-469-5223 | FAX: 925-460-3920 | damion.velasquez@ebsbenefits.com

From: Mary Kocks mkocks@nd.edu
Sent: Friday, May 20, 2016 11:17 AM
To: Steven Cohen
Cc: Damion Velasquez; Sam Lindberg; Jim Heide; Cindy Wibbing
Subject: Re: banner testing

Damion,

We would expect all Open Enrollment records to have an 'O' in the first character and a null QE indicator.

Mary

On Fri, May 20, 2016 at 12:20 PM, Steven Cohen <scohen3@nd.edu> wrote:
Hi Damion,

I can't speak to what code we should receive back for Open Enrollment since we get an O back instead of a Q for the record, but during OE we don't allow any pending changes. Whatever an employee selects goes through. Due to the large employee base we have, manually approving all of the benefits would be too lengthy of a process.

Thanks!

On Friday, May 20, 2016, Damion Velasquez <damion.velasquez@ebsbenefits.com> wrote:
Good Morning Mary,

This coding is near complete, however we wanted to insure that all possible scenarios will get 100% QE Code Coverage for new hire, Rehire, and Open Enrollment Events. Can you help with the 2 below points?

1)In case of a Rehire: if Enrollment is pending for approval then approved; what should the expected output be for QE Code field on file? Potentially map this to '01' new Hire
2)In case of Open Enrollment: if Enrollment is pending for approval then approved; what should be expected output for QE Code field on file? Potentially map to '10' Admin QE

UND Requested QE's
1) a 2 digit QE indicator with values
01 - new hire enrollment
02 - job status change
03 - child birth or adoption or granted legal guardianship
04 - dependent spouse or child loses his/her insurance coverage
05 - married
06 - death of dependent
07 - dependent child loses eligibility
08 - dependent spouse or child obtains insurance
09 - divorce
10 - admin change

Thanks Mary

Hello Damion M Velasquez,

We are working on this functionality. Code which mentioned in above comments can be an achieve by DTS.

But can you confirm scope for above change like generic or company specific? We have scan production companies for feeds where "Enrollment Change Reason" is mapped PFA for same Election Change Reason Mapped Feeds List.xls

So generic change will impact feeds across companies. So please give inputs for same.

CC-- Vinayak Kulkarni Satya sam lindberg

Rohan J KhandaveVinayak Kulkarnisam lindberg
Rohan, I dont know if this is my call to make, without seeing the code. Is this just a table being added to the back-end? if so we would anticipate company level. I believe all of the other updates for this QE Code process has been a system wide change.

sam lindbergSam your thoughts

CC: Cindy Wibbing

Hi Rohan:

Company level would be most appropriate.

Thank you,
Sam

Hi Rohan:

Was this migrated to prod? If not when will it be done?

Thank you,
Sam

Can we move forward with this ticket?

Hello sam lindberg,

Please find below comments which i commented yesterday on JIRA WT-2490

Hello Damion Velasquez,
Thanks for your reply , we have start working on this issue.
We are developing new field(Election Change Reason Of Review Pending) which will will work accordingly "Election Change Reason" along with changes suggested by UND for New Hire.
So please find changed estimation.

sam lindberg

Hi Sam,

We have deployed WT-2490 on Production. Please verify this at you end.

Let us know in case of any queries

Thanks & Regards,
Aniruddha Dev

hi Damion

Please go ahead with testing.

Thank you,
Sam

Can yo ulook into this? We are not able to get a new hire QE when the Qualifying Event happens. Test employee
Damion Velip entered today as the employee with a QE

sam lindbergRohan J KhandaveVinayak KulkarniSatya

Can we get a call setup nightly to review this together until resolved? i.e. 8pm PST - 9:30am IST? We can't keep losing 12-24 hours on back and forth on testing, research, etc.

Damion, please setup a call with you, Sam and whoever makes sense on DEV side until resolved. If we don't need the call just cancel....but we need to get daily updates on this until resolved.

Thanks,
Steve

Steve Allisonsam lindbergAmit GudeVinayak KulkarniAniruddha DevRohan J KhandaveSatyaGanesh SadawartePradeep Kanojia [X]

Hello All,
Please provide times you can be available for a call to discuss the status of this last updating we are trying to accomplish for this feed to go LIVE for the Client. We understand Harbinger may have off-time availability due to the Time Difference, and we will make accommodations as needed

Issues on the TABLE: No QE Code for new Hire Qualifying Events. The client and Sam have both entered transactions for New hire and no codes are populating.

Thank you and please advise ASAP!!!! we need to get on the phone and discuss strategies for this to be finalized

sam lindberg Damion M Velasquez

Hi ,

The new fields 1) Enrollment Election Change Reason of Review Pending 2) Enrollment Qualifying Event Date of Review Pending which were exposed need to be mapped on the template . We see this mapping is missing on Template . We will map this and will update you on this .

Thanks & Regards,
Aniruddha Dev

Aniruddha Dev Will #1 be allowed for Data Transformation?

Thank you

sam lindberg

Damion M Velasquez

Hi Damion,

Yes, #1 is allowed for Data Transformation.

Regards,
Aniruddha Dev

Aniruddha Devsam lindberg

I did a quick mapping/export on template: QE Illusions Banner Payroll. For the new hire we added I see 'General' and 'Review Change approval' populating on File because I didnt DTS those fields. Question: Will General or Review change approval 'alone' happen in any other scenario other than New Hires? Thanks

Damion M Velasquezsam lindberg

Hi Damion,

Please go through our comments below

Enrollment Change reason - Review Change Approval

This happens whenever enrollment goes for Admin Approval . Such as New Hire Enrollment , Re-hire Enrollment, Force Contingent Plans etc.
We have checked records for Test Employee 'Rosie Test'. This employee got change reason as 'Review Change Approval' for 'Wellness Center' plan. This plan has force contingency on 'Medical Waiver' Plan (Please find attached screenshot). When employee has new hire mode and as admin approval is pending for 'Medical Waiver' due to that 'Wellness Center' enrollment is not added. When admin approves "Medical" enrollment then as per forced contingency 'Wellness Center' enrollment gets added with latest enrollment mode of "Medical Waiver Plan" i.e Review Change Approval.

Enrollment Change Reason - General
This happens in case of Core Plan Allocation.
In case of 'Rosie Test' employee . Travel Insurance Plan is a Core Plan . So records for this plan will have 'General' as enrollment change reason.

This is as per our current implementation.

Thanks & regards,
Aniruddha Dev

sam lindbergsent test file to UND. There is a small pool of missing QE Codes for TRV, Wellness and LFX plans which is expected. Will wait for results

SatyaVinayak Kulkarnisam lindberg
Hello,

We ran across one issue with the templates below. Transaction on the following members were done and are not passing on the file
1) Spousal Life was added for a Marriage QE, but the record was not sent in the file - ID #900501769
2) For a child birth QE, spousal life was waived and the new baby was added to child life. Neither record was received back in the file. - ID #900548102

EMPL ID:
QE Illusions Banner Child Dependent on Employee Life
QE Illusions Banner Spouse Dependent Life

Hello Damion M Velasquez,

We checked both employees below are details for same.

1) EMP ID - 900548102 , Spousal Life Insurance : Enrollment into "Spousal Life Insurance" got dead on 12/17/2015 with by user "Farida Suhardjo". And in OE user waived on 05/12/2016 by "steve cohen". So employee is never enrolled into "Spousal Life Insurance". Also termination reported on 04/29/2016 and template is changes only.

For Child Life & Spouse Life , we checked "Effective Date Service" services is not executed on "UND For Banner Payroll Testing" company as this is test company. We run this service today and exported file again. Both Child & Spouse life enrollments exported on file.

Note : For daily services we are considering this company only.

CC – Vinayak Kulkarni , Satya , sam lindberg

Hello Damion M Velasquez,

Please close ticket if above details satisfying or if you required more information.

Posted a new test file and see records missing for Spousal Life and child Life are now appearing.

sam lindberg

Hi Dev:

Could you help me import this test data to test the banner demo data. The layout we are supposed to use is "emp demo initial load." Employee Demo.xlsx Employee Demo.txt. I keep gettting an error of Error(s): Total fields in file does not match total number of fields in template.

The goal is to import the the new hires so that the MD wellness plan populates. We are not seeing the wellness plan having the QE code during a new hire.

Can you see why in the new hire scenario MD wellness code is not getting the qe code?

Can we get this completed by tomorrow? It would be fantastic.

Thank you,
Sam

Hi ,
We have corrected '_Employee Demo Initial Load' import template with respect to 'Employee Demo.txt' file on 'UND For Banner Payroll Testing' as well as on 'UND For Banner Payroll Testing for HSPL'. I have corrected file for Last name , because Last Name should not contain Numbers. we have successfully imported corrected import file on 'UND For Banner Payroll Testing for HSPL' company,

Please have a look and let us know if you are facing any problem during import.

hi Vishal:

I still get the error for not the the correct number of fields.

Can you load my corrected file to the UND For Banner Payroll Testing?

Thank you,
Sam Employee Demo.txt

Hi sam lindberg ,

We have imported given file on "UND For Banner Payroll Testing" successfully.

Please have a look.

Thank you very much. What did you do upload the file?

Sam

What was the problem? Why was Sam getting an error?

Hi ,
Total fields in file does not match total number of fields in template. Fields count in template is 31 but there were 30 fields in sams files so this files goes to bad. I have added only one blank column in file and imported. its succeeded.

Thanks.

Hi Sam,

Please see above comments for import file issue details.

Regarding Medical Wellness code:

MD wellness plans is force contingent on medical, which means whenever an employee opts for medical then employee will automatically get wellness.

But due to approval is required for new hires, whenever an employee opts for medical, it goes to pending and wellness will not allocate automatically due to medical is not approved.

When admin approves medical then at that time employee will get wellness and which happened due to admin approval thus system is not considering this as new hire for wellness.

You may consider same QE code for wellness as of medical QE code. But due to force contingency and approval for new hires combined causing wellness code to be blank on file. We will analyze this further to get some sort of solution, we will update you on this by tomorrow.

Hi Damion:

I updated some testers to have MD plan. Sam lindberg is the name of the testers.

Also, Can we have the wellness to code just like the medical plans that pend?

Thank you,
Sam

Hi Vin:

I would like it to have similiar logic as the medical plans.

Thank you,
Sam

Hi Damion:

Were you able to update the logic to code for the welness based on what DEV said?

Thank you,
Sam

Hi Dev:

Can you update the logic so the wellness plan populates with the correct code.

This needs to be done tonite. We cant wait. This is critically urgent?

Thank you,
Sam

Hi Satya:

Can we get this completed today? This is super critical. Vinayak would probably be the best to finish it.

thank you,
Sam

this is not complete

Yes Sam,

We are working on this ticket on priority today. You will get updates by EOD for sure.

Thanks & Regards,
Satya Prakash

Hi all:

Is this complete as the client is expecting it today? What do you need from me?

Thank you,
Sam.

Hi sam lindberg

As we discussed in the call, development team have corrected the existing data and it is exporting as required on the file.

For any new data that will be coming in, or any updates to existing data, we are preparing a trigger that will set the data to values as required on the export file. Development of this trigger needs some more time and we also need to test it to confirm it is working correctly for all expected scenarios. We should have this ready by tomorrow (Friday).

We have also started development for an enhancement that will handle this scenario through the application for all companies in future.

Let me know if you need more information or if you have any concerns.

Thanks @ Regards
Shubhankar Joshi

CC: Vijay Siddha, Satya, Vinayak Kulkarni, Jyoti Mayne, Rakesh Roy, Aniruddha Dev

Hi Shubhankar:

We reran the payroll file today with scenarios and we had many that did not have code. Could you please look into these? I have attached a sheet, please look at the red highlighted rows. The yellow is the wellness. and the green are to be expected with no code. I think it may be a systemic issue.

Once the fix is complete. Can you run a new payroll file and attach in this ticket. I will send this file to the UND team.

Thank you,
Sam Copy of UND BANNER 6.16.2016.xlsx

Hi All,

The data correction done yesterday was tested for scenarios related to Plan Contingency changes and for these corrections data exported correctly on feed. After analyzing the file provided by Sam, we observe that Plan Design Eligibility has also been changed on June 15th (screenshot attached) which has caused a change in elections and also resulted into some terminations.

UND has not configured any code for elections/terminations due to Plan Design Eligibility changes. Also we do not expect these to happen on UND going forward. However, if UND configures a code for changes due to Plan Design Eligibility Changes, the same will also start getting exported on the export file. See below.

Today, we have implemented a trigger to handle election changes done through review changes & deployed this on 'UND For Banner Payroll Testing' on production.

Note: We found eligibility of wellness plan on UND payroll test company and actual UND company is different so that we have changed it and made both same. You will not see wellness plan in tunnel as it is forced on Medical waiver. But you can test it on payroll file.

Do not change eligibility of any plan to avoid this kind of issue again in future also Please create new scenarios and test them on payroll file.

Hi Vin:
Also what happens when a plan elig setting is changed? Will we need to change the code?

Can you run the payroll file for me as we need it early this morning to send to UND? Please attach in this ticket.

Thank you,
Sam

Hi Damion:

can you rerun the file ASAP?

thank you,
Sam

Hi David:

For the payroll, currently we are seeing alot of no qe codes for scenarios that the client entered into the site. We sent the tix back to DEV and pointed out the ones that needed codes. We can't reinput the scenarios since they all came from the client.

The only thing that came out of client test was the wellness code needed updating. But now we are getting alot more missing qe codes. I don't understand when we rerun the payroll it not stepping though the system and reassigning the missing codes.

The client was expecting to have file today.

Can you help to get this resolved?

Thank you,
Sam

sam lindbergDavid Rhodes

reran file and same issues. I do not think at this point we can ask UND to re do all of the transactions they entered. We are expected to deliver a file, and have many Blank Values for QE code.

I just sent an email to development to get on this ASAP. I did see an email from Vinayak that said someone changed the customization and those changes led to terminations. They are no codes set for terminations done by altering the plan customization. Was this checked as the reason for the missing codes you are seeing?

Hi all:

I have attached the test scenarios that und used.

Please delete the changes and then push the file in to recreate the changes. Can you please recreate the payroll file and attach in this ticket? I need to send this to UND today as they want to review it this affternoon.

Thank you,
Sam

As discussed with Sam in call, we are creating scenario & will share test file.

Thanks & Regards,
Satya Prakash

Hi sam lindberg,

CC-Satya,Rohan J Khandave,Vinayak Kulkarni

We have done with all scenario in attached excel now code are not populating blanks except for life as its already communicated. We generate payroll file with below scenarios.

• New Hire Enrollment
• Child Birth or Adoption
• Dependent Spouse or Child Loses Coverage
• Married
• Death of a Dependent
• Dependent Spouse obtains Insurance
• Divorce
• Admin Change

Please find attached test payroll file UND_BannerPayroll061720161704.7z. and if you want test another you can test but please do not delete last 2 run dates.

For New Hire Enrollment please refer below test employees
901999082
901999083

Password: undpayroll

Please check and let us know if you face any problem.

Thanks,
Ganesh

Are you sure this is thoroughly tested? It seems every time we are told it is ready Sam and Damion take 5 seconds to find problems.

Hello Damion M Velasquez & sam lindberg,

QA team is still testing file also verifying scenarios mentioned into Copy of UAT OE Testing Script_06172016 (002).xlsx , client use these scenarios for file testing . QA will update there testing status once they completed scenarios mentioned into above excel file.

CC – David Rhodes Vijay Siddha Satya Rakesh Roy Ganesh Sadawarte Vinayak Kulkarni Hrishikesh Deshpande Aniruddha Dev

sam lindberg Damion M Velasquez

Hi Sam,

We have created Test scenarios on UND for Banner Payroll testing company on Production and exported Payroll file.
Please find attached Zip UND File and Scenarios.zip for Test file and Scenarios. Password of Zip followed in Email to You and Damion.

Our Test scenarios are as same as clients scenarios. We used different employees for our test scenarios.

We have also tested this file from our end and observed that there is no any Blank QE code or date exporting on file. File Structure and records are proper.

*Please refer file (Attahced in Zip) for final UAT and Ignore previous File which was attached by Ganesh. *

Let us know if you need any details from our end.

Thanks,
Hrishikesh.

Hi

Can you look at the file i ran, please see attachement? The major thing I noticed was the FMC and FDC did not have codes? Is this to be expected?

The LTD, TRV, LFX did not have codes which I was expecting since they are all employer paid.

The MD looked perfect.Great fix there. Thank you for taking the time this weekend to work on this!! I appreciate it. full payroll from 1.1.2016 to 7.1.2016.xlsx

Thank you,
Sam

Hi Sam,

As discussed with you in call , we are not sure from which company this file ran ( from 01/01/2016 to 07/01/2016).
we can see last exported file from UND test company is by us, see below

Please note that, all the logic for these QE codes is on UND test company and not on regular UND. also records that will change due to QE going further will have QE codes on file.

so if you export file from 01/01/2016 then you would get some records with blank QE codes as at that time we did not have QE codes logic that we have built recently.

Please consider test file given by Hrishikesh in above comments. Let us know if you have any questions on this.

Hi Damion:

Can you assess the payroll file and make sure everything is to be expected? Once its done please send it to the UND team. Please note we recreated the scenarios because the we made a code change and that only new changes would get the qe codes.

Also can you run a full payroll file as well as changes to make sure we are solid.

Thank you,
Sam

sam lindberg Damion M Velasquez

Hi Sam,

We have found issues in two scenarios which is attached in UND.xls . Enrollment team is working on the fix for these. All other scenarios are working fine.

Regards,
Aniruddha Dev

CC: Rohan J KhandaveHrishikesh DeshpandeVinayak KulkarniSatya