Monitoring Services: Enrollment Coverage and/or Rate Overrides Exist Where No Thru Date Value Is Specified (Doc ID 2430214.1)

Last updated on SEPTEMBER 27, 2023

Applies to:

Symptoms

This issue is handled via Monitoring Services.

The basic concept of Monitoring Service is the ability to define and periodically look for events (faults, issues, availability) in customer instances and, as needed, when an event occurs, create / update a Service Request with a well-defined problem statement, the diagnostics collected and steps defined for the engineer to easily solve the issue.

Various issues may occur when a participant benefit enrollment record has been overridden and no value has been specified for the "Thru" date.

Some examples are listed below:

     A) The Open life event is processed for an employee but the correct rate is not displaying the new value for the new plan year.

     B) Previously overridden enrollment rate with Thru value of 01-AUG-XX does not revert back to originally generated rate value prior to override.

In scenario (A), the override will not end after processing a life event unless a "Thru " date value is specified.

     It is recommended to enter a "Thru" value at the time of overriding the enrollment.

     For example, if for a legitimate reason a value is overridden at the beginning of the plan year (01-JAN), a Thru date of 31-DEC is used. This will ensure that a new rate will populate for thee next annual enrollment.

     If the Thru Date field is left blank then the system will use the enrollment override data until the end of time, which may be desired in some cases.

For scenario (B), within Oracle Advanced Benefits (OAB) and Oracle Standard Benefits (OSB), enrollments do not change unless a life event or an unrestricted event is processed for a person.

     When you make an enrollment override, you are correcting the enrollment information for the latest life event to have processed.

     The enrollment override information will remain in effect until a subsequent life event is processed with an occurred on date that is AFTER the enrollment override "Thru" date.

     Entering the "Thru" date alone will not end the overridden value. In this case, an event must be process on or after 02-AUG of the same year before the rates will be updated to the system calculated amount.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.