Diagnosing Pre-Payroll Errors
Occasionally, you might experience errors that cause pre-payroll to end abnormally. These errors can be related to a single employee, or the entire payroll cycle.
You have a number of diagnostic tools available to help you identify the errors that are causing pre-payroll to end abnormally. To identify the errors, you should:
Review all payroll messages that were generated by this payroll ID.
These messages are specific to certain employees in the payroll process.
Review all messages in the Personal In Basket.
You might need to clear the in basket of all messages, and then rerun pre-payroll to locate the specific messages that are associated with this payroll ID. These messages apply to programmatic errors that occur during payroll processing.
Generate logs when running pre-payroll.
These logs can provide you, the system administrator, and the JD Edwards technical assistance team with pertinent information. You should generate these logs:
JDE.log
JDEDebug.log
UBE.log for R07200
Determine whether the Pre-Payroll Driver UBE finished normally on the server.
Contact the system administrator for assistance with these troubleshooting tasks:
Review the OCM mappings for R07200.
Confirm that a server package/update was completed if you use modified objects.
Confirm that Quantum for Payroll is loaded on the server, and that the database connections are set correctly.
Confirm that all necessary UBEs and business functions have been mapped to run on the server.
Confirm that the version of the R07200 that is associated with this payroll ID has been checked into the server.
Verify that these setup tasks have been completed:
Review the accuracy of the data selection for the payroll ID.
Specifically, review data selection criteria for employee number, start date, and pay status.
Confirm that the Master Pay Cycle is set up with valid dates.
Verify that the country code that is associated with the payroll ID is the same country code that is associated with the employees whose records you are processing.
Verify whether Auto Pay is selected for the payroll ID, if applicable.
Review the additional parameters for the payroll ID.
Confirm that employees who are being processed in this payroll are not locked to another payroll ID.
After you reset the payroll ID, verify that the G/L Date (DGL) and Batch Number - G/L (GICU) fields in the Employee Transaction Detail File table (F06116) are empty.
Contact the system administrator for assistance.
Verify that security for the system and for the payroll ID have been set up correctly by:
Verifying that the person who processed pre-payroll is included in the Execution Control Parameters.
Confirming that additional security has not been set up for a specific user.
Contact the system administrator for assistance.
After reviewing tools, setup, and security information, if you still cannot determine the cause of the pre-payroll errors:
Process pre-payroll without generating any reports.
If pre-payroll runs successfully without reports, contact the system administrator or technical support; you might need to build a server package with the reports.
Verify that the Employee Master Information table (F060116) and the Employee Jobs table (F060118) contain the same number of records.
Exclude interim payments from the payroll ID.
If pre-payroll finishes successfully without interim payments, review all of the interim payments that were previously included in the process. Specifically, review one-time overrides and DBAs.
Confirm that timecards are being created during pre-payroll for all autopay employees.
If the R07200 program fails to run on the server, try processing it locally.
Contact the system administrator for assistance with this task