Understanding Data Error Handling
This chapter provides an overview of data error handling and discusses how to:
Correct errors in the Journal Entry Transactions - Batch File table.
Identify data to be purged and reprocessed.
Purge the batch of F0911Z1 records.
Reset and repost the payroll accounting lines.
Understanding Data Error Handling
This section discusses:
Data error possibilities.
Data error correction procedures.
Data Error Possibilities
These are some reasons that data error handling would be required:
The payroll office might discover errors in the accounting lines after posting the data to JD Edwards EnterpriseOne General Ledger.
When you run the Journal Entries Batch Processor program (R09110Z) in the JD Edwards EnterpriseOne system, the system validates the specific combinations of account code and cost center and might detect an invalid account number.
The accounting lines sent to JD Edwards EnterpriseOne General Ledger from PeopleSoft Enterprise payroll applications contain an account code and a cost center. The PeopleSoft Enterprise account code corresponds to the object and subsidiary in the JD Edwards EnterpriseOne system, while the PeopleSoft Enterprise cost center corresponds to the JD Edwards EnterpriseOne company.
Because the account number in the JD Edwards EnterpriseOne system consists of a combination of the business unit, object, and subsidiary, the combination of the PeopleSoft Enterprise account code and cost center might produce an JD Edwards EnterpriseOne account number that is invalid.
For example:
It might use a cost center in the PeopleSoft Enterprise system that does not correspond to a valid JD Edwards EnterpriseOne company.
If the JD Edwards EnterpriseOne company contains two or more accounts with the same object and subsidiary, but different business units, the integration might produce the wrong JD Edwards EnterpriseOne business unit, object, and subsidiary combination.
Data Error Correction Procedures
When errors are discovered:
The finance office administrators and payroll office administrators must communicate to coordinate the method of handling the errors and to identify the data to be corrected.
The payroll office administrators might need to correct errors in the payroll setup.
For example, if the account code and cost center are generating an invalid JD Edwards EnterpriseOne account number, you might need to book the amounts to a different account code or cost center in the PeopleSoft Enterprise system.
The finance office administrators might need to redistribute the amount to the correct account in the JD Edwards EnterpriseOne system.
For example, if the account code and cost center are correct in the PeopleSoft Enterprise system, but amounts are booked to the wrong account number in the JD Edwards EnterpriseOne system because two or more JD Edwards EnterpriseOne accounts have the same object and subsidiary, but different business units in the same company.
Errors in the payroll data that has been posted to general ledger can be handled in one of two ways:
Correct errors in the F0911Z1 table using the Journal Entry Revisions program (P0911Z1).
You can use this method if you have run the Journal Entries Batch Processor program in proof mode and the errors are few enough in number that they can be easily corrected in the F0911Z1 table. After you correct the errors in the F0911Z1 table, run the Journal Entries Batch Process program in proof mode. In this situation, the payroll office administrators should correct the payroll setup so that the same errors do not occur on the next payroll run.
Purge the batch of F0911Z1 records that contain errors and request the administrators of the PeopleSoft Enterprise payroll application to:
Reset the general ledger posting process.
Correct the errors in the payroll setup.
Rerun general ledger processing and repost the results.
You would use this method if the errors were too numerous to be corrected in the F0911Z1 table.
Correcting Errors in the Journal Entry Transactions - Batch File Table
Use the Journal Entry Revisions program (P0911Z1).
See Working with Batch Journal Entries.
Identifying Data to be Purged and Reprocessed
If reprocessing of payroll data is required, the finance office administrators and payroll office administrators must communicate to identify the data to be reprocessed. This section discusses how to locate data to be purged or reprocessed:
When the requirement initiates in the payroll office.
When the requirement initiates in the finance office.
Finance Office Initiates
If the data correction requirement is initiated in the finance office:
The finance office administrator locates the Enterprise process instance ID from the Transaction Number field on the Work With Store & Forward Journal Entries form.
The transaction number on this page is the PeopleSoft Enterprise process instance ID.
The finance office administrator communicates the process instance ID number to the payroll office administrator.
The payroll office administrator views the GL Transaction Status page for the process instance to determine the affected pay run ID (Payroll for North America) or calendar group ID (Global Payroll).
Payroll Office Initiates
If the data correction requirement is initiated in the payroll office:
The payroll office administrator views the GL Transaction Status page to determine the process instance ID associated with the pay run ID (Payroll for North America) or calendar group ID (Global Payroll) that requires reprocessing.
The payroll office administrator communicates the process instance ID number to the finance office administrator.
The finance office administrator uses the process instance ID number to locate the payroll batch transaction on the Work With Store & Forward Journal Entries form.
The payroll process instance ID is the same as the transaction number in this page.
See Also
Locating Payroll Batch Transactions in the JD Edwards EnterpriseOne System
Purging the Batch of F0911Z1 Records
Use the Purge Batch Journal Entries program (R0911Z1P).
See Purging Processed Batch Journal Entries.
Resetting and Reposting the Payroll Accounting Lines
If the JD Edwards EnterpriseOne system purges the batch of F0911Z1 records, the PeopleSoft Enterprise payroll application administrator must be notified to reset the general ledger processing and repost the accounting lines.
See Also