Process to Migrate Seniority Dates

You run the Migrate to Version 3 of Seniority Dates process to migrate the seniority dates data to the new version (V3) from an earlier version (V1). Use the Scheduled Processes work area to schedule and run the process.

Note: Before you migrate to V3, you must do this - Update the seniority basis for all worker assignment records to the appropriate values in days or hours. You can do this using HCM Data Loader.

You can run the process only once to migrate seniority data from V1 to V3.

If you want to roll back to V1 after migrating to V3, run the Migrate from V3 to V2/V1 - Correct diagnostic test. For more information, refer to the Migrate from V3 to V2 or V1 - Correct attachment in the document Self-Service Data Integrity Framework for Employment Flows - Part 1 (Doc ID 2548287.1) on My Oracle Support (https://support.oracle.com).

Note: Even though you can see V2 seniority dates related process parameters, they are no longer supported. V2 seniority dates have been deprecated from release 23B.

What Happens When You Run the Process

V1 to V3 conversion: V1 seniority dates only display the hire date and seniority date for the enterprise and legal employer and you don't configure any seniority rules. When you run the process to migrate seniority data from V1 to V3, the application automatically creates these seniority rules:

• Legal Employer Seniority Date - Work Relationship Level - Migrate

• Enterprise Seniority Date - Person Level - Migrate

The process hides the seniority dates on the Work Relationship page and the application stops populating V1 seniority dates. However, the application will retain the value of the V1 seniority dates. If there are adjusted values for V1 seniority dates, the application automatically creates the corresponding adjustments for V3 seniority rules. Therefore, the resulting seniority dates values are the same in V3. The seniority dates region in the employment information UI will display V3 seniority dates instead of V1 seniority dates. After the migration to V3, seniority data is maintained in the PER_SENIORITY_DATES_F table and the PER_PERIODS_OF_SERVICE table is no longer used to maintain V1 seniority dates.

Note: All existing V1 seniority data are retained in the PER_PERIODS_OF_SERVICE table.

Note: You must re-evaluate the integrations, extracts, reports, derived factors, eligibility profiles, and fast formulas. This is because these items may be using the tables or database items where the underlying seniority dates version is V1. All existing V1 seniority data are retained in the PER_PERIODS_OF_SERVICE table.

Process Parameter

The Migrate to Version 3 of Seniority Dates process uses the Migrate Seniority Data From parameter. This parameter indicates whether you want to migrate seniority dates data to V3 from V1.

Parameter	Process Results
V1 Seniority to Non-Cumulative V3 Seniority	V1 seniority dates are moved to V3. V3 seniority rules corresponding to V1 seniority are created as non-cumulative.

Note: Even though you can see V2 seniority dates related process parameters, they are no longer supported. V2 seniority dates have been deprecated from release 23B.