SAP Knowledge Base Article - Public

2341235 - Data Privacy Consent Statement - DPCS 1.0 - DPCS 2.0 - Recruiting Management

Symptom

The Data Privacy Consent Statement allows customers to present a candidate with a notification detailing how the customer handles the candidate’s personal data. Candidates must accept this statement before entering their data.

There are two versions of the Data Privacy Consent Statement configuration:

  • DPCS 1.0 allows customer to provide a data privacy prompt for internal and external candidates in the candidate's preferred language. (Old Version not supported anymore)
  • DPCS 2.0 allows customer to provide a country-specific data privacy prompt for internal and external candidates, in the candidate's preferred language.

This Knowledge Base Article is a Master Knowledge Base Article for DPCS knowledge base - it provides links to DPCS configuration guide for both versions of the Data Privacy Consent Statement and summarizes known issues caused by misconfiguration.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SuccessFactors Recruiting Management (RCM) - All versions

Resolution

Please refer to the below Knowledge Base Articles for more information regarding DPCS 1.0 and DPCS 2.0

DPCS 1.0:

KBA Description
2341230

DPCS 1.0 - how to enable version 1.0 of Data Privacy Consent Statement and how to set up privacy statement - Recruiting Management

This Knowledgebase Article explains how to enable and set up Data Privacy Consent Statement version 1.0. It also explains how to report on DPCS 1.0 approval.

2148489 How to setup Data Privacy consent statement admin permissions for recruiting RCM DPCS 1.0

Note: Version 1.0 is not supported anymore. For new implementations, please enable version 2.0.

DPCS 2.0:

KBA Description
2341240

DPCS 2.0 - how to enable version 2.0 of Data Privacy Consent Statement and how to set up privacy statement - Recruiting Management

This Knowledgebase Article explains how to enable and set up Data Privacy Consent Statement version 2.0. It also explains how to report on DPCS 2.0 approval.

2103927 Can I show “Country of Residence” when creating an external candidate account?
2341323 Error: Assertion failed: DPCS country list is empty - Recruiting Management
2249799 Switch back to DPCS 1.0 from DPCS 2.0 - Is it possible to switch back to DPCS 1.0? What are technical prerequisites to switch back to DPCS 1.0?
2321135 Error Message: "Cannot find valid dcps for the dpcs type of 1" - error appearing after DPCS 2.0 is enabled, but no privacy statement is configured yet.
2234728

DPCS 2.0: Legal Minimum Obligation Period settings - When DPCS 2.0 is enabled, Legal Minimum Obligation Period option becomes available.

This KBA explains in detail when Minimum Obligation Period applies and how to modify the settings

2233613 When will the candidate be forced to accept the DPCS 2.0 statement once again?
2176660 The status triggerred e-mail notifications can be sent out only to existing candidates - setting up a template in Edit Applicant Status Configuration won't trigger any e-mails. This is a known product limitation.

 

UPDATE: B2005 release 

NOTE: The data segmentation feature is enabled for only selected customers in 1H 2020. The date of universal upgrade for all customers is to be decided.

You can now add a custom field to your Data Privacy Consent Statements. With this field, you can extend the standard statements to include custom-defined information. Required priority is “Type->Customized field -> country”

Aside from the Countries/Regions field, only one from the list (given below for B2005) can be used as customized field to create or filter Data Privacy Consent Statements.

  • LegalEntity
  • BusinessUnit
  • Division
  • Department
  • MarketingBrand(MDF)

For those five fields, map to internal user or external user included, backend is string(internal) or number(number).

Change on DPCS customized field:

  • If change type, all related DPCS will be removed, meaning that customer lose all DPCS that is used previously defined customized field.
  • Clear message and confirmation will be given, in order for customer to notify that all related DPCS will be permanently removed
  • Change on DPCS customized field doesn't happen often, thus design of configuration should not be easy access

For custom field configuration, kindly reach out to your Partner or SAP Professional Service.

NOTE: Although the feature can be enabled now in Admin Center > Company Settings > Platform Feature Settings, the 'Custom Field Name' column is empty as this feature is not fully implemented in Recruiting Management.

In DPCS display page, if customized field is not turned on, customized field should not be displayed. If the customized field is turned on, there will be an extra column with the name of customized field. For DPCS type that customized fields applys, value should be number of customized field value selected. Otherwise it should be empty or indication of NONE value.

DPCS Custom.JPG

See Also

Enabling the Data Segmentation Field of Recruiting Data Privacy Consent Statements

Keywords

Data Segmentation field, DPCS, Data Privacy Statement, Data Privacy Statement Custom field , KBA , LOD-SF-RCM , Recruiting Management , How To

Product

SAP SuccessFactors HXM Core all versions ; SAP SuccessFactors Recruiting all versions