Seniority Date Versions

You can manage the seniority of workers using V1, V2, or V3 versions of the Seniority Dates functionality. This table describes these versions:

Version	Description
V1	Seniority dates that are managed using the Work Relationship task are referred to as V1 seniority dates. You can only manage the Enterprise Seniority Date and Legal Employer Seniority Date using V1 seniority dates. V1 seniority dates are stored in the PER_PERIODS_OF_SERVICE table.
V2	Seniority dates that are configured using the Configure Seniority Dates task without using advanced configuration options are referred to as V2 seniority dates. You can configure multiple seniority dates as per your requirement. These seniority dates are managed using the Seniority Dates task. V2 seniority dates are stored in the PER_SENIORITY_DATES table. Note: You run the Populate Seniority Dates ESS job to initially populate the seniority dates. After this job is run, you don't need to run any other scheduled process.
V3	Seniority dates that are configured using the Configure Seniority Dates task and advanced configuration options are referred to as V3 seniority dates. You can configure multiple seniority dates as per your requirement. These seniority dates are managed using the Seniority Dates task. V3 seniority dates are stored in the PER_SENIORITY_DATES_F table. Note: The seniority dates aren't calculated during run time. You must run the Calculate seniority Dates process to calculate seniority dates. You need to schedule this process because V3 seniority dates are populated only after the process is completed.

For more information, see the document Seniority Dates - Comparison between Different Seniority Dates Versions (https://community.oracle.com/customerconnect/discussion/631037) on Customer Connect.