You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now

How to best handle retro dated HR Transactions without impacting a future dated action?

We've been running into multiple situations where a leader (or HR) will submit a back dated HR transaction but the worker has a future dated action already processed. The retro change will go through but then business reports it "reverted back" because the future action that was out there didn't have the retro changes accounted for.

Example:

Change Assignment processed on worker with 6/1/2024 effective date

On 7/2, Leader submits a Change Assignment to put worker on an LOA status with an effective date of 5/21/2024

The workers LOA status change ends as of 5/31 because the 6/1/2024 record was already processed.

Is there any way around this? Or advise on a good business practice to avoid? We do have some transactions where we will have to allow retro dated changes.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!