Hi @suraj,
Could you please check this? Thanks.

---------------------------------------------------------------
CC: Vijay Siddha, Satya, Jaideep Vinchurkar

Hi Cindy Wibbing ,

With initial analysis, Please find below observations,

• For Beneficiary Imports, followings fields are mandatory

1. Employee SSN
2. Beneficiary First Name
3. Beneficiary Last Name
4. Beneficiary Date of Birth
5. Beneficiary Relationship
6. Beneficiary Old plan design identifier
7. Beneficiary Type

• We are able to import files with Beneficiary Date of Birth , please referred following customization
  

• We have even tried with "Test Ben Trust" file import but its goes to bad.

Please let us know if you have any query.

Thanks !

Hi Cindy Wibbing,

This is because of Implementation of unique fields for dependent Import in which "Dependent Date of Birth" was marked as Unique and Mandatory. Please ref "WT-7755 Dependent Import - Validation For unique fields" for more details.

We need to take this as a new change request so Please suggest the same.

Thanks !

CC : Amit Thorve Vijay Siddha Satya Jaideep Vinchurkar Suraj Sokasane

Vishal Bajad This is not a dependent import. This is beneficiary import and DOB should not be mandatory for the same.

I don't know how this will be treated as new change. While making code changes in ticket no. WT-7755 the beneficiary import should have been excluded from mandatory checks.

CC-Abhay Patil, Jennifer Leugers, Nick,Vijay Siddha,Cindy Wibbing

Vishal Bajad - can you please take it ahead as a bug? This is NOT a change request. CC Satya Vijay Siddha

Hi Abhay Patil,

We will plan this bug in next week.

Hi ,

This issue has been resolved and its pending for code review. it will get deployed with next deployment patch once we done with code review.

Thanks !

Hi Vishal Bajad,

Verified on Lb
Company - QA City of Durham

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" beneficiary.
2)Not given Date of birth in beneficiary template - File wents to bad - "Dependent Date of birth is required" for beneficiary "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , it must be marked unique - Import done successfully
4)For Business associate and Others, Date of birth given in file is shown in beneficiary page.and for Trust it has no DOB

Working fine as expected.

Marking item state as Ready for stage

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise

Verified on Stage
Company - city of bellevue for hspl

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" beneficiary.
2)Not given Date of birth in beneficiary template - File wents to bad - "Dependent Date of birth is required" for beneficiary "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , it must be marked unique - Import done successfully
4)For Business associate and Others, Date of birth given in file is shown in beneficiary page.and for Trust it has no DOB

Working fine as expected.
Marking item state as Ready for Prouduction

Jayshree Nagpure
Per your notes it looks like you are still making DOB a required field for Beneficiary loads. Can you please verify that this is not a required field for a beneficiary load. The spouse and child records are independent and have to be loaded in the Spouse and Child table.

Per Amit's remarks the requirement should not be on the Beneficiary load.

cc Amit Thorve

Jayshree Nagpure
Can you please make sure the change is made to not make the Date of Birth mandatory for all beneficiary types.
Thanks!
Cindy

Jayshree Nagpure and Jaideep Vinchurkar This DOB should not be mandatory for any Beneficiary Type.

Please feasibility of this request.
If we remove DOB from all types beneficiary, it should not allow, spouse and children as beneficiery that are not present in system

Hi Jaideep Vinchurkar
We do not want the DOB to be mandatory on the Spouse or Child Relationships either. They should already be in the Spouse or Child tables in the Spouse Load or the Child Load.

cc Amit Thorve

Jaideep Vinchurkar I dont know what you are talking here.

If the spouse or child is not exists in the system and when we add them as beneficiary are they getting added in the Employee_DependentSpouse/Employee_DependentChild tables?

Can we discuss this on call?

Hi,
Do we have any update on the status?
White Label asking for timeframe.
Thanks!
Cindy

We are done with code changes. By today end of the day the change will go on local test environment. QA will update with stage and production dates.
Amit Thorve and Cindy Wibbing: Previously we were having a bug in system, where import is allowing beneficiary as spouse or child but there was no check of their existence in system. i.e. a spouse beneficiary can added though he/she not present in system. In My above comments, I just want make Vishal Bajad aware of this issue, so that his code fix should introduce this issue again. my comments were only meant for developer.

