Hi Jennifer,

Vinayak Kulkarni,Rohan J Khandave

We have updated templates to solve below issue but codes are still pulling from PDHT mappings. We have not moved PDHT mapping to new positions. If we need to move benefit plan codes from PDHT mapping to somewhere else then we need Deduction codes list with all variations. It must contain all things that trigger code, like Plan Name, Class1, Healthtier, etc.

Please let us know below issue are solved? and provide details code list for PDHT mappings so we can move them.

Thanks ,
Ganesh

Jennifer LeugersPlease update.

Open items as of today

FDU Medical Payroll file

Open Items:

1. File headers are incorrect. Headers should follow the file specs as laid out in the excel file named: Health Ded layout options May 28 2015

2. File naming convention – please add a .csv extension at the end

3. Plan type is incorrect. Please refer to “plan type” tab in the file: Medical payroll – codes 010116.xlsx (POS = 12, DP lines = 10, CDHP plans = 11)

4. Missing domestic partner lines of coverage

5. Waiver code missing - On file name: FDU Payroll201602261052, Hannah is a new hire who waived coverage. The Participation code should be “W” instead of “E”

6. Benefit plan waive (member is still in an active status) – See file named: FDU Payroll201602261319 – Jasmine was in the medical benefit and then waived coverage effective 2/5/16. The waiver line should show the two code columns (Benefit plan and coverage code) as blank.

a. Also for this record, two lines appeared, one with a participation code of “E” and one with a “W”. this record should only have one line with a W. the E line should drop.

7. When a member is terminated from a plan due to a change in EE status to termination (member example: Dinah and Hannah):

a. The date of the plan term should appear in the Effective date column (currently showing plan enrollment effective date)

b. The Participation code should be I (currently showing W)

FDU Other Payroll file

Open Items:

1. File naming convention – please add a .csv extension at the end

2. File headers are incorrect. Headers should follow the file specs as laid out in the attachment “Deduction enrollment layout 7-9-13 within the email titled “FW: test file on second secure email”

3. Deduction amounts for all benefits (with the exception of those benefits where we are providing the annual flat amount) needs to be per pay period, not monthly

4. Metlaw “x” benefit is showing two lines, one with a cost of $0.00 and the other with the monthly cost. We should only be seeing the 2016 benefit.

5. During a change in the benefit the file is sending a term of the previous line and then a new line. We only need to send the new line of coverage.

a. Example: File name FDU Others201602261155 – EE Missy, ded code “I” changed from cost $0.00 to $16.80 due to an approved EOI, both the 0.00~ was sent and the new 16.80. We only need the new line of 16.80

6. Terminations – Tilde needs to be removed from the Deduction code and place by itself in the ded amount column

7. Still missing Child life and Child AD&D from this file

8. Missing HSA elections

HI all - as per our call yesterday, we were going to give UHC an ETA on the above issues getting fixed. Please provide.

Hi Jennifer, We will provide new test file by fixing above issues by PST Friday morning.

Jennifer Leugers,Vinayak Kulkarni,Rohan J Khandave

Hi Jennifer,

We made change in templates for above reported issue. Please refer last exported file of group templates _FDU Payroll and _FDU Others

Thanks,
Ganesh

Thanks. Also attached is the file requested from UHC.

Hi Jennifer,

CC- Vinayak Kulkarni,Rohan J Khandave

We checked attachment. We are checking that how to handle additional criteria for deduction code and let you know the details for this.

Thanks,
Ganesh

Hi all - any updates on this? Looks like the last comment was about ten days ago. Thanks!

Also - please see below on the changes that were made.

We are getting closer! A lot of the open items are now showing correctly and can be closed. I indicated these below in green text.

Anything with red text is either still and issue or a new issue (both of which are indicated below in red text)

Please let me know if you have any questions or need any more details.

Also, I noticed that we had a mistake on a couple of fields on the mapping document in regards to the payroll calendars. Sorry for any confusion, I’ve included the updated mapping document. There were only 3 fields that I updated (highlighted in Yellow).

FDU Medical Payroll file

Open Items:

File headers are incorrect. Headers should follow the file specs as laid out in the excel file named: Health Ded layout options May 28 2015 – RA - Corrected

