You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Seniority Dates were not getting calculated for some users from past 2 years

Summary:

Hi everyone,

We have scheduled "Calculate Seniority Dates" in our instance but have noticed that for few employees it is not getting calculated and it is showing as seniority dates were last calculated on DD/MM/2024.

We then ran Seniority Date Records Violating Unique Constraint - Report with person number parameter for one employee and noticed there is a data corruption. We then ran Seniority Date Records Violating Unique Constraint - Correct in Validate and COMMIT mode and the issue is resolved for that one employee. This process deletes any manual adjustment days and correct the record.

Similarly we ran a Seniority Date Records Violating Unique Constraint - Report without person number as a parameter and identified there are more records exists with corruption and the report output shows Report exceeds the maximum number of rows allowed so it has been truncated. And there were many manual adjustments happened on these records and the data gets deleted for all population in HCM if we run Seniority Date Records Violating Unique Constraint - Correct in Validate and COMMIT modes.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!