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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.

Absence Date Validation

Summary:

We have a vacation plan that begins on the 91st day of employee and front-loaded with 40 hours. On the 181st day of employee any hours from the 91-180 day plan are transferred to the 181 day plan and the 181 day plan is front-load with 40 hours. So if on day 175 an employee had 16 hours, on the 181st day the 91-180 plan hours of 16 are transferred and the plan is end date. The 181 day plan receives the 16 + 40 new hours giving a balance of 56 hours.

Works Great!

We have encounter a problem where a given employee had 56 hours in the 181 day plan say that was 8/15/22 and on 8/20/22 the employee puts in an absence entry for 8/1/22. The entry was accepted. The problem is that the 91-180 plan is closed and has no hours. We want a way for that to not happen. I think i can do this via Global Absence Entry Validation but that is geared toward the Absence Type and not the Absence Plan. Is that my only option? If that FF is the otpion

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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