Fusion Global HR: V2 Seniority Dates Deprecation in Release 23B (Doc ID 2935517.1)

Last updated on JULY 05, 2023

Applies to:

Goal

Who is affected?

Global Human Resources customers who still use Seniority Dates V1/V2 coexistence or V2 are affected.

How do I know what Seniority Date version I am on?

We recommend users visually confirm their version in the UI.

Version 1 (V1):  Visually review the Seniority Dates in My Client Groups>Quick Action>Show More>Employment>Work Relationship

For confirmation if V1 is being used in coexistence with V2, check if fields Legal Employer Seniority Date or Enterprise Seniority Date are populated.

 
Version 2 (V2) and Version 3 (V3):  Visually review the Seniority Dates UI in My Client Groups>Quick Action>Show More>Employment>Seniority Dates

The V2 page has a different look and layout than the V3 page.

V2

V3

For further information on rules that have been configured for V2 or V3, visually review the Configure Seniority Date Rules screen in Setup and Maintenance>Search>Configure Seniority Dates

What is the change?

Seniority Dates V2 will no longer be supported. Customers on Seniority Dates Version 2 MUST transition to Seniority Dates V3 to ensure business continuity.

Moving to Seniority Dates V3 will provide users richer capabilities and more robust functionality. Additional Details are available at Seniority Dates Enhancements

When is the change?

Effective 23B, Oracle will no longer support Seniority Dates V2.

What's my next step?

• I’m on Seniority Dates V1, what’s my next step?
• I’m on Coexistence for Seniority Dates V1/V2, what’s my next step?
• I’m on Seniority Dates V2, what’s my next step?
• I’m on Seniority Dates V3, what’s my next step?

Where can I learn more?

• Update 20B What's New - IMPORTANT Actions and Considerations
• Help Center Topic: Implement Global Human Resources Guide - Considerations for Migrating to V3 Seniority Dates
• What’s New 23B

Error produced when I run diagnostic "Migrate to Version 3 of Seniority Dates"

• As of this document, our recommendation is to run the diagnostic with RUN MODE = COMMIT and Backup = No.
• Ref:https://docs.oracle.com/en/cloud/saas/human-resources/23a/faigh/process-to-migrate-seniority-dates.html#s20063048

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.