Symptom
This KBA outlines the permissions required to view the following items:
- Compensation Statements
- Combined Statements
- Variable Pay Statements
- Variable Pay Individual View
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 Compensation
- SAP SuccessFactors Variable Pay
Reproducing the Issue
Once a cycle has completed for Compensation and Variable Pay, sometimes generated statements cannot be viewed from employee profiles
Resolution
- Below is a breakdown of each view and what is required when it comes to data-model configuration and Role-based Permissions (RBP)
- During this breakdown we will use the following hierarchy:
- In RBP we have the following selected for this hierarchy:
- Employee Data (requires target population)
- Variable Pay Personal Statement
- Rewards Statement
- Compensation Statement
- Employee Views (requires target population)
- Compensation Information
- Compensation Statement
- Variable Pay Individual View
Note: The labels of these portlets will vary as they can be customised
Compensation Statements
- Compensation statements use RBP as well as the option of defined roles at template level.
- If "default permission" is selected, it will follow RBP for statement view, else it will use the roles selected at template level
- The data-model is defined as follows:
- These are the roles which are selectable from within your plans Complete Compensation Cycle> Rewards Statements> Manage Statement Templates
- Here we have selected roles and only for the manager of the employee to see the statement:
- If a manager checks, they can see the statement in the profile
- The manager upwards will see it; however, the second manager will not
First Manager (EM & EM+)
Second Manager (EA)
- If permissions on the statement are updated to "Default Permissions", this is then determined from RBP and what is configured within employee views
Note
If "Default permissions" is selected, only RBP for "Personal Compensation Statement" will be check, which is under "Employee Data" given the correct target population.
Thus, the roles within the data-model have no impact
Combined Statements
- Combined statements can be controlled by RBP
- The prerequisites of this are as follows:
Enable "View generated Variable Pay and Combined Statements based on Role-Based Permissions" via Action for all plans > Company Settings > Manage Company Settings
- Ensure the standard element for combined statements is correctly enabled
- This can be checked in Manage Business Configuration > Employee Profile > Standard > personalCombinedStatement
- Grant permission for this element in RBP under Manage Data
Note
If this option is not enabled within action for all plans, then combined statements will follow the roles defined in the data-model
- In this example we have the following defined in the data-model when the Company Setting option is NOT enabled:
- This means only the employee's manager (EM) employees manager manager upwards (EM+) and employees second manager (EA) can see statements
- From the view of the manager (EM & EM+) we see the statement and so will the other defined roles
- The statement permissions/roles selected within the plans Complete Compensation Cycle > Rewards Statements > Manage Statement Templates are as follows:
- If the second manager (EA) selection is removed, the statement will no longer be visible for anyone in this role:
- If updating permissions to "Default permissions", this will look at the data-model, not what is within RBP
- Thus, the same roles above will still see the statement
Note
Changes in these permissions are dynamic
Variable Pay Statements
- Variable Pay statements can now follow RBP as well as template level roles
- To use this statement type on RBP, the option selected in Company Settings, as shown above in the "Combined Statements" section, will need to be enabled
- The following roles are within the data-model:
- Before generating statements for this plan, set the following permissions:
- With these permissions set the only people who can see the statement would be the employees and their manager upwards
- The second manager will not be able to see the statement in the profile:
First Manager (E, EM, EM+)
Second Manager (EA)
- An example would be to update the data-model and remove second manager (EA) as well as the employee (E):
- When accessing the employee's profile again, only the above roles may see the statement and NOT the second manager or employee
- If permissions are set to "Default permissions" then this follows RBP
- Historically, this would only follow the above roles similar to combined statements; however, this has been enhanced
Variable Pay Individual View
- Variable Pay individual view within the employee's profile is controlled by the data model roles as well as RBP
- The permissions we have in this example are as follows:
- From the employee's profile these roles will see the following:
Note the template name on People Profile here is not translatable and this will therefore show in English. This is current product design.
You cannot permission for whom the link shows for. For example, defining target population on the link and another for the portlet.
If you have access to the portlet then you will see the link, but the data behind the link is what is determined via RBP.
Please create an influence request should there be a request to enhance this feature.
- These roles will work in hand with the RBP permissions defined
- Once these elements are defined, the Individual view can be enabled as a view in RPB “Employee Views”
- Should you have permission via RBP to see the portlet but NOT be within the data-model roles, you will see the following page when selecting the Variable Pay Individual View link:
- The visibility of the Live Profile View can be controlled by the Variable Pay administrator throughout the Variable Pay process, even after Variable Pay forms have been created without updating the permissions
- This can be done within the plan via Plan Setup> Settings> Calculation Setting> Live Profile Visibility
- This is a dynamic option and the view does not depend on if the forms are completed or not
Note
Unless the standard data element has been defined and permissioned in the data model (using legacy permission rules as explained above), the Live Profile View will not populate.
Additionally this is not supported while using interpolability templates. This is noted in the guide
Check List
The following is a list of things to check should you encounter issues with viewing statements etc.
- Are worksheets completed?
- Have statements been generated?
- What permissions are defined for the generated statements under Complete Compensation Cycle > Rewards Statements > Manage Statement Templates? Default or template?
- If you are unable to see the Variable Pay Individual view, are the roles and permissions assigned correctly?
- Can statements be viewed in under Complete Compensation Cycle > Rewards Statements > Manage Statement Templates?
- Do you have statement suppression on? See KB article 2641834 - Compensation & Variable Pay - Suppressed Statements
- Users who should not see Variable Pay Individual view can see this section. If permissions are correctly assigned, is the individual view under Configure People Profile within a different employee view? For example, Compensation Information for which the affected users have access to? An option here would be to it into it's own employee view to permission
See Also
KB article 2641834 - Compensation & Variable Pay - Suppressed Statements
Keywords
SF, success factors, CMP, VRP, compensation statement permission, variable pay statement permission, combined permissions, CMP-10621, vpIndividualView, personalVarPayStatement, personalCombinedStatement, personalCompensationStatement, enable combined rbp, combined statements , KBA , LOD-SF-CMP-PS , Personal Statements , LOD-SF-VRP , Variable Pay Programs , LOD-SF-CMP , Compensation Management , LOD-SF-VRP-PS , Personal Statements , LOD-SF-VRP-LP , Live Profile View , How To