Calculate Seniority Dates (v3) creates new rows/IDs in PER_SENIORITY_DATES_F without functional chan — Cloud Customer Connect
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

Calculate Seniority Dates (v3) creates new rows/IDs in PER_SENIORITY_DATES_F without functional chan

in HCM Extract 1 comment

Hi everyone,

we’re investigating why the Calculate Seniority Dates (v3) process creates new rows (new IDs) in PER_SENIORITY_DATES_F for existing employees even when there’s no functional change to the underlying data. In these cases, not only the LAST_UPDATE_DATE changes, but the CREATION_DATE appears reset and a new row/ID is generated, which then triggers daily false deltas in our HCM Extract (Changes Only) interface to SAP. This behavior causes unnecessary updates, downstream mismatches, and additional operational effort.

In the report, you can see that the ID changed, which is why the data appeared in the

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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