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

SAP Knowledge Base Articles - public

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


Error message received when attempting to create a Job Requisition from Position Management (Position Org Chart) if a Job Requisition field with type "Picklist" is included in the Business Rule Mapping.


SuccessFactors Recruiting Management - b1605


With b1605 (Q2 2016 release) SuccessFactors has provided a new method for integrating EC position management with Recruiting Management, which is based on the OData API for requisitions.

However this integration method has also shown some drawbacks in comparison to the SFAPI based method.


Customers may request the possibility to use a picklist on the requisition side that is mapped to and prefilled from the position.

If this is the intended scenario, the OData API will require you to map the picklist values from MDF to the optionID of the legacy picklist in RCM. In order to do so, you will currently need to define this mapping with the help of an additional object that contains both the code and the optionID value of the legacy picklist.
The mapping object needs to be setup and maintained. Whenever there is a new value in the picklist, you will need a new instance of the object. The MDF and the legacy picklist do not have to be manually kept in sync, as there is an automated way of doing so (see EC master guide, Q2 version, section 16.5 “Keeping ECV2 and MDF Picklists in Sync”).

The need to have this kind of mapping object shall go away in the not too distant future, when legacy picklists will be migrated to MDF picklists. You will then have the same picklist on both sides and thus there will no longer be a need for the mapping object.


Please find an example for such a picklist mapping:



To configure this in your system, execute the following steps:

i. Create the mapping object in Configure Object Definitions, with only one custom field which is called “optionID”.




ii. Create a new instance of this object for every mapping. For the mass creation of all values of one or several picklists, it may be best to use the MDF import for the object(s).



iii. Use the mapping object in the field mapping by performing a lookup via the external code.


See Also

2343638 - Unable to create Business Rules for Position Management to Recruiting Integration

2262815 - Succession Management: How do I migrate to or enable the MDF Position Model?

2079418 - Position Management - Employee Central



Position Management oData API Picklist Business Rule Job Requisition , KBA , LOD-SF-RCM-API , Webservices & APIs , How To


SAP SuccessFactors Recruiting all versions