Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Retro Not Processed if Element Entry Date is Not First Date of the Previous Month

Summary:

We have one element for which we can override the amount. If the override is done retrospectively, it only gets processed if the Element Entry Effective Start Date is the first day of the month and it does not get processed for any other date retrospectively.

How to mitigate this?

Content (required):

Scenario #1 works:

Ran payroll for May for an employee - Ran payroll for June for that employee - Overrode Amount for the element as effective of 1st June- Ran payroll for July for that employee - the overridden amount is appearing for July, the Retro element is processed for June and the difference between the overridden amount and the already processed amount appears (this is correct)

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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