Retropay Costing Results from Before the Payroll Change Defaulting to Assignment Costing instead Element Entry Costing
(Doc ID 1609538.1)
Last updated on FEBRUARY 27, 2019
Applies to:
Oracle Payroll - Version 12.0.6 and laterInformation in this document applies to any platform.
Symptoms
Applied & tested the Patch 16554212:R12.PAY.A COSTING ENTRIES NOT PICKED PROPERLY
Find that the original scenario is fixed, ie for costing of a regular run but they also tested the costing of Retropay results, although find that the problem is happening for Retropay results.
Steps to Reproduce:
- Assignment has a payroll change, mid period
- Retropay and Payroll are run, then Costing
- For that period, see:
-
- Costing results from before the payroll change are defaulting to the Assignment Costing instead of going to the costing on the Element Entry from that week.
- Costing results from after the payroll change are correctly going to the costing on the Element Entry.
Expect that the costing for the Retropay results would follow the Element Entry costing, even though there was a Payroll change mid period.
Changes
Patch 16554212:R12.PAY.A COSTING ENTRIES NOT PICKED PROPERLY
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 |
References |