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.
User dont want to move to V3 of Seniority dates
Summary: when we run the query "SELECT VERSION_CODE FROM FUSION.PER_EMPL_CONFIGURATIONS" it shows the version as "V2" but we dont have any Seniority Dates rules created, we maintain the seniority dates in "Manage Work Relationship" page and user want to continue in the same way.
will there be any impact if we are maintaining the seniority dates in "Manage Work Relationship" page, as query "SELECT VERSION_CODE FROM FUSION.PER_EMPL_CONFIGURATIONS" it shows we are in version as "V2"
Content (please ensure you mask any confidential information):
Version (include the version you are using, if applicable):
Tagged:
1