Missing BEN_PROG_PARTIC Record (Doc ID 609092.1)

Last updated on NOVEMBER 11, 2024

Applies to:

Symptoms

Compilation of information regarding the PS_BEN_PROG_PARTIC record and its impact on PayCalc & Dedcalc processing.

The most common cause of a large number of employees who previously had been having deductions taken properly and then all of a sudden not having any taken, or having only one type (Benefit or General) of deduction taken and the other type not taken is due to a missing PS_BEN_PROG_PARTIC record.

One cause for Payroll to have a  missing BEN_PROG_PARTIC record can be from reprocessing a hire in BenAdmin from Final Enroll and then running payroll.  Another can be from changing employees to a new Benefit Program and missing an employee or two, or possibly from just accidentally deleting an employee's BEN_PROG_PARTIC record.  The result is that there is NO entry in the table for that employee(s), which will cause both Payroll and Payroll Interface to misprocess the employee's deductions, as well as massive skipping of records.

Certain circumstances will cause COBOL to misfire.  In one case, a basic life benefit legitimate for full time employees.  Procedurally, when a full time employee goes to part-time and loses certain benefits, the user has been going in to the benefit participation record in Correction mode and changing the date of the benefit, as opposed to adding a new row.  Consequently, benefit date and benefit program date have fallen out of sync.  This employee should have had two BEN_PROG_PARTIC  records, but only had one.  This caused hundreds of employees following this employee not to calculate. 

Cause

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