SAP Knowledge Base Article - Public

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

Symptom

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.

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

Environment

SAP SuccessFactors Recruiting Management

Cause

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.

Resolution

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:

picklist_oData.JPG

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

  1. Create the mapping object in Configure Object Definitions, with only one custom field which is called “optionId”:
    picklist_oData1.JPG
  1. 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):
    picklist_oData2.JPG
  1.  Use the mapping object in the field mapping by performing a lookup via the external code:
    picklist_oData3.JPG

    NOTE: If the environment is Picklist Center, please create the rule using the field in RCM dot id, for example "filter1.id" in the screenshot below:
    picklist center.jpg

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

2780212 - Create Requisition from Position field invalid error for Picklist field - Recruiting Management

2780148 - How to map a picklist from EC Position to Recruiting Requisition - Recruiting Management

2885113 - How to find association fields in a lookup rule for Position Management

2878293 - Error when mapping picklist or object fields from EC to RCM through Position Management

Keywords

Position Management, oData, API, Picklist, Business Rule, Job Requisition

, KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RCM-INT , Integrations & Intelligent Services , How To

Product

SAP SuccessFactors Recruiting all versions