- Performance Management
- Main cause is when the user was inactive in the system at the time the form was created or routed. The SuccessFactors Application will automatically skip any inactive user in a route map at the time the route map is created, during a manager change, or when routing, so while an employee may be set as active today, at the time of the routing they were inactive and therefore skipped in the current route map.
- Permissions, RBP Permissions: Make sure the user has been granted all required permissions to access the system. If they lack permissions to login then the system is intelligent enough to know this and will therefore skip that user to prevent the form from becoming stuck with someone that can't access it.
- The other possible cause is that a new managers being hired into the system via the user data import and the system saw the new manager as inactive because the employee came before the new manager in the order of the employee import.
- Solution: Add user(s) to the default user group, then route the existing route map to the correct steps.
- The Manager only implementation check box was turned on for one or more user data imports, inactivating all non management users.
- See related solution: Admin Tools: Route Maps - Skip route map step if any user is missing.
- You can usually correct any issues like this by routing the form back using Admin Tools > Route Document. If your user is active you will see the route map correct itself. You may need to route it back to a step prior to the one that had the issue.
KBA , sf routing maps , LOD-SF-PLT , Foundational Capabilities & Tools , LOD-SF-PM , Performance Management , Problem
SAP SuccessFactors HCM Core all versions