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.
Is it necessary to migrate to V3 Seniority Date?
Summary: Following document, FusionGlobal HR: V2 Seniority Dates Deprecation in Release 23B (Doc ID 2935517.1), our version is V2. We wish to keep using per_periods_of_service along with the manage work relationship functionality. We do not have any seniority date rules since we simply use the seeded functionality of hire date.
Should we or do we have to migrate to V3, then rollback to V1? Please confirm.
What does it mean that Oracle will no longer support V2?
Content (required):
No Seniority Date Rules are configured. The Employment configuration Options>Default Enterprise Seniority Date is Null
Version (include the version you are using, if applicable): 23A
Tagged:
0