3786995 - Agreed to Privacy Statement Report Discrepancy - Recruiting Management

The report for Agreed to Privacy statement between Scheduled File Output Integration using entity Candidate and DPCS Statement Log is showing different result.

SAP SuccessFactors Recruiting

1. Go to Integration Centre.
2. Create Scheduled File Output Integration using entity Candidate.
3. Select the necessary field (name, candidateID and agreedToPrivacyStatement).
4. Then go to Data Privacy Statement.
5. DPCS statement and select History.
6. Select the most recent version and view Log
7. Download the report
8. Search for a sample Candidate to compare between the reports
9. Integration Centre report shows the agreedToPrivacyStatement as False while the DPCS log shows as Accepted.

This is an expected behavior due to either of the following reason.

• For anonymized candidates, agreeToPrivacyStatement always evaluates to False, regardless of any historical DPCS acceptance (dpcs_acknowledge). Although the DPCS Statement log may show an earlier acceptance (e.g., when the candidate first created an external account), once the candidate is anonymized, Integration Centre reports agreeToPrivacyStatement as False due to anonymization.
• If candidates accepted the external privacy agreement as external candidates and later became internal users, Integration Centre attempts to locate an internal DPCS acceptance. When no internal DPCS is configured or accepted, agreeToPrivacyStatement is reported as False. In scenarios where internal DPCS is enabled, configured, and accepted by the internal user/candidate, the integration report will show True.

• 2082213 - Is it Possible to Report Against User Who Accepted or Declined DPCS - Recruiting Management
• 2646469 - How to report on candidates who accepted the Data Privacy Consent statement while creating the candidate profile

DPCS, data privacy, statement, report, consent, history, data, INC31485473 , KBA , LOD-SF-RCM-REP , Reporting & Analytics, Data Imports & Exports , Problem