Enrolling Employees Using Overrides

Use enrollment overrides when you need to waive eligibility requirements for particular employees. For example, if an organization acquires another company, the acquisition plan might stipulate that you waive the benefits eligibility requirements for the employees in the acquired company. You can use enrollment overrides to enroll these employees in plans for which they would not typically meet the eligibility requirements.

The Enrollment Overrides form includes these date fields, which enable you to review and record the dates that are associated with employee enrollment:

  • Begin Date

  • Ending Date

  • Eligible Date

  • Participation Date

  • DBA Begin Date (deduction, benefit, accrual begin date)

  • DBA End Date

  • User Def Date (user-defined date)

Because the reasons for overriding existing eligibility requirements differ by organization, you can use the User Def Date field to record date information that is specific to the organization's business needs. For example, the organization might track the date on which the employee was hired when overriding eligibility. Or, it might track the date on which an employee would have been eligible for the benefit if the eligibility requirement had not been overridden.

You can use vocabulary overrides to rename this field with a name that fits the organization's needs. For example, you might change the name of the User Def Date field to the Hire Date field or the True Eligibility Date field. You can use this field to track any date that you want to associate with an employee's benefit enrollment.

See " Setting Up Category Codes for DBAs" in the JD Edwards EnterpriseOne Applications Human Capital Management Fundamentals Implementation Guide.

SeeJD Edwards EnterpriseOne Tools Foundation Guide.