3526638 - Creating Job Requisitions when one Job Code is mapped to Multiple Roles in the Job Profile Builder - Recruiting Management

Since 2H 2024 Release, a single Job Code can be mapped to multiple Job Roles by creating a unique combination of the Job Code and a custom Employee Profile field. Specific configuration changes are required to ensure the correct value of the Job Role is associated with the Job Requisition.

SAP SuccessFactors Recruiting Management

The following integrations need configuration changes to determine the correct Job Role association with a Job Requisition when using a one-to-multiple mapping of the Job Code to Job Role.

• Creating job requisitions using Position from Position Org Chart.
• Creating job requisitions from Succession Org Chart.
• Creating job requisitions using OData API.

For more information on how to configure this feature, please refer to User Assistance Documentations on the Help Portal:

• Job Code Association with Multiple Job Roles
• Creating Job Requisitions when one Job Code is mapped to Multiple Roles in the Job Profile Builder
• Associate a Job Profile to Job Requisition by Providing JobRole externalCode Using OData API

Expected behaviors:

1. If the Job Requisition template has both the jobCode and jobRole fields, the system checks if the Job Code is associated with the Role.
   Here are sample error messages when the association is not found:
   
   
   • Position Org Chart - "Sorry, the requisition cannot be created. Creation of a job requisition for position xxxxx failed. Details: The jobCode is invalid because it is not associated with the given jobRole. with the index 0"
   • OData API - "[COE0018]The jobCode is invalid because it is not associated with the given jobRole. with the index 0"
   • OData API - "The given jobRole is not associated with the jobCode. Provide a jobCode associated with the given jobRole. with the index 0"
     
     
       
2. When updating the jobRoleEntity, it will not automatically pull the Job Code associated with the Role into the job requisition details.
3. When only updating the jobCode without providing the jobRoleEntity, it will pick up a random Role associated with the Job Code.
4. Position Org Chart - If the business rule cannot find a matching value in the custom field between the Position and the Role & Job Code Mapping Entity, no error will occur and it will pick up a random Role associated with the Job Code.
5. Succession Org Chart - There is a requirement of setting the same field id in both the Employee Profile and the Position object if Succession nomination method is set to MDF Position. However, when not using the same field id, no error will occur and it will pick up a random Role associated with the Job Code. 

• KBA 2719720 - How to map the Job Role when creating Job Requisitions using Position Org Chart - Recruiting Management
• KBA 2520200 - Incorrect Job Profile associated with Job Requisition created via Position Org Chart - Recruiting Management
• KBA 3523450 - Upsert JobRequisition with jobRoleEntity "The given jobRole is not associated with the jobCode. Provide a jobCode associated with the given jobRole. with the index 0" - Recruiting Management

User Assistance Documentation Links:

• Job Code Association with Multiple Job Roles
• Creating Job Requisitions when one Job Code is mapped to Multiple Roles in the Job Profile Builder
• Associate a Job Profile to Job Requisition by Providing JobRole externalCode Using OData API

2H2024, RCM, JPB, Job Profile, Job Requisition, OData API, jobRole, jobRoleEntity, Job Code, Position, Org Chart, Succession , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-POS , Position Integration , How To