File naming convention – please add a .csv extension at the end – RA - Corrected

Plan type is incorrect. Please refer to “plan type” tab in the file: Medical payroll – codes 010116.xlsx (POS = 12, DP lines = 10, CDHP plans = 11) – RA - Still incorrect (see file: FDU Payroll201603180940 – the POS and CDHP plans are reversed. Grace is in POS and s/b 12, 1010119 is in CDHP and s/b 11)

Missing domestic partner lines of coverage – RA - Corrected

Waiver code missing - On file name: FDU Payroll201602261052, Hannah is a new hire who waived coverage. The Participation code should be “W” instead of “E” – RA - Corrected

Benefit plan waive (member is still in an active status) – See file named: FDU Payroll201602261319 – Jasmine was in the medical benefit and then waived coverage effective 2/5/16. The waiver line should show the two code columns (Benefit plan and coverage code) as blank.

Also for this record, two lines appeared, one with a participation code of “E” and one with a “W”. this record should only have one line with a W. the E line should drop. – RA - Still an issue, there are still two lines appearing with participation codes of “I” and “W”. Only the line with a W and a ~ in the Benefit plan column should appear. (Example on file: FDU Payroll201603181325 Grace)

When a member is terminated from a plan due to a change in EE status to termination (member example: Dinah and Hannah):

The date of the plan term should appear in the Effective date column (currently showing plan enrollment effective date) – RA - this iscorrect for the non DP lines, however the DP line is still showing plan enrollment date. (example file: FDU Payroll201603181325 ID Rory)

The Participation code should be I (currently showing W) – RA -This is correct for non DP lines. However the DP lines are still showing “W” instead of “I” (example file: FDU Payroll201603181325 ID Rory)

03/18/16 New – Coverage Code column should be blank for a term, currently showing coverage code. (example on file: FDU Payroll201603181325 ID Rory)

03/18/16 New – Domestic Partner Term – the Benefit Plan should be a ~. Currently showing the ben plan code (example on file: FDU Payroll201603181325 ID Rory)

03/18/16 New – Missing benefit plan code and Coverage code for ID Karyn, who newly added the benefit (should have had a benefit plan code and coverage code of “ES11”. See file: FDU Payroll201602261052

03/18/16 New – Question – Was this file: FDU Payroll201603040533 – a full file? it seemed to only pick up all waivers and didn’t show the full population with medical benefits. On the next test file, could you please provide a full file?

FDU Other Payroll file

Open Items:

File naming convention – please add a .csv extension at the end– RA - Corrected

File headers are incorrect. Headers should follow the file specs as laid out in the attachment “Deduction enrollment layout 7-9-13 within the email titled “FW: test file on second secure email” – RA - Corrected

Deduction amounts for all benefits (with the exception of those benefits where we are providing the annual flat amount) needs to be per pay period, not monthly – RA - Corrected

Metlaw “x” benefit is showing two lines, one with a cost of $0.00 and the other with the monthly cost. We should only be seeing the 2016 benefit. – RA - Corrected

During a change in the benefit the file is sending a term of the previous line and then a new line. We only need to send the new line of coverage. – RA - Corrected

Example: File name FDU Others201602261155 – EE Missy, ded code “I” changed from cost $0.00 to $16.80 due to an approved EOI, both the 0.00~ was sent and the new 16.80. We only need the new line of 16.80– RA Corrected

Terminations – Tilde needs to be removed from the Deduction code and place by itself in the ded amount column– RA Corrected

Still missing Child life and Child AD&D from this file – RA - Corrected

Missing HSA elections – RA - The HSA election appears, however, the Deduction code (HE) is missing. (example on FDU Others201603181430 Helen)

New 03/18/16 - The date of the plan term should appear in the Effective date column - currently showing plan enrollment effective date (example on file: FDU Others201603181430 Grace)

New 3/18/16 – A change in election for the DFSA, FSA and HSA should show the change effective date instead of the original plan enrollment date. All other benefits seem to pick the changed effective date (example on file FDU Others201603181517 Helen)

Ganesh SadawartePlease check.

Hi Jennifer Leugers,

CC- Rohan J Khandave,Vinayak Kulkarni

We have done changes in template for above issues. We are done with compiling code for plan design health tier mapping and we are working on additional criteria for this.

We will update you 3/24 on this for additional criteria of PDHT.

We are working on below issue. .

Concern: Also for this record, two lines appeared, one with a participation code of “E” and one with a “W”. this record should only have one line with a W. the E line should drop. – RA - Still an issue, there are still two lines appearing with participation codes of “I” and “W”. Only the line with a W and a ~ in the Benefit plan column should appear. (Example on file: FDU Payroll201603181325 Grace)

Cause: As we are create two different templates one for waiver and other for other plans,Because the waiver need separate benefit plan code due to this two record exported on file.

Correction: As initial analysis we need code changes to handle this scenario and will share details analysis soon.

Concern: 03/18/16 New – Missing benefit plan code and Coverage code for ID Karyn, who newly added the benefit (should have had a benefit plan code and coverage code of “ES11”. See file: FDU Payroll201602261052

Cause: 2015 Non-Union 11 month mapping have eligibility criteria on benefit salary. Due this employee does not get any health tier please find attachment . According criteria benefit salary less than 32730 or benefit salary greter than 40242 but the employee salary is 35000.

Please refer last exported files which has full file.

Thanks,
Ganesh.

Hi all - why is this listed as resolved? Is the PDHT issue resolved?

_We will update you 3/24 on this for additional criteria of PDHT. _

Hi Hanmant Shinde,

CC- Prashant Samal

Can you please verify PDHT mapping as we move to another place. Prashant Samal has done code matrix complication. Please find below details.

Environment: Stage

Company: FDU Payroll For HSPL

Template:
1) FDU Payroll DP
2) FDU Payroll MED

