Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Prevent V3 seniority calculation/re-calculation from changing manually adjusted seniority
Summary: How can we prevent the calculate seniority dates ESS job from touching our seniority records that were manually adjusted? We are on V3.
Content (required): We had to create a new seniority (V3) configuration. I ran the ESS job to seed the records in the table. I then ran HDL to adjust all our re-hires' dates. Everything looked great. Then the scheduled job came in and unraveled all my manual adjustments - the dates are now skewed. How can we prevent Oracle from touching the records that got manual adjustments? Basically, if a seniority record got a manual adjustment via HDL or UI, they should remain untouched by the system.
Tagged:
0