2081508 - Custom Reportable Recruiting Fields - Recruiting Management

• Data missing/Incorrect data fetched in reports for custom Fields in Recruiting Management
• This KBA explains how to report on Custom Fields in SuccessFactors Recruiting using Ad Hoc (Table) and Canvas (ORD) reports

SAP SuccessFactors Recruiting Management

Note: Provisioning access is required. Please reach out to your Implementation Partner for assistance.

• To make a custom field reportable, you need to map them to Custom Reportable Recruiting Fields in Provisioning.
• When adding a new custom field it needs to be configured in the XML template and mapped to match what is in the template.
• Then a sync must be done in order for these to be reportable. Hence, when adding new fields in Provisioning they must match what is in the configuration.

For example:

The following field must be reportable: <field-definition id="locale" type="picklist" required="true" custom="true">. Then, what needs to be done is:

1. The fieldID and the field type in Provisioning must match what is in the XML.
2. Map this under the Job Requisition tab in Provisioning in the picklist column, inserting the fieldID. In the case above, 'locale'.
   If the type was text in the XML, it would go in the text column in provisioning. Mapping under the wrong type can cause problems with the sync: a field configured as a picklist and mapped in a text field column could cause random reporting and/or sync errors.
3. Scroll down and click Save.
4. After saving the new field, you will select 'Synchronize Selected Field Data' tab. 
5. This job syncs the information currently existing in the system to make it reportable in Reporting. Sometimes, it's needed to re-trigger this job in order to have the values displaying in the reports.
6. You will get a message back in provisioning when it goes through, then, after synchronizing, you will get an e-mail confirming results.
7. If you do not get an e-mail back confirming that the sync was successful it may indicate a problem.

IMPORTANT:

• Make sure custom reportable fields are only mapped once in provisioning. Having the same field mapped as a date and also as a text field/picklist field could cause sync problems.
• Mapping with a nonexistent field definition ID, mapping duplicates/mapping in the wrong field type can cause random troubles in ad hoc data and/or break the sync.
• If you have a field that is not retrieving/displaying information when creating a report but you do have information on those fields, please ask your Implementation Partner in order to have the Synchronize Extended Field Data triggered again. This job is the one that will sync the information currently existing in the system to make it reportable in Reporting. Sometimes, its needed to re-trigger this job in order to have the values displaying in the reports.

2315734 - How many reportable custom fields can be set up for one instance - Recruiting Management

sf, success factors, RCM, field, ORD, ANA, rpt, reporting, canvas, table, center, v2, secured, adhoc, report not showing value, report not displaying data , KBA , LOD-SF-RCM-REP , Reporting & Analytics, Data Imports & Exports , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , How To