3144392 - "Alternate Route User Step" Step When Creating Job Requisition via Position - Recruiting Management

When creating a Job Requisition through Position Management, a specific step of the Job Requisition approval is replaced by "Alternate Route User Step".

"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

This behavior will occur when there's a specific role in the Route Map but the user is not provided through the Position to Job Requisition mapping.

This will happen when the specific role in the Job Requisition is not defined as required or the role is required but the rule contains isDraft equals true (isDraft will not validate if a required field is not being passed through the mapping).

Since it's required to have a user approving the Job Requisition, the system will alter the existing step by a custom step (U) and add a user to it.

This behavior is caused by a misconfiguration. Make sure to map all users to the roles defined in the Route Map, otherwise this behavior will happen and we can't determine which user will be added to the custom step.

For more details about the "Alternate Route User Step", please refer to the KBA: 2077339 - Alternate Route User Step - U Step - Performance Management.

For existing Job Requisitions, you can find the custom user through the information icon over the custom step:

Alternate, Route, User, Step, missing, cannot, can't, approve, changed, change, step, approval, map, position , KBA , LOD-SF-RCM , Recruiting Management , Problem