Please let me know if you need details.

Thanks,
Ganesh.

typo correction in above comment: complication --> Compilation, Prashant Samal has done code matrix Compilation

Records verified, 8 records were missing the codes and the benefit coverage, as discussed with Ganesh, we identified the issue, and the missing codes are imported to system, will update as verification completes.

Hi Ganesh Sadawarte,

Test file exported from the group template is verified, all the records are exporting with proper Benefit Plan codes and Coverage codes as expected.

Random employees from each benefit types are verified along with those previous employees for which codes were missing, all the tested codes are correctly exporting.

Thanks.

Assigning back to Ganesh.

Jennifer Leugers

Hi Jennifer,

CC- Vinayak Kulkarni , Rohan J Khandave

We have move PDHT code to another place and also require customization changes for this are done to templates. Please refer last export file of _FDU Payroll goup tempate on FDU payroll.

Please let me know if you require more details.

Thanks,
Ganesh

Hi all - there were two pieces to this. Please see below on the still outstanding questions.

Good News, the “FDU Other” file looks good! I will be passing it off to the group to review formatting from their end and begin scenario testing. With this being said, in preparation for the group to start going into the stage site, I would like to update the names for the two FDU groups in stage. (change FDU Payroll to “FDU” and change the current “FDU” to “FDU OLD”)

Please let me know if this will cause any confusion on your end and if this is ok for me to do.

As for the FDU Medical payroll file. could you please clarify if all of the codes have been updated on the back end to move them off of PDHTM?

I’ve copied the current open items and placed them here to save on scrolling to find them, so the below are the current open items. Please let me know when we can expect the coding to be complete for #6.

FDU Medical Payroll file

Open Items:

Benefit plan waive (member is still in an active status) – See file named: FDU Payroll201602261319 – Jasmine was in the medical benefit and then waived coverage effective 2/5/16. The waiver line should show the two code columns (Benefit plan and coverage code) as blank.

Also for this record, two lines appeared, one with a participation code of “E” and one with a “W”. this record should only have one line with a W. the E line should drop. – RA - Still an issue, there are still two lines appearing with participation codes of “I” and “W”. Only the line with a W and a ~ in the Benefit plan column should appear. (Example on file: FDU Payroll201603181325 Grace)

03/18/16 & 04/05/16– Question – the last file you ran does not seem to be a full file as it seemed to only pick up waivers and didn’t show the full population with medical benefits. On the next test file, could you please provide a full file?

