SAP Knowledge Base Article - Public

2081508 - Custom Reportable Recruiting Fields - Recruiting Management

Symptom

Custom Reportable Recruiting Fields need to be mapped 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 and then a sync must be done in order for these to be reportable.  When adding new fields in Provisioning they must match what is in the configuration; mapping with a nonexistent field definition ID, mapping duplicates or mapping in the wrong field type can cause random troubles in adhoc data; and/or break the sync.

Environment

SuccessFactors Recruiting Management - All versions

Resolution

  • The field definition ID and the type have to match what is in the XML; See below for an example of a custom field from a job req:
    <field-definition id="locale" type="picklist" required="true" custom="true">

 

  •  You would map this under the Job Req Tab- as locale- in the picklist column.

    If the type was text in the XML; it goes 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 could cause random reporting and/or sync errors **.

     
  •  After saving the new field – you will select “synchronize selected field data” (you may have to select that twice- you will get a message back in provisioning when it goes through and you will get an email confirming results).

     
  • If you do not get an email back confirming that the sync was successful it may indicate a problem.

    ***All req templates need the custom fields configured the same and all application templates need those custom fields configured the same and mapped accordingly to be reportable.  Having a field configured as a text type in one req template and a picklist in the other req template can cause problems with the sync if you want that field to be reportable.  The same is the case if there is more than one application template using custom reportable fields.***

  • Make sure the custom reportable fields are only mapped once in provisioning – having the same field mapped as a date and also as a text field or picklist field could cause sync problems.

    <field-definition id="locale" type="picklist" required="true" custom="true">

 

Keywords

Configure Reportable Custom Fields

Custom Reportable Recruiting Fields Custom Reportable Fields , KBA , sf configuration , sf recruiting reports , LOD-SF-RCM , Recruiting Management , How To

Product

SAP SuccessFactors HCM Core all versions