My Oracle Support Banner

EPY: Retro Pay Amount is Going to the Current Funding Source for General Ledger (Doc ID 2987992.1)

Last updated on APRIL 15, 2024

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Retro Pay is being expense to the current account for General Ledger.

An employee is paid in October and retro pay earnings are included on the paycheck. The retro pay earnings are from August - when the employee's position number was funded by Account Code X.

Effective October, the position number did not change, but funding for the position changed to Account Code Y.  The retro pay earnings from August were expensed to Account Code Y.

We expected the retro earnings would be expensed to the account code based on the funding for the earnings period designated on the August check.


The issue can be reproduced at will with the following steps:

1. Department Budget Table has combination code (ie. P0000001) associated as the default for earnings - Set up HCM>Product Related>Commitment Accounting>Budget Information>Department Budget Table USA
2. Create paysheets - Payroll for North America>Payroll Processing USA>Create and Load Paysheets>Create Paysheets
3. Verify on the payline that the combination code is blank - Payroll for North America>Payroll Processing USA>Update Paysheets>By Payline
4. Run payroll calculation - Payroll for North America>Payroll Processing USA>Produce Payroll>Calculate Payroll
5. Confirm payroll - Payroll for North America>Payroll Processing USA>Produce Payroll>Confirm Payroll
6. Run PSPPFUND - Payroll for North America>Payroll Distribution>Commitment Accounting USA>Distribute Actuals
7. Verify that the PAY_ERN_DIST for the combination code which shows the default from the Department Budget Table
8. Run PAYGL02 - Payroll for North America>Payroll Distribution>Provide GL Information>Commitment Accounting Actuals
9. Insert a new effective dated row on the Department Table that changes it to another combination code (ie. P0000004) - Set up HCM>Product Related>Commitment Accounting>Budget Information>Department Budget Table USA
10. Go to JOB data and insert an effective date row for the beginning of the begin date on confirmed check and increase the salary - Workforce Administration>Job Information>Job Data
11. Verify that the retro is triggered - Payroll for North America>Retroactive Processing>Retro Pay>Process and Review Requests>Request and Trigger Summary
12. Run the retro calculation - Payroll for North America>Retroactive Processing>Retro Pay>Process and Review Requests>Calculate Retroactive Pay
13. Verify that the RETROPAY_ACCT is blank.
14. Create paysheets for the next pay period - Payroll for North America>Payroll Processing USA>Create and Load Paysheets>Create Paysheets
15. Run the Retro Process Load - Payroll for North America>Retroactive Processing>Retro Pay>Process and Review Requests>Load Retro Pay to Paysheets
16. Verify that PAY_EARNINGS does not have the ACCT_CD that was used on the confirmed paycheck
17. Run payroll calculation - Payroll for North America>Payroll Processing USA>Produce Payroll>Calculate Payroll
18. Confirm payroll - Payroll for North America>Payroll Processing USA>Produce Payroll>Confirm Payroll
19. Run PSPPFUND - Payroll for North America>Payroll Distribution>Commitment Accounting USA>Distribute Actuals
20. Verify that the PAY_ERN_DIST for the retro earnings is using the combination code (ie. P00000004) which is the default from the Department Budget Table

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.