Get Started: AI Resources for Oracle Cloud HCM – Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Seeking help using/integrating the V3 Seniority Date table into reports
Summary:
Migrating to V1/V2 Coexistence to V3 Seniority Dates and trying to understand how to populate start dates in custom reports
Content (required):
Our integration team uses the fields DATE_START and ORIGINAL_DATE_OF_HIRE from the table PER_PERIODS_OF_SERVICE.
It is my understanding that once we migrate to V3, we will no longer be able to use the PER_PERIODS_OF_SERVICE table and must use the PER_SENIORITY_DATES_F table. However, the DATE_START and ORIGINAL_DATE_OF_HIRE are not columns in the new table.
What is the recommendation for substituting these fields to ensure that migrating to V3 does not cause a major disruption?
Tagged:
0