If you run the Salaries and Allowances job while processing your payroll and the job fails with no timesheets generated, there a several reasons why this might occur.
We’ve compiled a list of possible causes and how to resolve them. Follow the steps below based on the identified cause.
Employee hours
Changes to the employee hours can cause failure. Look for the following error in the Pay290 log file:
"ERROR on retrieve_employee_details (S1200)
CURRENT EMPNO ([EMPNO]/p120j1 csr_hours_worked)
ORA-06502: PL/SQL: numeric or value error: number precision too large "
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
Search for ERROR within the file.This highlights the employee number causing the issue.
Check the employee in question to ensure the hours aren't too high or that the increment due date is a valid year.
Absence without pay
Changes made to absence without pay can cause failure. Look for the following error in the Pay290 log file:
"ERROR on percentage_calculation
CURRENT EMPNO ([EMPNO]/p640c temp transaction processed_ind N)
ORA-01476: divisor is equal to zero "
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
Search for ERROR within the file.This highlights the employee number causing the issue.
Ensure an absence without pay row has not been recorded with the same dates as a pension rate of pay salary row, if so this will cause the job to fall over.
Ensure that if this employee is on absence without pay that allowances that are adjusted Y are not ended otherwise will bring up error. ORA-01476: divisor is equal to zero.
Ensure that only one absence has been entered this period, otherwise this will cause job to fall over.
Data conflict
Data conflict on position_history can cause failure. Look for the following error in the Pay290 log file:
"RATE NOT FOUND FOR POSITION CODE/SCALE POINT: [POSITION]/[POINT] P912a -> ERROR get_rate_2120
CURRENT EMPNO ([EMPNO]/p212c rate matches employee's rate)
ORA-01403: no data found"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
Search for ERROR within the file.This highlights the employee number causing the issue.
There is a row(s) on personal_rate and position_history which are causing a conflict and there is no scale point set against the employee's Position Code. Then either
To delete the old historic rate for the employee, please raise a new case online and reference the title of this article and please include details of the employee affected.
A payroll user will need to record a scale point against the position and then an analyst will need to update date_input on the employee's position to prevent arrears in this instance.
Please raise a new case online and reference the title of this article and please include details of the actions taken.
Re-run the PAY290 job.
Absence without pay records on temp_transaction
There are two open-ended absence without pay records on temp_transaction for one employee. This can cause failure. Look for the following error in the Pay290 log file:
"ERROR on calculate_absence_allowance
CURRENT EMPNO (EMPNO,p635prop standard value allowance
counter in 1..p290gen.t_slwp_values.count)."
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
Search for ERROR within the file.This highlights the employee number causing the issue.
Ensure there are not more than one open ended absence without pay record for one employee.
If there is more that one record, the incorrect row will need to be deleted by Support.
Please raise a new case online and reference the title of this article and include details of the employee affected.
Date effective on position history
There is a data input error for the Date Effective on Position History which can cause failure. Look for the following error in the Pay290 log file:
"P220a -> ERROR on calculate_new_emp_retro
CURRENT EMPNO ([EMPNO]/p220a employee left between retro period)
ORA-06502: PL/SQL: numeric or value error: number precision too large."
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
Search for ERROR within the file. This highlights the employee number causing the issue.
Check the date effective.To do this, follow these steps in back office.
Click CorePay then click Enquiry.
Click View Position History.
If this is incorrect ask HR users to ensure the appointment details are keyed correctly, e.g. 01-JAN-1950, as this will cause the Generate Salaries and Allowances job to fall over.
Space issue
A space issue can cause failure. Look for the following error in the Pay290 log file:
" p290gen.delete_timesheet -> ERROR Deleting TIMESHEETS
ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","select file# from file$ where."
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To resolve this issue, support will need to liaise with the database administration team to flush the SHARED_POOL table.
Please raise a new case online and reference the title of this article and include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"ERROR updating_employee
CURRENT EMPNO ([EMPNO]/p170nm)
ORA-04063: package body "OPS$COREHR.PERS_END_PROCESS_API" has errors ORA-06508: PL/SQL: could not fi.
The package is referencing a test table that doesn't exist on the database."
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"P635a -> ERROR on calculate_absence_allowance
CURRENT EMPNO (EMPNO/p635b)
ORA-01403: no data found"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"P100a -> ERROR fetching EMPLOYEE DETAILS
CURRENT EMPNO (24493/p100g weekly paygroup)
ORA-06502: PL/SQL: numeric or value error: number precision too large"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"P670a -> ERROR on calculate_absence
CURRENT EMPNO (EMPNO/p670g second salary personal rate)
ORA-01403: no data found"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"p290all.get_adjustment_allowance_mult -> ERROR on get_adjustment_allowance_mult (s9160)
CURRENT EMPNO (1116869/p916_found_mult multiplier > 1)
ORA-01476: divisor is equal to zero"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"P100a -> ERROR fetching EMPLOYEE DETAILS
CURRENT EMPNO (000761/p100e2 compress_days)
ORA-06508: PL/SQL: could not find program unit being called"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file. Look for the following error in the Pay290 log file:
"Error on calculate_holiday_salary
current empno (EMPNO/p851c position code/point)
01403: no data found."
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
PAY290 trace file
There is an error in the PAY290 trace file due to M. Look for the following error in the Pay290 log file:
"ERROR fetching EMPLOYEE DETAILS
CURRENT EMPNO (EMPNO/p100a retrieve employee details)
ORA-06502: PL/SQL: numeric or value error: number precision too large"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
A security patch may have resulted in the PAY290 program failing to run.
To review for any errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
ERROR on calculate_retro_end_subs_all
There is an error in calculate_retro_end_subs_all. Look for the following error in the Pay290 log file:
"CURRENT EMPNO (EMPNO/p4b50c calculate timesheet days)
ORA-06502: PL/SQL: numeric or value error: number precision too large"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review for any errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
P4146a
There is an error on adjust_multiplier_4146. Look for the following error in the Pay290 log file:
"P4146a -> ERROR on adjust_multiplier_4146
CURRENT EMPNO (EMPNO/p4146_found_mult calculate rate)
ORA-01476: divisor is equal to zero."
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review for any errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
P645a
There is an error on Error on calculate_substitution_absence. Look for the following error in the Pay290 log file:
"P645a -> Error on calculate_substitution_absence
CURRENT EMPNO (EMPNO/p645a for counter in 1..p290gen.t_slwp_values.count)
ORA-01403: no data found"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review for any errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
P220a
There is an error on calculate_new_emp_retro which can cause failure. Look for the following error in the Pay290 log file:
"P220a -> ERROR on calculate_new_emp_retro
CURRENT EMPNO (XXXXX/p220a employee left between retro period)
ORA-06502: PL/SQL: numeric or value error: number precision too large"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review for any errors please raise a new case online and reference the title of this article. Include a copy of the log file.
Secondary appointments
The employee is left with 1 or more secondary appointments. Look for the following error in the Pay290 log file:
"Primary apt deleted-
Error on calculate_basic_salary (S8000)
current empno (XXXXXX/p800e1 Salary on PH same as salary on NT)
ORA-01403: no data found"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review for any errors, please raise a new case online and reference the title of this article. Include a copy of the log file.
Resource deadlocked
The resource is deadlocked, look for the following error in the Pay290 log file:
"ERROR updating_employee
CURRENT EMPNO (XXXXXX/p170nm)
ORA-00060: deadlock detected while waiting for resource."
To resolve this, follow these steps.
If error shows resource deadlocked, then rerun failed job.
If it fails again after following these steps below, please log a new case online and attach the log file.
From the dashboard menu, click Payroll Dashboard.
Click Manage payroll then click rerun beside failed Salaries and Allowances job.
Missing personnel data
There is a missing personnel data. Look for the following error in the Pay290 log file:
"ERROR P170a -> ERROR updating_employee - CURRENT EMPNO (XXXXXXX/p170nm) - ORA-01400: cannot insert NULL into ("COREHR"."HR_PERSON_ORG_ITEM"."START_DATE")"
To resolve this, review the log file. To do this, follow these steps.
Retrieve the log file for the PAY290.
To review for any errors, please raise a new case online and reference the title of this article. Include a copy of the log file.