This article describes the steps on how to address the errors when uploading or updating Recruiting Templates because of the sensitive tag. This error may show even if you are not directly changing the fields with sensitive tags in question, e.g., gender or race.
Error: The field "gender" cannot be configured as sensitive="false" as it is set to sensitive="true" in other templates (job application/candidate profile templates).
Error: The field "race" cannot be configured as sensitive="false" as it is set to sensitive="true" in other templates (job application/candidate profile templates).
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Cause: The fields in question, e.g., gender and race are no longer considered as a sensitive fields so you cannot set them or retain their sensitive tag to "true." However, at the same time, the system would error out if you change their sensitive tag to "false" because in the Manage Data they are still set as sensitive fields.
Resolution: Remove the sensitive fields in Manage Data. This would not remove the fields in the template, it would just remove the sensitive tags altogether.
a. In RBP > under MDF Recruiting Permissions > Recruiting Sensitive Personal Data Field List > View/Edit/Import/Export is checked (All except Field override is checked).
b. In RBP > under MDF Recruiting Permissions > Recruiting Sensitive Personal Data Field List.spdFieldList > All except Field override is checked.
c. Then in Manage Data > Search for Recruiting Sensitive Personal Data > RCM_SENSITIVE_FIELDS > remove your fields from the list.
Recruiting Management, RCM, Error, sensitive, gender, race, application, permissions , KBA , LOD-SF-RCM-APP , Applicants and Job Applications , How To