1. HCM Data Loading Business Objects
  2. Example of Loading Dependent Enrollments

Example of Loading Dependent Enrollments

Use the Dependent Enrollment business object to designate dependents of multiple employees into a benefit offering.

You typically perform this task when you are migrating from a legacy system during a merger or acquisition. You can also use the data loader if you want to move dependents in bulk from one plan to another.

Considerations

You must consider the following points before you load dependent enrollment.

  • You can load the Dependent Enrollment object using either the default benefits relationship or the unrestricted benefits relationship. However, you cannot use both relationships simultaneously.

  • You can create and update records using Dependent Enrollment HCM Data Loader. You can't delete records.

  • Dependent Enrollment processing does not depend on Effective date, but on Life Event date.

Preparing to Load Dependent Enrollment Object

Before you can load dependent enrollment, you must:

  • Verify that the data required for enrollment such as employee name, address, salary, and contact details are available in the HR application. It might be difficult to verify errors in HR data after the upload.

  • Ensure that you do not include certifications when you are migrating data from a legacy system. This might cause completed enrollments to be suspended again. Avoiding certifications also improves performance and reduces pending action items.

  • Determine the number of unique employees and the total number of enrollments that you plan to load into the application. You can obtain this information from the extracted source data.

  • Ensure that the total payout percentage assigned to the beneficiaries add up to 100%. Both primary and contingent beneficiaries must have 100% assigned to them.

  • Create electable choices on the basis of eligibility rules. To verify whether your electable choices follow eligibility rules, use random checks based on eligibility criteria.

  • Create benefits relationships for all the employees whose data you want to load.

  • Ensure that the benefit relationships are properly aligned with the hire and assignment dates. For instance, the date on which the life event is processed must follow benefit relationship date, and the benefit relationship date must be the same as or follow the hire date.

  • Verify that the total number of potential life events is equal to the total number of employees whose data you want to upload. In the Evaluation and Reporting work area, Processes tab, use the Assign Corrective Life Event process to create the data related to potential life events.

  • Run the participation evaluation process without applying the defaults and ensure that the number of started events match with the number of employees you determined in the previous task. You must fix any errors you encounter at this stage.

  • Ensure that values are not added to the CloseLifeEvent attributes in the .dat file. You must first verify the enrollment data and then use the Close Life Event process to close a life event.

Generate the .dat File

This example DependentEnrollment.dat file designates a dependent into a benefits program.

METADATA|DependentEnrollment|PersonNumber|BenefitRelationship|EffectiveDate|LifeEvent|LifeEventOccuredDate
MERGE|DependentEnrollment|10026712115|Default|2016/10/28|NewHire|2016/10/28
METADATA|DesignateDependent|Plan|Program|Option|DependentPersonNumber|LineNumber|PersonNumber
MERGE|DesignateDependent|GlobalPlan|Green Company Full Benefits|Employee plus Family|100010026713030|1|10026712115