Handling Data Errors in Batch Posting

This topic provides an overview of data error handling and discusses how to:

  • Identify data to be purged and reprocessed.

  • Reset and repost the payroll accounting lines.

This topic discusses:

  • Data error possibilities.

  • Data error correction procedures.

Data Error Possibilities

The following 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 General Ledger.

  • When you run the Journal Entries Batch Processor program (R09110Z) in EnterpriseOne, the system validates the specific combinations of account code and cost center and might detect an invalid account number.

    The accounting lines sent to General Ledger from Global Payroll applications contain an account code and a cost center. The Enterprise account code corresponds to the object and subsidiary in EnterpriseOne, while the Enterprise cost center corresponds to the EnterpriseOne company.

    Because the account number in EnterpriseOne consists of a combination of the business unit, object, and subsidiary, the combination of the Enterprise account code and cost center might produce an EnterpriseOne account number that is invalid.

    For example:

    • It might use a cost center in Enterprise that does not correspond to a valid EnterpriseOne company.

    • If the EnterpriseOne company contains two or more accounts with the same object and subsidiary, but different business units, the integration might produce the wrong 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 EnterpriseOne account number, you might need to book the amounts to a different account code or cost center in Enterprise.

  • The finance office administrators might need to redistribute the amount to the correct account in EnterpriseOne.

    For example, the account code and cost center are correct in Enterprise, but amounts are booked to the wrong account number in EnterpriseOne because two or more 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 tables in the EnterpriseOne database.

  • Purge the records that contain errors from the EnterpriseOne database and request the administrators of the Enterprise payroll application to:

    1. Reset the general ledger posting process.

    2. Correct the errors in the payroll setup.

    3. Rerun general ledger processing and repost the results.

      You would use this method if the errors were too numerous to be corrected in table F0911Z1.

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 topic discusses how to locate data to be purged or reprocessed:

  • When the requirement initiates in the finance office.

  • When the requirement initiates in the payroll office.

Finance Office Initiates

If the data correction requirement is initiated in the finance office:

  1. The finance office administrator:

    1. Locates the Enterprise process instance ID from the Transaction Number field on the Work With Store & Forward Journal Entries page.

      The transaction number on this page is the Enterprise process instance ID.

      See PeopleSoft EnterpriseOne 8.11 Application Integrations with PeopleSoft Applications, "Using the PeopleSoft Payroll to PeopleSoft EnterpriseOne General Ledger Integration," Processing PeopleSoft Payroll Data in PeopleSoft EnterpriseOne General Ledger , Locating Payroll Batch Transactions in PeopleSoft EnterpriseOne

    2. Communicates the process instance ID number to the payroll office administrator.

  2. The payroll office administrator views the View GL Transaction Status page for the process instance to determine the affected calendar group ID.

Payroll Office Initiates

If the data correction requirement is initiated in the payroll office:

  1. The payroll office administrator:

    1. Views the View GL Transaction Status page to determine the process instance ID associated with the calendar group ID that requires reprocessing.

    2. Communicates the process instance ID number to the finance office administrator.

  2. The finance office administrator uses the process instance ID number to locate the payroll batch process transaction on the Work With Store & Forward Journal Entries page.

    The payroll process instance ID is the same as the transaction number in this page.

If EnterpriseOne purges the batch of F0911Z1 records, the Enterprise payroll application administrator must be notified to reset the general ledger processing and repost the accounting lines.