Fusion Global Payroll: Costing Data Not Prorated after Position Change
(Doc ID 2975960.1)
Last updated on OCTOBER 01, 2023
Applies to:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.23.04.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
After moving the employee's assignment from one position to another after running the Payroll for the respective month it has been noticed that the costing data was not prorated - no change in costing.
EXPECTED BEHAVIOR
-----------------------
After running the Payroll for the respective month the costing data should be prorated and including the update.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Define Proration Event Group
2. Define Assignment for employee before position change
3. Define costing of the position
4. Move employee from one position to another in Manage Assignment (on 12th June)
5. Define costing of new position
6. Run Payroll for June and notice that the proration was triggered due to position change
7. Notice that costing was prorated for elements as expected
8. Define Proration Event Group
9. Define Assignment for employee before position change
10. Define costing of the position
11. Move employee from one position to another in Manage Assignment (on 11th of July)
12. Define costing of new position
13. Run Payroll for July and notice that the proration wasn't triggered for this employee.
14. Notice that costing was not prorated for elements as expected
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 |
Cause |
Solution |
References |