04/05/16 New– Previously worked – During an add with a Domestic Partner, the domestic partner is appearing with the incorrect Benefit plan code and coverage code. Example on file: FDU Payroll201604051435 Midge The file is pulling the regular coverage codes, not the DP coverage codes (CDUF12/CUF2 vs DPCS12/DPC2)

Please check

Hi Jennifer Leugers,

cc - Rohan J Khandave

We have checked for above mentioned points.

#1) Waiver Benefit plan and coverage code are blank in above file(FDU Payroll201604110336.csv) - For Jasmine.
#2) For this we need enhancement, we have already given 3c's dated 21/Mar/16 4:44 AM, This change is need more time to analyze and we will share analysis for the same.
#3) As you request for Full file, please refer last exported file(FDU Payroll201604110336.csv)
#4) We have made template customization for this, Now file is pulling correct DP coverage code.

With kind regards,
Rajendra Pawar

Hi all - any updates on #2?

Hi Jennifer Leugers,

CC- Rohan J Khandave

We have not schedule this yet we will include this in to next sprint which started from 4/25/2016. Please refer WT-41 for this enhancement.

Thanks,
Ganesh

Hi all - this was started yesterday? Do we have an ETA of completion?

Hello Jennifer Leugers,

This is major enhancement which will have an impact on entire rule engine implementation in export. So in this sprint we are doing only analysis for this. After analysis we will share efforts required for this for dave's approval.

Hello Jennifer Leugers,

We are doing analysis for new Rule Engine implementation.Below are few findings

1. Currently all Row wise , Column wise feeds internally has separate code routines for Rule Engine. As per our analysis we can merge these separate logic into common logic for all.

2. Also some fields like Enrollment Termination Date & Effective Date not null or equal to null conditions are not working. That fix is identified in current analysis.

CC – Satya

Hi all - any updates on this or any ETAs I can share with UHC?

Hello Jennifer Leugers,

Apologies for delay in response , We are close to finish our analysis for Rule Engine enhancement.

We will share detail ETA for same on Monday EOD.

Rohan J Khandave Please provide Dev efforts today and Hrishikesh Deshpande provide QA efforts.

No further delay.

Hello Jennifer Leugers,

For Rule Engine Enhancement 37 days are required for development , please find below details

1. UI Change to select DB Fields on Rule Engine : 3 days
2. CRUD operations (Insert , Update ,Delete) : 2 days
3. Make common logic Of Rule Engine for All : 7 days
4. Write business logic for DB fields : 15 days
5. Unit Testing : 10 days

CC-- Rakesh Roy Hrishikesh Deshpande

Hi all - when is the ETA for this to be in Local / Stage?

shyam sharma Satya Please check this and update.

Hey all - any update on an ETA?

All - really need an update on this. Have been asking for about two weeks.

All - this is getting pretty embarrassing. I haven't gotten an update on this item since May 24. My call with UHC is in two hours. Can anyone look into this ASAP?
Samir
Satya
Jaideep Vinchurkar
Rakesh Roy
Shubhankar Joshi

Hi Jennifer,

We have analyzed this and doing some customization changes to get this solved, Ganesh will update you on this ASAP
Ganesh Sadawarte Vinayak Kulkarni Rohan J Khandave

Hi Jennifer Leugers

CC- Rohan J Khandave,Vinayak Kulkarni

We have done customization for two lines appeared, one with a participation code of “E” and one with a “W”. this record should only have one line with a W. the E line should drop that remain from open items and Please refer last export file of _FDU Payroll goup tempate on. These file is full file.

We done these changes FDU company and verify that now the only one line is exporting per member. you check this for Jasmine. it exported Waiver line on file as expected.

Scenario that verified.

1) Plan Type Should Populate as per below code.

• UHC CDHP Medical and Delta Dental PPO = 11
• UHC POS Medical and Delta Dental PPO = 12
• Waive Medical and Dental Plan = 12

2) effective waiver line should show the two code columns (Benefit plan and coverage code) should as blank.

3) Waiver line Participation should always has "W"

4) If termination is exporting on file then Benefit Plan should is "~" and Coverage Code is blank.

5) if waiver termination is exporting then Participation is "W" other wise Participation is "I".

