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.
Impact on DBI's when we move from Seniority date V2 to V3
Summary:
We are planning to move to V3 version of seniority dates functionality. We are in V2 and since we can still access V1 we are using DBI' referring V1 Table (Per_Periods_of_Service) Ex - PER_ASG_REL_ORIGINAL_DATE_OF_HIRE, ACP_HIRE_DATE etc.
If we move to V3, what will be the impact on fast formulas using these DBI's. Do we need to upgrade to new DBI's? There is no documentation on this. Kindly let us know if any of you have any inputs.
Content (required):
Version (include the version you are using, if applicable):
Tagged:
0