Understanding the rollup hierarchy method of planning

[xavierlegarrec]

Introduction

In this 20 minutes recording we cover everything there is to know about the rollup hierarchy in SuccessFactors Compensation.

 

Key takeaways

• Rollup hierarchy allows Comp Administrators to select only specific planners in a hierarchy (standard hierarchy or compensation-specific hierarchy) and add all employees in levels below them into their worksheet.


• It is supported for both Compensation and Variable Pay.


• It supports inactive users and also works with the Compensation Manager Hierarchy (SECOND_MANAGER column of the UDF) but only through XML changes which prevent us from using the Admin UI to flag planners as a consequence (only mass upload of planners through CSV demoed at 8'31 is then available to assign planners). See an example of the xml code change in the recording at 17'.


• Planners flagged in one template carry over when we duplicate the template (since 2H 2022 release).


• Mass update worksheets jobs "Move employee to new manager's worksheet" and "Add new employee to worksheet" are supported with Rollup hierarchy (since 2H 2022 release).


• We don't recommend using Rollup hierarchy for the purpose of adding many employees into one worksheet (for optimal performance of the module we recommend a maximum of 100 employees per worksheet). We recommend it for example to skip levels of the organization that don't allow for meaningful planning recommendations to be made against a budget, for example managers with only one or two team members. To build a Comp Admin only process we should keep the Method of planning on "Standard", create worksheets for all supervisors and route them to a one and only workflow step called "Comp Admin" and have Comp Admin then use Executive Review.


• Rollup has the drawback of requiring manual maintenance of RBP groups to grant executive review access (RBP cannot identify in a dynamic way who we flagged as planners).

 

https://youtu.be/VvnrkEKKmx8

 

 

See code options and sample below:

 

 

 

 

--

All the best,

Xavier

 

 

 

(If you found this blog useful please consider giving it a Like)