Symptom
The purpose of this article is to detail how to configure Succession Management permissions for MDF Position nomination method + RBP permissions.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Succession Management
Resolution
MDF Position Permission process works similarly to legacy positions with RBP, with the addition of Object Level Permissions. First, we need to set the permissions that are not specific to MDF:
- From Admin Tools
- Set User Permission
- Manage Permission Roles
- Create/Edit the desired Role
- Click on "Permission..."
Within the same Permission Role, you may set all Succession Permissions, both the ones requiring a Target Population and those that do not require it.
You can verify the Permissions that require a Target Population to be set by checking if that specific permissions have a "†" character next to it.
After selecting the desired permissions on this page, click on done and scroll down the page to set the Target Population of this role. Here you will select to who these Permissions will be given (in this example. to the group "Payroll Admins, Admin, EC Admins") and the Target Population that this group will have for the selected permissions — as an example the population which will be included in the Matrix Grid Report.
After the above section is completed, you can configure the Object-specific permissions over the Position object. When using MDF Positions, granting Position object-level permissions in the same role as the Succession Planning/Approval/Management Permissions makes the Succession related permissions apply to the Position target population as well (besides the user target
population). So the Position object permissions will help you to grant Succession Planning/Approval/Management permissions over Positions that are vacant (TBH positions).
At a minimum, "View Current" permission on the Position Object is required for the Succession related permissions to apply to the Position target population.
It's important to highlight that when you have Succession Planning/Approval/Management permissions in the same permission role as the Position object permissions, the Succession Planning/Approval/Management permissions will apply to both the user target population and to the Position target population. Please see the below diagram that illustrates this.
For example, if you have User A in your User target population, but User A's position is not within your Position target population, you'll still be able to add successors to User A's position, but you will not be able to show/edit the details of the position. The other way around is very similar: if you have Position Z in your Position target population, but the Position Z's incumbent is not within your user target population, you'll be able to both add successors to and show/edit the details of Position Z.
As another example, if a user has set up Succession Management and Matrix Report Permissions and Succession Planning Permission with the target population of only self, but under the Position object target population he has access to all positions, he will be able to nominate and see talent information for all positions.
Note: Best practice is to have only one position target population associated to a user's Role Based Permissions, due to the fact that MDF Nomination Method uses both Position and user Target Population.
See Also
Granting Permissions for Succession Planning | SAP Help Portal
Position Target Populations for MDF Positions | SAP Help Portal
Keywords
SuccessFactors, SF, SCM, Succession, Succession Management, Position, MDF Position, RBP permissions, Target Population, Position Object. , KBA , LOD-SF-SCM-ADM , Admin Center, RBP, Permissions and Settings , How To