verified on LB
Company - city of durham

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" , "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , its uniqueness has been removed - not necessary to mark DOB field unique(Without uniqueness import is done successful)
4)For Trust","Business associate", and "Other" ,"Domestic partner","Employee","Friend","Other Relative","Parents","Sibling" - Date of birth is inserted in beneficiary page.
5)If spouse/child no exists in system - file wents to bad with proper error message("No such child/spouse exists")

Working fine as expected
Marking item state as ready for stage

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise

verified on Stage
Company - city of bellevue for hspl

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" , "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , its uniqueness has been removed - not necessary to mark DOB field unique(Without uniqueness import is done successful)
4)For Trust","Business associate", and "Other" ,"Domestic partner","Employee","Friend","Other Relative","Parents","Sibling" - Date of birth is inserted in beneficiary page.
5)If spouse/child no exists in system - file wents to bad with proper error message("No such child/spouse exists")

Working fine as expected
Marking item state as ready for Production

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise

Jayshree Nagpure Can you please check the attached.
White Label BCC tried import but states it is not working. See comment from BCC
Attached is the import file.

"I have the group “Quincy” in stage, and I’ve created the import template “Bene Import” which has the birth date field mapped, but is not set up to be a unique field (so that it can be left null). I checked the Beneficiary form for the group, and Date of Birth is editable, and I can manually add a beneficiary with no Date of Birth. In the attached file (password via email), I get a server error when I try to import these records using the “Bene Import” function, but if I put fake dates of birth in the same records, they load with no problem."

Hi Cindy Wibbing ,

Please find below 3C's ,
Concern : Import failed for Null Replacement character.
Cause : This is because of failed to check for null replacement character.
Correction: We have provided code fix and its will deployed on LB with deployment patch.
Work around : Please remove date of birth field from template if not required or provide any default date value in import file.

Thanks !

Verified on LB
Company - Wheaton

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" , "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , its uniqueness has been removed - not necessary to mark DOB field unique(Without uniqueness import is done successful)
4)For Trust","Business associate", and "Other" ,"Domestic partner","Employee","Friend","Other Relative","Parents","Sibling" - Date of birth is inserted in beneficiary page.
5)If spouse/child no exists in system - file wents to bad with proper error message("No such child/spouse exists")
6)When DOB is mapped but not given in File or given as "~" - Import done successfully
7)For Unique DOB field - Import done successfullu
8)For Uniquee DOB Field - DOB is blank(File wents to bad)

Working fine as expected,
Marking item state as Ready for stage

Thanks,
JAyshree

cc : Rakesh Roy Prasad Pise

Verified on Stage
Company - Asml for hspl

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" , "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , its uniqueness has been removed - not necessary to mark DOB field unique(Without uniqueness import is done successful)
4)For Trust","Business associate", and "Other" ,"Domestic partner","Employee","Friend","Other Relative","Parents","Sibling" - Date of birth is inserted in beneficiary page.
5)If spouse/child no exists in system - file wents to bad with proper error message("No such child/spouse exists")
6)When DOB is mapped but not given in File or given as "~" - Import done successfully
7)For Unique DOB field - Import done successfully
8)For Unique DOB Field - DOB is blank(File wents to bad)

Marking item state as Ready for Production

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise

Verified on Production
Company - Asml for hspl

Verified below scenario for beneficiary import :
1)Not given Date of birth in beneficiary template - Import is done successfully for "Trust","Business associate", and "Other" , "Spouse","Child","Domestic partner","Employee","Friend","Other Relative","Parents","Sibling"
3)When DOB is given for spouse, child etc , its uniqueness has been removed - not necessary to mark DOB field unique(Without uniqueness import is done successful)
4)For Trust","Business associate", and "Other" ,"Domestic partner","Employee","Friend","Other Relative","Parents","Sibling" - Date of birth is inserted in beneficiary page.
5)If spouse/child no exists in system - file wents to bad with proper error message("No such child/spouse exists")
6)When DOB is mapped but not given in File or given as "~" - Import done successfully
7)For Unique DOB field - Import done successfully
8)For Unique DOB Field - DOB is blank(File wents to bad)

Marking item state as Production complete

Thanks,
Jayshree

Hi Jayshree Nagpure
Were you able to test with the attached zip file on Quincy in Stage?
Just need to know so I can let BCC know whether we tested the file or not.
Thanks!
Cindy

Hi Cindy Wibbing,

Yes, We tested the attached zip file on Quincy for hspl on stage.
Import done successfully -
Also verified on beneficiary page

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise Vishal Bajad