How to Change V3 Seniority Dates Rule Configuration
You can change the version 3 (V3) seniority rule configuration only if transactional data isn’t already generated for a V3 seniority date rule.
Use the Seniority Dates V3 - Remove Seniority Dates Transaction
Data diagnostic process to change the version 3 (V3) seniority rule
configuration by deleting transaction data for the selected seniority rule. You can
change the seniority configuration for a single seniority rule even if it’s used in
the calculation.
Note: The V3 seniority rules setup doesn’t allow the configuration
to be changed for a seniority rule if transaction data exists for the
rule.
Diagnostic Process Details
This table describes the diagnostic process:
| Diagnostic Test Name | Description |
|---|---|
| Seniority Dates V3 - Remove Seniority Dates Transaction Data | Remove transaction data for seniority dates version 3. Once this process is completed, you can make configuration changes for the selected seniority rule. |
The diagnostic process can be run only for a single V3 seniority rule which can be
active or inactive. The test can be run in these two modes:
- Validate: The seniority rule transaction data is not deleted in this preview mode.
- Commit: The seniority rule transaction data is deleted for the selected rule.
When the process is run in the Validate mode, user can choose to automatically
generate manual adjustments in the HCM Data Loader format. The adjustments can be
loaded back after the configuration change, hence making the overall process
simpler.
Note: The application generates the HCM Data Loader output in the
process log file, and generates only in the Validate mode.
These are the steps to change the configuration for a V3 seniority rule:
- Run the Seniority Dates V3 - Remove Seniority Dates Transaction Data process in Validate mode and generate the manual adjustments in the HCM Data Loader format.
- Verify the results.
- Run the Seniority Dates V3 - Remove Seniority Dates Transaction Data process in Commit mode. This will remove the transaction data, and you can make configuration changes in the seniority rule.
- Perform the configuration changes for the seniority rule you want.
- Run the Calculate Seniority Dates process for the selected seniority rule.
- Load the manual adjustments using HCM Data Loader with the data generated in step 1.
- Run the Calculate Seniority Dates process for the selected seniority rule.
You can migrate V1 and V2 seniority dates to V3 seniority dates in one go and choose to create your V3 seniority rules as cumulative or non-cumulative when migrating from V2. Also, you can change the seniority configuration for a single seniority rule even if it’s used in the calculation.
For more information, see the following documents:
- Self-Service Data Integrity Framework for Employment Flows - Part 1 (Doc ID 2548287.1) > Migrate from V3 to V2 or V1 - Correct on My Oracle Support
- Seniority Dates - Troubleshooting Seniority Dates - Frequently Asked Questions (https://community.oracle.com/customerconnect/discussion/631046) on Customer Connect.