2227769 - Creation of a Requisition for Position with External Code Failed: fieldId is invalid - Recruiting Management

When creating a job requisition via Position Org Chart, error message is displayed:

"Sorry, the requisition cannot be created. Creation of a job requisition for position [Position Code] failed. Details: fieldID invalid"

SAP SuccessFactors Recruiting Management

There are a few possible root causes for this issue:

• The type of the fields which are mapped by the Position to Requisition Field Mapping Rule are not compatible between Job Requisition Template (RCM) and Data Model (EC). The format string value being passed from Postion may not have the same value in the picklist ID linked in the Recruiting field ID.
• The picklist ID used in RCM is not the same used in the Lookup Table created to map the picklist fields
• The option ID being passed through the Lookup Table is invalid (e.g. could be inactive, not pertain to the picklist in use)

For Cause 1:

Edit the Business Rule so that the rule is having only fields with the same type mapped.

A field defined in Job Requisition as type=”picklist” can only be mapped to a field which is also defined as picklist on EC Data Model. If you are passing the value as format text (%s), be sure that value being passed from position data is same with picklist ID. (e.g. The position data being passed is "administrative". The picklist label must have the same value as "administrative" not "Administrative"  or "ADMINISTRATIVE".

Please contact your Professional Services consultant or contact Employee Central Support Team for further assistance on setting up the rules.

For Cause 2:

If you are using the Lookup Table option that is described in the KBA 2361220 - How to map Picklist fields in EC Position Management to RCM Integration with oData API - Recruiting Management, then it's required to make sure that the picklist ID in the Lookup Table is the same one as used in the RCM Job Requisition Template.

NOTE: For MDF Picklists, RCM takes into consideration the picklist ID that is configured in the "Legacy Picklist ID" ID configured inside the Picklist ID. So, if post migration to MDF there are picklists where you see potential picklists with the same ID, e.g. in the list it has a picklist called picklistID and picklistID~%1 or picklistID~LEGACY, check for the Legacy Picklist ID to confirm which of these picklists RCM will take into consideration to use. To fix this issue, you can follow the steps from the KBA 2909791 - Picklist codes appended with suffixes "~%1", "~MDF" or "~LEGACY" - Post Picklist Migration.

For Cause 3:

This issue could be tied to Cause 2. In order to check the values, you have to check the option ID inside of the picklist in use to see if the values are correctly added to the lookup table and correct it as needed.

2361220 - How to map Picklist fields in EC Position Management to RCM Integration with oData API - Recruiting Management

2909791 - Picklist codes appended with suffixes "~%1", "~MDF" or "~LEGACY" - Post Picklist Migration

position, job, requisition, req, picklist, center, centre, mdf, id, invalid, org, chart, rule, business. , KBA , LOD-SF-RCM , Recruiting Management , Problem