2829023 - Unable to create requisition via Position Org chart due an error with an invalid external code - Recruiting Management

When trying to create a job requisition via Position Org Chart, the following error will be received:

"Creation of a job requisition for position #### failed. Details: '##' is/are invalid values of 'field-id'. Enter valid external code"

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. Log into the instance
2. Go to Position Org Chart
3. Try to create a new job requisition using any position
4. Then the following error will be received: "Creation of a job requisition for position #### failed. Details: '##' is/are invalid values of 'field-id'. Enter valid external code"

As of now, we have identified two possible causes:

1. The error was caused by an incorrect mapping of Pay Grade field to a Job requisition field. You will need to verify that the correct fields were defined on the Position to Job requisition mapping rule.
2. The error is caused due to the mapping in the rule. When selecting the fields you want to map the requisition fields to (the source), you need to select them from a dropdown, not typing it in as we do for Job Requisition's fields. The screenshot below shows the incorrect configuration:

The resolution to each type of cause above mentioned are below described.

CAUSE 1

1. To verify the correct mapping, go to the following:
1. Access Provisioning
2. Go to Import/Export Corporate Data Model XML
3. Export the XML and open it
4. Search for the label/external code defined for the "payGrade" field. See an example below:

<hris-element id="payGrade">
<label>Salary Band</label>
<label xml:lang="en-US">Pay Grade</label>
<hris-field max-length="32" id="externalCode" visibility="both" required="true">
<label>Salary Band</label>

From here, we can see that the externalCode for the payGrade is labeled as "Salary Band".

Now, in the Job Requisition Template look for the same object payGrade (which label in the data model is actually called "Salary Band"):

For example: <field-definition id="custom_salaryGrade" type="object" required="false" custom="true" object-type="payGrade">

To fix the mapping, now, follow the steps below:

1. Go to Admin center >  Position Management Settings > Integration
2. Open the "Rule for Mapping Fields Between Position and Job Requisition"
3. Verify these fields were mapped:

Note: Each Field-id are case sensitive, the same cases should be used from the templates vs. the field mapping rule.

CAUSE 2

When creating the rule mapping, make sure to use the Position's option and not the text field and manually insert the values, otherwise, the rule won't work. The rule for issue reported in cause 2 should be configured as follow:

2501144 - Position to Job Requisition Rule Definition for the Job Requisition FO/GO Object Fields

invalid external code, creation of job requisition failed, enter valid external code, position org chart job requisition fails, invalid values. , KBA , LOD-SF-RCM , Recruiting Management , Problem