Important Note
If you need to Rollback the pay to fix it, you will need everyone else logged off the database.
To Rollback, refer to the PayGlobal Help File for further information Click here
Or to watch the video on Rollback Pays. Click here
You can use the Eject User function and apply the lock to stop more users logging in.
Refer to the PayGlobal Help File for further information Click here
Could not deny pessimistic locks on associated tables as some records are being edited by other users. Check the table status form for more information on locked tables/records.
Another user has an employee record open in PayGlobal. Please ask other users to close out of editing employee records and try closing the pay again.
Close Routines failed - Last successful step was 0 - Failed during MastUpdate
This will be an employee that has been moved to a different period code. You will need to delete them from the pay you are trying to close.
-
Rollback pay
-
Fix the employee causing the crash by deleting them from the pay sequence.
-
Process and close the pay.
General zero FTE Hours proof failure by : 1094.42
Fault detected with employee : 3424 Zero proof FTE hours : 1094.42
Failed during IntegrityOk
This is usually caused by an employee being paid more than 999.99 hours annual leave on termination. This error can also occur if you are reversing a termination and the negative AL termination hours are more than -99.99.
To resolve issue you will need to manually enter the Annual Leave on Termination with quantities of less than 999.99 or less than -99.99 hours in multiple transactions.
Not all employee/entity updates were completed.
The most common reason for this is that another user has these records locked.
Once those users have released these records, then the pay closing procedures can be resumed.
Failed during EntityUpdateClose routines failed, last successful step was 0 -
This is usually caused by a User Defined field being updated on close pay with amounts that exceed the size of the User Defined Field Settings.
For example:Field Size of UDF is 6 and 2 decimals. This means that you can enter 999.99 (the decimal point counts as a character).
Not all employee/entity updates were completed.
The most common reason for this is that another user has these records locked.
Once those users have released these records, then the pay closing procedures can be resumed.
Failed during EntityUpdate
Close routines failed, last successful step was 1000 - EntityUpdate
This is usually caused when either the FTE or Total Amount on the Costcentre exceeds the field size. The size is 10 numerals, including decimal point.
To resolve, clear out the Total Amounts / FTE on the Costcentre records.
Accumulator : YTD Kilometres
Referential integrity issue finding key "****" in table "Allowance"
Close routines failed, last successful step was 1120 - RebuildAccumulators
The Close Pay procedures were updated in version 4.71.0.0 where the Pay will not close if there are any errors whatsoever.
This Error means there is a problem with a User Defined Field that is set to Accumulate.
In this example, the YTD Kilometres UDF had an allowance attached that did not exist in the database.
The resolultion is to add the correct allowance, or to Change "Accumulating" to NO on the UDF setup.
Close routines failed, last successful step was 1000 - EntityUpdate
Closing Pay error Close routines failed, last successful step was 1000 - EntityUpdate is a generic error that can be caused by the following:
-
Another user/ process has locked a record during Closing Procedures
-
Take backup copy of current database
-
Rollback the pay. Note that even though the pay failed to close, a rollback is needed to clear the fail tag
-
Process and Close the Pay Again
-
User Defined Field values exceeding their field size
-
Go to Administration> User-defined Fields
-
Right +Click on the User Defined Fields table , add the Accumulator Column and Filter the grid to show only accumulator UDFs
-
Back in the Employee Grid, add these Accumulator UDFs and sort individually to check where an employee may have potentially exceed the filed size values
-
Cost Centre/ FTE
-
This is usually caused when either the FTE or Total Amount on the Costcentre exceeds the field size. The size is 10 numerals, including decimal point.
-
To resolve, clear out the Total Amounts / FTE on the Costcentre records.
-
Custom Triggers
-
If Steps 1-3 does not yield any potential cause, contact PayGlobal Support so we can check if there are customised triggers
(Not Common ) Input Allowance table values not equal to Current Allowance Values possibly due to rounding/truncation when large quantities are involved
Reach out to MYOB PayGlobal Support so we can check the back end tables.
Error!!! (Method: UpdateEmployeeAccumulators - Transaction (Process ID 279) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction)
Try to rollback the pay by going to Payroll> Rollback Pay> Process and try to Close again.
The deadlock error is usually due to momentary loss of connection with the SQL database or data lock when two users/process are accessing and writing to the same object.
Calculated value for user defined field XE****** for employee 12345 exceeds the maximum field size. UDFCalculation didn't process
This error occurs when closing a pay and the amount being written to a User Defined Field (UDF) exceeds the maximum balance size configured for that field.
To resolve this issue you may need to make the size of the UDF larger. To do this you will need to contact MYB PayGlobal Support to provide a SQL script to enlarge the field or if your database is hosted online, we can run the script for you.
If the UDF size is correct, then the payment to the UDF might be incorrect.
Contact MYOB PayGlobal Support for assistance.
Accumulator : Service Award LWOP Days- Employee - Error!!! (Method: UpdateThisAccumulator - Arithmetic overflow error converting numeric to data type numeric)
See resolution for as this is usually the same issue Common Close Pay Errors | Calculated value for user defined field XE****** for employee 12345 exceeds the maximum field size. UDFCalculation didn't process
ERROR Other open pays were found for this employee that are not linked to termination payments. Please process and close the other pays first, or delete the transactions in them for the employee.
There is another open pay with transactions not relating to the termination being processed in pay in the pay your are processing.
The transactions would need to be removed from the other pay sequences and added to the Termination Pay.
Please here on instructions on how to delete the employee from the other pays.
Error: There are no valid pay sequences
This error will be displayed if the pay sequence is not fully processed.
To check if it is fully processed, view the Pay Status / PR Seq tab.
See screenshot below:
The red X against the pay sequence means that it has not been fully processed yet.
If you have processed it and it still shows not fully processed, ensure you have deactivated all queries on the employee grid and do not have any queries on the Process Pay screen before processing again.
