2449731 - Warning message in Configure Reportable Custom Fields - Recruiting Management

Warning message is appearing under Configure Reportable custom Fields, on configuring the custom field under the section being configured:

"Warning: The "FIELD ID" custom field is mapped to a different Column Name in the "Candidate/Application" section. Any common custom field must be mapped to the same "Column Name" across different sections. When you incorrectly map a common custom field, it could lead to an incorrect report and these fields will not be sortable on the Candidate Workbench."

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

SAP SuccessFactors Recruiting Management

The custom field is mapped in two different sections, but in different Extended Table Column Name. E.g.: customField1 and customField2 are mapped in Application and Candidate sections, but in Application it's mapped in Text10 and Text11, respectively, and in Candidate it's mapped to Text1 and Text2).

Any common custom field between two templates must be mapped to the same Extended Table Column Name. Following the example above, the fields customField1 and customField2 in both sections should be Text10 and Text11 respectively.

Note that, although the warning message is displayed, the incorrect mapping of the reportable fields can be saved for correction later. However, if you are ignoring the warning message, you might face issues like not able to sort the field in Candidate Summary page when the Extended Table Column Name is different in Candidate and Application tab/column for common Custom fields.

2081508 - Custom Reportable Recruiting Fields - Recruiting Management

error, warning, display, options, application, candidate, field, id, type, extended, table, column, name, , KBA , LOD-SF-RCM , Recruiting Management , Problem