6) if effective election exporting for waiver then Participation is "W" other wise Participation is "E".

Please check and let us know if you need more details.

Thanks,
Ganesh

Hi all - reopening this per UHC's comments below. Please advise.

This is open item #3 on the open items list. I’ve tested in FDU STAGE with the global template: _FDU Payroll

The one last item that was open was in regards to a termination scenario where a member, who is still active, waives their coverage. The file is now showing the results as I expected for my test person, Mitchell Test. So for that particular issue, we can close it.

However, we now have new issues, which I’m not sure if are a result of development mapping the benefit and coverage codes outside of the PDHTM.

In my tests in the site, it does look like these codes are no longer looking to the PDHTM, but they are also not pulling the correct code. It looks like the people are all defaulting to a code of EE09. For instance, Randy Test is a Semi Monthly 12 person, whose salary is $50,000, and he is enrolled EE+DP in the POS plan. His Benefit plan code should be DPSP12 and his Coverage code should be DPS2. On the payroll file: FDU Payroll2016111111729, his codes are coming up EE09.

Could you please confirm if development completed this coding stop using the PDHTM? Also, would they be able to provide us with the key to their mapping just so that we can review their logic to understand it?

Hi Jennifer Leugers,

We checked employee Randy Test and he is enrolled into UHC POS Medical and Delta Dental PPO plan EE only so EE09 code is appearing on file. He has domestic partner but not enrolled in any benefit.

Please below attached snaps for more details

Also we tried by enrolling DP into medical plan and observed two records on file, one record is from Medical template and another from DP template as below.

NZB,randy,12/01/2016,12,DPSP09,E,DPS9,M
NZB,randy,12/01/2016,10,DPSP09,E,DPS9,M,,

Please let us know if any concern.

With kind regards,
Rajendra Pawar
----------------------------------------------------------------------------------------
Rohan J Khandave Vinayak Kulkarni Ganesh Sadawarte

Since he is in a Semi Monthly 12 payroll schedule, I am expecting the following for Randy Test:

POS plan EE Only – Benefit code: EEONLY Coverage Code: EE12

If he enrolled his domestic partner, I would expect the following 2 lines:

POS plan EE + DP

Benefit Code: DPSP12 Coverage Code: DPS2

Benefit code: EEONLY Coverage Code: EE12

Hi Jennifer,

Our specific logic for FDU to fetch Benefit Code and Coverage code was overwritten by generic logic, that is why you had wrong codes to Randy test.

Now, we have corrected the logic and taken appropriate steps so that it wont overwrite in future.

We have got below result after correcting logic

with-out DP enrollment
POS plan EE Only – Benefit code: EEONLY Coverage Code: EE12

with DP

Benefit Code: DPSP12 Coverage Code: DPS2
Benefit code: EESPSE Coverage Code: ES12

Note: As per your comment, for second line it should be EEONLY and EE12 but as per the code sheet given by UHC it should be EESPSE and ES12, see below snap from code sheet given by UHC

I ran a quick test for the other codes and it looks like the codes for the 11 month people are not appearing on the files. The codes for the other payroll schedules seem to be appearing fine.

For instance, on the file that I ran on 12/6 at 10:26, all of the people with 11 months payroll schedules are blank:

Hi Jennifer,

All of given 11 month people have payroll-schedule that is expired and ended last year.
there are two 11 month payroll schedule defined on FDU

1] Semi-Monthly 11 Month ( 01/01/2013 - 12/31/2014 )
2] Semi Monthly 11 Month ( 01/01/2015 - 12/31/2020 )

Codes for first payroll schedule are not configured at back-end at it is not active and given 11 month people belongs to it. Find below snaps.

employee's payroll schedule

company's payroll schedules

Additional questions from UHC

I have a few items for the FDU Medical Payroll file. The group is getting very motivated on getting this file in production, so I’m crossing my fingers that 2017 is the year that we’ll finally get this off the open items list.

Do you know when the 11 month codes will be mapped to the connection?

In regards to the Domestic Partner logic - I’ve heard back from the client and they let me know that they no longer accept Domestic Partners, so we don’t need to do any further coding on the Domestic Partner piece.

