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.

Validation for L1 and L2 Absence Withdrawal After Payroll Lock Date not working as expected

Summary:

We need to implement and validate a system rule for absence withdrawal by L1 and L2 roles, specifically in cases where they attempt to withdraw an employee's leave after the payroll lock date. The system should enforce the following behavior:

  1. Before Payroll Lock Date:
    • L1 and L2 should have the ability to withdraw an employee’s leave without restrictions for the relevant payroll period.
  2. After Payroll Lock Date:
    • L1 and L2 should be restricted from withdrawing an employee’s leave once the payroll lock date has passed for the relevant month.

Currently, the withdrawal functionality for L1 and L2 is not working as expected, as the system does not properly validate withdrawal actions against the payroll lock date. This leads to inconsistencies in attendance and payroll data, especially when adjustments are made after the payroll is processed.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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