If the Generate Salaries and Allowances (PAY290) job is stuck and the log file displays an error, it may be due to one of two reasons:
There are duplicates present in an underlying temporary table.
An employee has changed pay groups but has a timesheet in the old group.
To resolve these issues, we have compiled a list of steps.
Duplicates on the temporary table
There are duplicates present on an underlying temporary table. Retrieve the log file for this pay group.
If you see the following error in the log file for this pay group:
"P180a; ERROR inserting into TEMP_NON_TSHEET - CURRENT EMPNO (XXXXXXX/p180g) - ORA-00001: unique constraint (OPS$COREHR.TEMPNON) violated. p290.main; Close file PAYROLL_LOGFILE_PATH pay290.trcXXXX"
this indicates that there are duplicates in the temporary table. This situation can occur if users enter changes on the Portal multiple times or double-click the submit button. Please raise a new case online and reference the title of this article.
Changed pay groups
If an employee recently changed pay groups and had timesheets generated in the old group before the transition, the old pay group may still be open. In this case, the system may pick up the timesheet in the old group, causing the PAY290 job to fail.
To resolve this issue, follow these steps:
Delete the old timesheet from the old pay group.
Re-run the PAY290 job in the old group, then re-run it in the new group.