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.

How to load past Person Absence Entry without affecting existing future dated absences

Summary:

Hi Team,

I have loaded year 2021 back dated person absence entries using HDL. Employee already has 2022 and 2023 future absence entries. Now when loading is completed for 2021 absences, existing future dated absences of 2022 and 2023 are also auto re-evaluated automatically. Because of re-evaluation, 'Last_Update_Date' column is also change to HDL loading date. Hence transactions of 2022 and 2023 also appearing in reports.

1. Is there any way to avoide future date absence re-evaluation when we load past dated person absence entries using HDL.

2. Is there any way where 'Last_Update_Date' of future dated existing transactions should not be affected when we are loading past dated data.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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