Back Dated Transaction In MSS Doesn't Preserve the Correct Cost Center

(Doc ID 2299016.1)

Last updated on AUGUST 21, 2017

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version and later
Oracle Fusion Global Human Resources - Version and later
Information in this document applies to any platform.


When there is a back dated transaction entered in Manage Employment, there is a warning alerting the user to check the future date rows (after the back date being entered) manually.
Since this Manage employment is used by HR Admins, it would be fine for them to check the future dated row is any exists.
Please find below business case scenario:

The employee was hired at 1/1/2017 with "Job - ABC, Grade - 7, Cost Center - XYZ".
On June 9th, 2017 (which is the current date - sysdate) the Cost Center was changed by the HR user and the employee has: "Job - ABC, Grade - 7, Cost Center - XYR"
After the Cost Center was changed and saved, HR came again in the same date June 9th, 2017 and set for the same employee a new job that will be valid starting with a future date June 10th, 2017.
After the new job is saved, the Cost Center is changed automatically with the one on that the employee was hired and the employee will have: "Job - ABD, Grade - 7, Cost Center - XYZ".



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