Compensation statements RBP

[SnehaK1]

Hi,

Current process:

Till now business have been opening up the statements of new campaign first to HR Manager, then to Manager and then to employees. This was managed via Manage statement templates > Manage permissions > Change permissions for who can view generated statements.

Requirement:

For this year campaign, business had a requirement that we should be able to open the statements as per RBP permissions to HR population only at first step. (Manage statement templates > Manage permissions > Default permissions.), but when we open the statement as per RBP it is likely to give permissions to all existing users (including non HR population) who are having permissions to statements and not only to the HR managers as required by business.

Kindly let us know if this requirement can be met. If yes, how?

Thanks,
Sneha

[LisaBranham]

Our company controls the Compensation Statement access via the Permission Roles. Although this removes the Compensation Statements access entirely during this process (which affects historical statements), this is a short enough timeframe that it has proven to be worth it to us to do while validating and preparing for leaders and employees to view them. We also remove the Compensation Information portlet security entirely from employees just before the push to EC until discussions are completed with Leaders.

[Neeraj_Jain]

Hello snehakalburgi_01,

Please check below SAP Note. Hope it's clarifies your query.

https://userapps.support.sap.com/sap/support/knowledge/en/2767375

2767375 - Compensation & Variable Pay - Statement Permissions & Variable Pay Individual View

Regards,

Neeraj Jain

[xavierlegarrec]

snehakalburgi_01

You need to remove permissions from "all" roles otherwise you will have the conflicts you mention and there is no way around that. The only workaround I can think of is placing the statement portlet in its own section this way there are two levels to control visibility and you would hide the whole section for all temporarily without impacting the statement permission itself. You could have a dedicated role for this with different target scopes based on job relationships and turn on the relevant ones one by one.

All the best

Xavier