-
Type:
Support Activity
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Support Task Type:Configuration
-
Environment:Production
-
Reported by:Support
-
Company:Dakotaland
-
Module:BenAdmin - Export
-
Issue Importance:Must Have
-
Severity:Simple
Template: Lincoln_Financial_Life
Hello Development Team,
Can you update the macro Enrollment Lincoln Financial Coverage Indicator to data transform as follow for client, Dakotaland FCU. The spec requires the Cvgs fields format to pass on file as Coverage Code-Enrollment Approved Coverage Amount for example if someone enrolls in Supplemental Employee Life with approved amount $50,000 it should come out as OLI-50000. Below is their structure with crosswalk of the plans and codes.
Life plans and codes:
Basic AD&D = AD
Basic Dependent Life = DLI
Basic Life = LI
Long Term Disability = LTD
Short Term Disability = WI
Supplemental Child Life = OCLI
Supplemental Employee AD&D = OAD
Supplemental Employee AD&D - Over 65 = OAD
Supplemental Employee Life = OLI
Supplemental Employee Life - Over 65 = OLI
Supplemental Spouse AD&D = OSAD
Supplemental Spouse AD&D - Over 65 = OSAD
Supplemental Spouse Life = OSLI
Supplemental Spouse Life - Over 65 = OSLI
When I mapped to Enrollment Lincoln Financial Coverage Indicator, they would come out as VLI-amount for the supplemental employee life instead of the one from structure. Attached is the file spec and structure/crosswalk. Let me know if you need additional info.
Thank you,
Alex LFG EDI Enrollment File Spec v2.pdf
Life_Structure_Crosswalk.xlsx
Hi Alex Nguyen,
Thank you for your patience. We have updated the benefit type name for the following plans:
Supplemental EE Life => Optional Life
Supplemental Spouse Life => Optional Spouse Life
Supplemental Child Life => Optional Child Life
Supplemental EE Life Over 65 => Optional Life Over 65
Supplemental Spouse Life Over 65 => Optional Spouse Life Over 65
Please let me know if you have any questions
Thanks,
Robyn
CC Jennifer Mitchell, Monika Demla
Robyn Adkison (Inactive)
added a comment - Hi Alex Nguyen ,
Thank you for your patience. We have updated the benefit type name for the following plans:
Supplemental EE Life => Optional Life
Supplemental Spouse Life => Optional Spouse Life
Supplemental Child Life => Optional Child Life
Supplemental EE Life Over 65 => Optional Life Over 65
Supplemental Spouse Life Over 65 => Optional Spouse Life Over 65
Please let me know if you have any questions
Thanks,
Robyn
CC Jennifer Mitchell , Monika Demla Hi Robyn Adkison,
I will test them out later and will let you know if the macro is working properly. May need Development involve if the codes not coming out correctly after benefit type has been updated.
Thank you,
Alex
Hi Robyn Adkison,
You can go ahead and close out this ticket. We had a discussion with Amit and Vinayak regarding the existing Lincoln macro and found out it won't work with the Lincoln file I built due to the format being different than the Lincoln files they built for other clients. The Lincoln macro is passing the code/approved amount in the format I needed, but problem is it will pass all enrolled plans on 1 column with commas separating each. This will cause the data to appear out of order on my file.
I opened another ticket WT-12986. Their suggestion was to try selecting "Is Padding Required?" and "Do Not Apply Padding For Blank Value" under the sub template field settings that way if not enrolled in the plan, it will not pass the leading value on file. This took care of it. File is now scheduled to run weekly.
Thank you,
Alex
Thank you so much Alex Nguyenfor your help on this file.
CC: Jennifer Mitchell
Robyn Adkison (Inactive)
added a comment - Thank you so much Alex Nguyen for your help on this file.
CC: Jennifer Mitchell 
Hi Robyn Adkison,
Can you update the benefit type on the supplemental life plans? Development said the codes are already setup on the Lincoln macro. As long as the benefit type is correct in WT it should pass their codes on file. Please see Rakesh last comments.
Thank you,
Alex