Symptom
When updating/editing a user for some users making the changes, when saving there is an error received "Second Manager Cycle Detected. Please try again" however for other users making the same change they can save without error.
Environment
SAP SuccessFactors HCM Suite
Reproducing the Issue
Perquisites:
- Second Manager needs to be enabled and in use (see KBA - 2509740 - Second Manager Column is Missing in the Employee Export or UDF)
- There needs to be a cycle error in the second manager hierarchy (see KBA - 2211816 - Second Manager Cycle Detected. Please try again.) - (this can be any sort of invalid second manager hierarchy in User C second manager hierarchy - so an inactive second manager or a invalid loop in the second manager hierarchy for User C)
- Two different users (User A and User B) are required with permissions to make changes to the specific users (User C) data to trigger the error
Steps to Replicate:
- For example we are using the Login Method as the user data we will change
- Login or Proxy as User A (User A must have the edit permission for "login method" for a target population which includes the user you are the making the changes to - User C)
- User A must have the Employee Data > Second Manager (Edit) permission assigned where User C is included in the target population
- Go to User C profile and edit the Login Method - when submitting - error received "Second Manager Cycle Detected. Please try again"
- Login or Proxy as User B (User A must have the edit permission for "login method" for a target population which includes the user you are the making the changes to - User C)
- User B must NOT have the Employee Data > Second Manager (Edit) permission assigned where User C is included in the target population
- Go to User C profile and edit the Login Method - when submitting there is no error and changes save
Cause
Expected system behavior based on current design
Resolution
Only the User with the permission to update/edit second manager (Employee Data > Second Manager (Edit)) for the target user will trigger the validation check error if there is cyclic issue
**Please note - the recommended solution here is to ensure there is no second manager cycle error - if you are using second manager each user should have a valid active second manager without any loops anywhere in the hierarchy.
See Also
Keywords
Second Manager Cycle Detected, Second Manager, would become their own manager in the reporting line , KBA , LOD-SF-PLT-UIM , Employee Import Issues , Problem
SAP Knowledge Base Article - Public