As mentioned previously, the additional eligibility criteria changes every year on November 16th. I’ve made the updates to the medical payroll coding document (please see the second tab - column H for the updated numbers). Could you please have these updated effective 11/16/16?

Would we be able to get the FDU stage client refreshed so that we have all of the new 2017 plans, rates and membership to assist with scenario testing? Please ensure that the payroll connections and any of your back end logic is not updated so that we don’t lose any of the work done up to this point on the payroll connections.

Hi Jennifer, Please see below inline comments

Do you know when the 11 month codes will be mapped to the connection?
Dev Comments: 11 months code are already mapped and added at back-end. Its just there are two 11 month payroll schedules available on company

1] Semi-Monthly 11 Month ( 01/01/2013 - 12/31/2014 ) ( no codes are added for this as this is expired)
2] Semi Monthly 11 Month ( 01/01/2015 - 12/31/2020 ) ( codes are present for this )

In regards to the Domestic Partner logic - I’ve heard back from the client and they let me know that they no longer accept Domestic Partners, so we don’t need to do any further coding on the Domestic Partner piece.
Dev Comments:
Okay, there are two company level templates consists group FDU payroll file

1] FDU Payroll MED
2] FDU Payroll DP - this is for domestic partners, we can remove this from group.

As mentioned previously, the additional eligibility criteria changes every year on November 16th. I’ve made the updates to the medical payroll coding document (please see the second tab - column H for the updated numbers). Could you please have these updated effective 11/16/16?
Dev comments: We could not see updated document, Provide us updated document

Would we be able to get the FDU stage client refreshed so that we have all of the new 2017 plans, rates and membership to assist with scenario testing? Please ensure that the payroll connections and any of your back end logic is not updated so that we don’t lose any of the work done up to this point on the payroll connections.
Dev commment:
Yes, we will work on this and we will update you once this is done.

Hi Ashwin,

Can you overwrite/refresh stage FDU by Production one as requested by Jennifer in above comments.

We have taken back-up of existing one to restore export logic on refreshed copy. Let us know if you have any questions on this.

Hi Vinayak Kulkarni,
FDU stage Database has been overwritten with production.

Ashwin Wankhede,Rajendra Pawar

Hi Jennifer Leugers,

We have refreshed stage FDU by Production copy, all payroll connections and its back-end logic for is kept as it is.

Please note that, for new 2017 plans, there are no codes added in system, provide us codes for new plans so that we can add it. Check our above comments for other details. Thanks.

I’m verifying DP logic that was called out below with the client, so I’ll let you know when they come back with a response, I’m pretty sure the logic is correct as it, but just want to double check.

However, I ran a quick test for the other codes and it looks like the codes for the 11 month people are not appearing on the files. The codes for the other payroll schedules seem to be appearing fine.

Hi Jennifer,

All of given 11 month people have payroll-schedule that is expired and ended last year.

There are two 11 month payroll schedule defined on FDU

1] Semi-Monthly 11 Month ( 01/01/2013 - 12/31/2014 ) - All given people are from this payroll schedule and this has ended in 2014 only. There are no codes configured for this payroll schedule.

2] Semi Monthly 11 Month ( 01/01/2015 - 12/31/2020 ) - Codes are configured for this, but given employees do not belongs to this schedule.

Note: Now, as stage FDU is refreshed by production copy, these test people do not exists. Thanks.

I ran a test on the FDU Medical payroll codes in the FDU Stage client. The 11 month codes are now populating.

However, I noticed the following that will need adjustments

Plan Type – showing 41 or 1 for records. These plan types are invalid, the only plan types should be 12 for the POS plan and 11 for the CDHP plan

