3472949 - IRT Data Anonymization: inconsistent Date Entries in 'Since' Fields"

• IRT Anonymization process add details in Married Since date field on target even if this information was not in use in Source.
• Married Since date set is prior to Date of Birth in anonymization process.

SAP SuccessFactors HCM Suite

Currently Data Anonymization Logic Design

Data Anonymization process to "Married Since" field is not customer specific, if the field is in use to any other user in source, the randomization process might populate it in target, even if users have it in blank in source.

Date of Birth is a separate logic from Married Since date:

"Date of Birth" uses the source user date to apply random and anonymize in target. This method replaces the actual date with a random one. For example, a DOB of 22-Oct-84 might be changed to 14-Nov-79.

For the 'Married Since' field (emp_personal_info), anonymization logic use predefined values, such as March 3, 1970. This could result in the 'Married Since' date being set before the individual's DOB after anonymization."

Engineering team analyze the possibility to change the logic, raising an internal enhancement process.

• Data Anonymization will check Married Since date is there or not (source). If it it is not present for a user then it will not populate the married since date in target.
• If it is already present (source) then we will populate the date as per actual logic and will validate anonymized value of Date of Birth, preventing to add dates prior to Date of Birth.

As this code enhancement system changes and pre-validation time before be applied, today a patch release date was not shared, new details about enhancement will be updated here.

2827300 - Data Anonymization feature in Instance Refresh - SuccessFactors - SAP for Me

TLS-31108, IRT, Data Anonymization, DOB, Married Since, Scramble, DA, logic, Refresh, INC8194577 , KBA , LOD-SF-PLT-IRT , Instance Refresh Tool , Bug Filed