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.
Migrating seniority dates from v1 to v3
Summary:
We plan to migrate to v3 version of seniority dates soon and are looking for a resource center/guidelines for do's an donts. We know we have plenty of reports and interfaces impacted because PER_PERIODS_OF_SERVICE is used almost everywhere
1. How do we verify the fall outs from the migration or the batch job that moves out data from v1 to v3 tables. Is there a diagnostic report/analytic available that helps us track the transition
2. Is there a list of business objects, UI flows, pages, notifications etc impacted by this change
3. How do we get the list of reports and integrations impacted by this table change
Tagged:
1