Multiple Jobs Functionality is not Considered for COBRA and Benefits Billing (Doc ID 620181.1)

Last updated on APRIL 08, 2015

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 8.8 SP1 and later
Information in this document applies to any platform.

Symptoms

  When the employee has a Cobra event that is not associated to the primary job, the COBRA event goes to Not Cobra qualified.  If there is an event for the employee who has mulitple jobs, where both jobs are associated to one benefit record, the event will not qualify.  For event where there is only one job or ben primary job equal to Empl record 0, it works fine. Typically the event associate to the non-primary job should not qualify in the case of a termination perhaps.  However, the event which should qualify due to loss of coverage in the event of a divorce, the correct empl record is carried over but it does not qualify.

Scenario:  Employee is hired effective 4/1/2000 to secondary job with Empl Rcd 1. Employee is then terminated effective 5/5/2000 from Empl Rcd 0.  Both Empl Rcd 0 and Empl Rcd 1 have Benefit record 0.  Employee then gets Divorced effective 6/10/2000. FSC Event is entered into the Bas Activity table for the employee using Empl Rcd 1. Run process through Ben Admin, the Event and eligibility information shows an Empl Rcd 1.  Next, run COBRA process and event goes to Closed and Not Qualified for Empl Rcd 1.  If a sql update is done to change the Empl Rcd from 1 to 0 on the COBRA Event Table, and reprocess the DIV event that now has an Empl Rcd 0, the Event now goes to Qualified.

Scenario:  Employee is hired effective 4/1/2000 to secondary job with Empl Rcd 1. Employee is then terminated effective 5/5/2000 from Empl Rcd 0.  Both Empl Rcd 0 and Empl Rcd 1 have Benefit record 0.  Employee then gets Divorced effective 6/10/2000. FSC Event is entered into the Bas Activity table for the employee using Empl Rcd 1. Run process through Ben Admin, the Event and eligibility information shows an Empl Rcd 1.  Next, run COBRA process and event goes to Closed and Not Qualified for Empl Rcd 1.  If a sql update is done to change the Empl Rcd from 1 to 0 on the COBRA Event Table, and reprocess the DIV event that now has an Empl Rcd 0, the Event now goes to Qualified.

Workaround:  Although this is not supported, an update to the COBRA Event table to change the Empl record #1 to an Empl Record #0 will allow the event to qualify.  This is up to the customer to decide if they want to track dependent events i.e DIV, MAR by empl record.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms