2479444 - Route Map is incorrect when creating a Job Requisition from Position Org chart - Recruiting Management

When you are creating a requisition from Home > Recruiting, the route map followed in the requisition approval process is as designed. But when you create a requisition from the Position Org chart using the same requisition template, some of the steps in the same route map are skipped, and they're not displayed in the requisition.

Example: You have a pre-defined Route Map in Recruiting with the following path Hiring Manager > HRBP > Recruiter.

When you create a requisition from Home > Recruiting, the requisition follows this route map for the approval process.

However when you create a requisition from the Position Org chart, the route map is changed to HM > Recruiter, skipping HRBP.

• SAP SuccessFactors Recruiting Management
• SAP SuccessFactors Employee Central

1. Go to Position Org Chart
2. Search for the position you wish to create a job requisition
3. Click on Create Job Requisition
4. The job requisition is created, and when you open it you see that steps of the route map is missing

• The operator is not mapped in the Position to Requisition rule (following the example provided in the symptom, the rule is not passing over a value to the HRBP role).
• The operator in the Position to Requisition rule is sending a fixed value, which is an inactive user or is an invalid user
• The role part of the route map is an associated operator, like Hiring Manager's Manager (GM), and no value is passed over to the Hiring Manager field (G)

For Cause 1:

It is required to map the operators in the Position to Requisition rule in order to pull them into the route map since these users are defined prior to the creation of the job requisition, in the Requisition Creation page, where you fill the job title and the due date.

For Cause 2:

The users in the route map must be active users in order to be able to route the job requisition for approval. If the user is inactive, then the user won't be assigned to the operator role. If the user is not part of the recruiting group that the operator rule is restricted to, then they won't be able to be assigned to the operator role.

For Cause 3:

Since associated operators are not real operators to Recruiting, it is required to passed the Recruiting operator a value in order for the system to pull the associations. Otherwise, the system won't know who to assign as the associated operator.

If valid users aren't coming over from the EC position correctly to the requisition, then the route map will skip the missing user step and will be shortened to only include the roles that are present in the requisition when it is created. This is working as per design.

route, map, position, org, chart, skip, step, missing, load, wrong, non, sync, not, synced. , KBA , LOD-SF-RCM-POS , Position Integration , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem