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

Example of Loading Participant Enrollments

Use the Participant Enrollment business object to enroll participants into a benefit offering in bulk.

Considerations

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

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

  • You can create records using Participant Enrollment HCM Data Loader. You can't update or delete records.

  • In order to update a record, de-enroll the participant first and then re-enroll the participant with the new value. Refer to the example ParticipantEnrollment.dat files provided in this topic to de-enroll and re-enroll a participant.

Preparing to Load Participant Enrollment Object

Before you can load participant 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.

Generating the .dat File

This example ParticipantEnrollment.dat file enrolls a participant into a benefits program. 

METADATA|ParticipantEnrollment|PersonNumber|ParticipantLastName|ParticipantFirstName|BenefitRelationship|LifeEvent|LifeEventOccuredDate|EffectiveDate
MERGE|ParticipantEnrollment|10026712115|Duprey|Luis|Default|NewHire|2016/10/28|2016/11/05
METADATA|CompensationObject|Program|OriginalEnrollmentDate|PersonNumber|LineNumber
MERGE|CompensationObject|Green Company Full Benefits|2014/10/28|10026712115|1
Note: It is not necessary to supply the ParticipantLastName and ParticipantFirstName attributes. The application does not perform any validation to cross check the name against the person number. These attributes are for provided only for your information.

De-enrolling from an Existing Option in the Plan and Enrolling in a Waive Option

You can de-enroll employees from a plan and enroll them into the waive option of same plan type. For instance, consider an employee who is enrolled in the Healthy HMO plan with the Employee Plus Family option. You can de-enroll the employee from the Employee Plus Family option and enroll the employee in the Waive Coverage option using the following example ParticipantEnrollment.dat file.

METADATA|ParticipantEnrollment|PersonNumber|ParticipantLastName|ParticipantFirstName|BenefitRelationship|LifeEvent|LifeEventOccuredDate|EffectiveDate
MERGE|ParticipantEnrollment|10026712115|Duprey|Luis|Default|Gain Dependent|2016/10/28|2016/10/28
METADATA|CompensationObject|Plan|Program|Option|OriginalEnrollmentDate|PersonNumber|DenrollPlan|DenrollOption|LineNumber
MERGE|CompensationObject|Healthy HMO|Healthy Benefits|Waive Coverage|2016/10/28|10026712115|Healthy HMO|Employee plus Family|1