The Semimonthly 9, EE only, sliding scale codes are incorrect – showing benefit code EE09, coverage code EE09 and it should be Benefit code SS09 and Coverage code SS09 (Please see file FDU Payroll201612280647_59124768182.csv EE ID# 113, 117 &121)

The coverage and benefit code for EC11 has an extra space after it, please remove the extra space.

I’ve attached the file parameters for the new sliding scale

Hi Jennifer,

All given 3 issues are resolved, Please find below details.

Concern:
Plan Type – showing 41 or 1 for records. These plan types are invalid, the only plan types should be 12 for the POS plan and 11 for the CDHP plan

Dev Comments:
Data transformation values were not updated properly against plans which caused this issue. We have updated Data transformation and now values are populating correctly.

Concern:
The Semimonthly 9, EE only, sliding scale codes are incorrect – showing benefit code EE09, coverage code EE09 and it should be Benefit code SS09 and Coverage code SS09 (Please see file FDU Payroll201612280647_59124768182.csv EE ID# 113, 117 &121)

Dev Comments
There was a problem in code logic to fetch out codes on file. We have updated code logic to fetch out proper codes We have also removed extra space for coverage and benefit code for EC11. Thanks.

Please check now, Please let us know if you have any questions on this.

Hi Pallavi Kulkarni Prashant Samal

Can we verify latest deduction code and check if we need to update existing one?

Yes Vinayak Kulkarni, we are on it..!

@@ Yogita Bhadane:

As discussed please start working on this:
PFA :
Old and New Codes Comparison.xls
FDU_Backend - Plan Class Tier Codes.xls

We will verify the changes any if found once you are done.

Thanks,
Prashant.

-------------------------------
Mandar Kulkarni

Hi Prashant Samal,

This is done. Please verify it.

PFA:
FDU - Codes ID'S Sheet_Effective_16

Thanks,
Yogita Bhadane

CC:- Mandar Kulkarni,Vinayak Kulkarni

I am trying to test the payroll export, however I’m receiving an error message. Please let me know when this has been resolved so that I can continue testing.

Hi Jennifer Leugers,

below are the 3C's,

Concern : Getting server error while exporting group template.

Cause : There was code issue, Fix has been deployed under Jira (WT-7474).

Correction : Fix has been deployed, Now feed is exporting without error.

Please check and confirm.

With kind regards,
Rajendra Pawar
-----------------------------------------------------
Rohan J Khandave Vinayak Kulkarni Ganesh Sadawarte

Please see below from UHC and advise

I was able to import review the codes and I was able to test the last updates, which are good. In running my test however, I noticed a new item:

There were some people who had an overage dependent, and as such, their dependent was terminated. It looks like on the file, the codes are showing blank.

And I have two questions:

Would we be able to get the FDU stage client refreshed so that we have all of the updated membership to assist with scenario testing? The client is having a hard time with testing since the last refresh was done 2 months ago. Please ensure that the payroll connections and any of your back end logic is not updated so that we don’t lose any of the work done up to this point on the payroll connections.

Could you please confirm that the sliding scale salaries have been updated in the back end coding? I believe that they were, but just wanted to get confirmation. (column H on the attached FDU medical payroll structure)

Hi Jennifer,

Please see below details.

Concern: Few overage dependent enrollments are getting blank codes

Cause: We had recently refreshed back-end codes with new conditions for salaries and while doing that there was a issue happened for records which do not have salary conditions and these are the such records, due to which they populated with blank code.

Correction: We have corrected this issue on Stage FDU. Please check.

Answer to question 1:
Yes, we can do that, however that would be done by end of next week. We will let you know once it is done.

Answer to question 2: Yes, it is updated.

Let us know if you need more information on this, Thanks.

Hi Khandu Kshirsagar and Ashwin Wankhede

Can we get Stage FDU refreshed with production copy?

Hi Prasad Pise,

We have moved "FDU" company from production to stage by overwriting their current copy.
Please check the below mentioned points for the moved company:

1. Make proper company module mapping
2. Save EDS and theme
3. Log in to the site with Partner/Broker/Employee role and make sure all pages are displayed

Please let me know if you need any information related to this, or any errors.

Attaching Company migration checklist used in migration with mail. WT-895_Company Migration Production To Stage.xls
QA Testing is in Progress.
CC: Vijay Siddha,Samir,Satya,shyam sharma,Ashwin Wankhede,Rakesh Roy,Indraprakash Tiwari

Hi Rajendra Pawar and Prajakta Belhe , Please work on this and get export setup done on refreshed FDU company.

For company move testing, I have created new ticket WT-8559 and assigned to Jayshree.

CC: Prajakta Belhe

Hi Jennifer Leugers

Stage FDU is refreshed with Production copy, also all export work done on stage is retained. Please check, Thanks.