Oracle HRMS delivers seeded life event reasons you can use for benefits administration. Seeded life event reasons are pre-defined; you can re-name them but they cannot be otherwise modified or deleted. You do not set up person changes for seeded life event reasons as you do with user defined life event reasons.
You link seeded life event reasons to your plan design just like user defined life event reasons, or you can include a seeded life event reason as a parameter when you run either of the following batch processes to manage life events:
Participation Process: Life Event
Participation Process: Temporal
For example, you could run the Temporal Participation Process to detect changes in age that might make a person age into a savings plan or age out of a medical plan. In this example, you would select the seeded life event reason Age Changed as a parameter when you run the process from the Concurrent Manager.
See: Life Event Usage
The following is a description of the life event reasons that are seeded with Oracle HRMS:
Administrative: Assign the administrative life event reason to a person or group of persons when the terms and conditions of a benefit plan change significantly and participants must be allowed to re-evaluate their elections. Examples of administrative life events include renegotiation of contract rates or addition of a new benefit
Open Enrollment: Use the Open life event reason to determine eligibility for an open enrollment period. Open enrollments typically occur at recurring scheduled periods, such as an annual health and welfare benefits enrollment or a quarterly savings plan enrollment.
Unrestricted: The unrestricted life event reason is used for benefit enrollments that are not time-dependent, such as a savings plan.
When you run the Participation Process in Scheduled mode from the Concurrent Manager, and select the enrollment period start date, the system creates a life event with a status of Detected for each person who meets the batch process criteria.
When you run the Participation Process in scheduled, life event, or temporal mode, the system creates a life event when the minimum or maximum boundary is crossed as specified in the definition you create for the applicable derived factor. The seeded life event reasons for temporally derived factors are:
Age Changed
Combined Age and Length of Service Changed
Compensation Changed
Hours Worked in Period Changed
Length of Service Changed
Total Percent Full Time Changed
You implement temporally based life events by creating the derived factor, including the derived factor in an eligibility profile or variable rate profile, and linking the profile to a compensation object.
See: Derived Factors
The seeded life event reasons for COBRA are used to determine ineligibility or enrollment period change for COBRA benefits. COBRA life event reasons should be associated with programs or plans subject to COBRA regulations.
Loss of Eligibility: This seeded life event reason detects when a COBRA enrollment period has passed.
Maximum Period of Enrollment Reached: This seeded life event reason detects when a COBRA participant is to be de-enrolled due to reaching the maximum period of enrollment, which can vary based on subsequent life events that occur during COBRA coverage, such as a divorce or qualifying disability.
Non or Late Payment: This seeded life event reason detects when a COBRA participant's payment is delinquent or late based on the participant's enrollment start date and the COBRA Payment due date. The initial payment is granted a 45 day grace period.
Voluntary End of Coverage: This seeded life event reason detects when the participant's COBRA participation has been voluntarily ended. This indicates that the COBRA eligibility end date has been reached as recorded in the COBRA Beneficiaries window with an ineligible reason of Voluntary End of Coverage.
Period of Enrollment Changed: This seeded life event is created when a person's COBRA eligibility end date is changed. For example, this could occur for a participant who is initially eligible for 18 months of COBRA coverage who becomes disabled during the first 60 days of coverage. The participant's enrollment period is changed to 29 months and the COBRA eligibility period end date is changed accordingly.
Enrollment Override: Use this seeded life event reason when you employ the Participation Overrides window or the Enrollment Override window to make a person eligible or ineligible for a benefit, or for enrollment or de-enrollment.
Quartile in Grade: This seeded life event is created by the system when a change in a person's grade, salary basis, or salary moves them into a new quartile in grade. These conditions trigger the Quartile in Grade life event if the BEN: Enable Quartile in Grade Life Event user profile option is set to Yes. If you set this profile option to No, the system never creates a Quartile in Grade potential life event.
Reduction of Hours: This seeded life event reason is used when a reduction in hours causes a person to experience a change in benefits status, such as becoming eligible or ineligible for a benefit.
Satisfied Waiting Period: This seeded life event is created by the system when a person experiences a life event but has not yet satisfied the waiting period for the benefit and is therefore not eligible. The life event is created with the occurred on date equal to the date the person satisfied the waiting period. The life event is given a status of potential until the waiting period completion date is reached.
Added During Enrollment: This seeded life event is used by Self- Service Benefits enrollment to prevent a life event from occurring when you create a family member or update a family member's details. You can define a gain dependentlife event reason if you want to trigger a life event based on a family member change in Self-Service.