If you encounter an error while generating jobs such as salaries and allowances, validation, run payroll update, or complete update for a newly hired employee who hasn’t yet been paid in the observation report, it may be due to one of the following reasons.
We have compiled a list of possible causes for the error message, along with steps to resolve them.
Incomplete PAY290 job
The generate salaries and allowances (PAY290) job did not complete successfully.
To resolve this, obtain the relevant log text files: pay290.log0000 or pay290.trc0000 (where 0000 is the Pay Group number).
To do this, check how to retrieve a log file, then raise a new case online, referencing this article's title and include the following details:
A copy of the PAY290 log file.
A copy of the PAY290 trace file.
Incomplete PAY140 job
The payroll validation (PAY140) job did not complete successfully.
To resolve this, obtain the relevant log text files, pay140.log0000 or pay140.trc0000 (where 0000 is the Pay Group number).
To do this, check how to retrieve a log file, then raise a new case online, referencing this article's title and include the following details:
A copy of the PAY140 log file.
A copy of the PAY140 trace file.
Incomplete PAY300 job
The run payroll update (PAY300) job did not complete successfully.
To resolve this, obtain the relevant log text files, pay300.log0000 or pay300.trc0000
🤓Tip: Here, 0000 represents the pay group number.
To do this, check how to retrieve a log file, then raise a new case online, referencing this article's title and include the following details:
A copy of the PAY300 log file.
A copy of the PAY300 trace file.
Incomplete PAY355 job
The complete update (PAY355) job did not complete successfully.
To resolve this, obtain the relevant log text file, pay355.log0000.
🤓Tip: Here, 0000 represents the pay group number.
To do this, check how to retrieve a log file, then raise a new case online, referencing this article's title and include the following details:
A copy of the PAY355 log file.
Invalid characters
The user's password contains invalid characters such as /, %, -, or @.
To resolve this, follow the steps below.
Change the password to include letters and numbers.
Log out of CoreHR completely.
Clear the job status. If you're unable to do this, please raise a new case online referencing this article's title.
Once cleared, log back into CoreHR then re-run the PAY290 job.
Locked session
A user is preventing the job from proceeding by accessing a record.
To resolve this, obtain the log text files for the relevant job as outlined above.
To do this, check how to retrieve a log file, then raise a new case online, referencing this article's title and include the following details:
A copy of the relevant log file.
A copy of the relevant trace file.
Full tablespace
The tablespace is full.
To resolve this, obtain the log text files for the relevant job as outlined above.
To do this, check how to retrieve a log file, then raise a new case online, referencing this article's title and include the following details:
A copy of the relevant log file.
A copy of the relevant trace file.