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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
We are not using PER_SENIORITY_DATES table, still need to migrate to V3 seniority dates?
Based on the previous SR 3-33505072291 , Oracle confirmed that we are we are on V1 seniority dates coexist with V2.
Current Version: 23B
But we have run the below Oracle query to get the latest DBI is the system and based on the analysis of these DBIs we are not using PER_SENIORITY_DATES table but using only PER_PERIODS_OF_SERVICE. Do we need to still migrate to V3 seniority dates even though we are not using PER_SENIORITY_DATES table in our fast formulas, Extracts and Reports?
Please confirm.
Query:
select
fat.module_name, fdg.base_group_name, fdg.group_name, fdi.base_user_name, fdi.user_name, fdi.description, fdi.data_type, fdi.definition_text,
Tagged:
0