Mid Period Salary Change is not Prorated by Retrocosting Process (Doc ID 947832.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Payroll - Version 11.5.10.2 and later
Information in this document applies to any platform.

Goal

After running the Retrocosting process, it looks like it is coding all of the salary (even though there was a change mid month) to the cost center that is active at the end of the month.

Example:

 

In  May 20XX, the costing run correctly assigned the monthly salary to account "1234".

The costing field on the assignment screen was updated on 20th May and when RetroCosting ran at the end of May it reassigned all the costs to the valid cost code at the end of the month - "5678"

On the 27th May, the salary was amended back to 15th May and the record went through Retropay.

In June, the Retropay process has reclaimed the overpayment and recalculated the correct salary for May. The costing, however, has still posted everything against "5678" the cost code valid at the end of the month.

 

 Is this the correct behaviour?

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms