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.
Issue with Seniority Date V3 entity
Summary:
We are are using the user entity PER_SENIORITY_DATES_V3_UE to get the enterprise seniority date and legal entity seniority date. At one point, we had to put a filter psdf.EXIT_DATE IS NULL as this was causing duplicates. However, this is now an issue as it is restricting some rows. We do not understand the column EXIT_DATE and how it gets populated. Is there a process that populates this column and can we schedule it? Can we get more information on this?
Content (required):
As above
As per Oracle HCM Tables, the table PER_SENIORITY_DATES_F,
Tagged:
0