2621016 - Creation of a job requisition for position **** failed. Details: The mapping field **** is entered in the rule to refer to a simple data type - Recruiting Management

When creating a job requisition from Position Org Chart, the following error is displayed: "Sorry, the requisition cannot be created. Creation of a job requisition for position **** failed. Details: The mapping field **** is entered in the rule to refer to a simple data type but the Job Requisition has no field with this name that refers to a simple data type."

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

SAP Success Factors Recruiting Management

A couple of causes could result in this error message:

• Field ID referenced in the business rule either does not exist or does not exactly match the Field ID defined in the template
• Field not present on the OData API Data Dictionary
• Mapping incorrect when using picklist
• Mapping the values into an Object

For each of the scenarios above we have a slightly different way to resolve:

Field ID referenced in the business rule either does not exist or does not exactly match the Field ID defined in the template:

1. Review the job requisition template and identify the correct Field ID defined for the field.
2. Verify that the Field ID exists and that its spelling and letter casing exactly match the value referenced in the business rule.
3. Update the business rule to use the correct Field ID.

Field not present on the OData API Data Dictionary:

1. Access OData API Data Dictionary, inside the Job Requisition entity
2. Check if the field is there
3. In case the field is not, access OData API Metadata Refresh and execute a Refresh.

Mapping incorrect when using picklist fields:

1. Access Position Management Settings, and access your mapping rule
2. Go to the field that is displayed on the error
3. Check if the mapping of that picklist field has the ".id" (Option ID) at the Requisition field. Since picklist fields are complex data types, the value must be assigned directly to the identifier of the picklist option.
   

Mapping field values into an Object:

1. Navigate to "Configure Object Definitions".
2. From the first dropdown, select "Object Definition", then choose the relevant object name.
3. In the object definition, locate "externalCode" in the "Database Field Name" column and review the corresponding value in the "Name" column.

The Name value may be "externalCode", "code", or another identifier depending on the object configuration. Enter this exact identifier, such as ".externalCode" or ".code", in the Requisition Field to ensure the mapping is configured correctly.

KBA 2171588 - SuccessFactors: OData API Metadata Refresh and Export

KBA 2532520 - Unable to find the recruiting entity from OData API Data Dictionary

simple, data, type, position, org, chart, create, requisition, creation, failed, mapping, field, OData, Refresh , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem