Distributed Costing not correct when Multiple Retro Elements Processed (Doc ID 1683210.1)

Last updated on JANUARY 05, 2017

Applies to:

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

Symptoms

For an hourly paid employee hours are entered retrospectively and paid in the following payroll period.  The element entries that contain the hours worked per cost center are calculated into a pay value and feed a distribution set.  Extra salary components like employer pension premiums, holiday pay reservations are costed using this distribution set (following the cost centers of elements where the hours worked are entered.

For the retrospective element entries made costing entries are set at element entry level. When the retro process is started this will generate multiple retro entries as it will affect the base salary and Holiday Pay Reservation.(In this example)

When the costing process is started it is found that from the generated retro entries the first distributed element are correctly costed against the costing segments set at element entry level. All other results seem to be costed against Organization level.  While it is expected since the element are part of the distribution set that these elements are costed against the element entry level costing belonging to the retrospective entered hours element entry.


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

1. Run payroll
2. Retro enter Hours worked
3. Run Retropay Process
4. Run Payroll
5. Run Costing


Cause

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