2552433 - 'JobRequisitionOperator has no such field' error occurred when creating job requisition via Position Org Chart - Recruiting Management

'JobRequisitionOperator has no such field' error occurred when creating job requisition via Position Org Chart.

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

SAP SuccessFactors Recruiting Management

1. Home > Position Org Chart
2. Search for position > Create Job Requisition > Create
3. Error will occur 'Sorry, the requisition cannot be created. Creation of a job requisition for position failed. Details: The mapping field recruiter is entered in the rule to refer to the field usersSysid of OData object JobRequisitionOperator, but the object JobRequisitionOperator has no such field.'

Note: Operator is recruiter for this example.

1. Wrong data field specified in the business rule.

Common misspellings:
<operator>.userSysId     (it should be 'users' and not 'user'.)
<operator>.usersSysid    (it should be capital 'I'.)

The configuration of business rules is case sensitive and it should follow the Property Name according to OData API Data Dictionary.

• Entity Name: JobRequisitionOperator
• Property Name: usersSysId

2. Adding the word 'Name' after the operator role. 

For example:
sourcerName.usersSysId
recruiterName.usersSysId (it should be sourcer.usersSysId or recruiter.usersSysId)

1. Check the rule configuration for the operator field.
2. Change the field to usersSysId to resolve the issue.
3. Remove 'Name' from the Requisition Field definition. 

Example:

KBA 2878365 - Position Management in Recruiting - Implementation Tips & Tricks from Support - Recruiting Management

userSysid, usersSysId, Operator, Position Org Chart, Rule Configuration, Job Requisition, mapping, user , KBA , LOD-SF-RCM-POS , Position Integration , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem