Skip to Content
Product Information
Author's profile photo Xavier Le Garrec

Understanding the rollup hierarchy method of planning

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 to add too 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).




See code options and sample below:




All the best,


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Frantisek Humpal
      Frantisek Humpal

      Once again you have done a great job! Thank you so much for the article! I really appreciate the guidelines on the csv setting of the structure.

      Author's profile photo Tatyana Kolina
      Tatyana Kolina

      Hi Xavier,

      Thanks for the valuable information!

      Have you seen such an error  'Error occurred. com.successfactors.jobscheduler.ScheduledJobExecutionException: Field Label in column -3 does not match the required field name.' , when loading a UDF with an added column COMPENSATION_PLANNER_***? I did everything as in the example in the video



      Author's profile photo Xavier Le Garrec
      Xavier Le Garrec
      Blog Post Author

      Hi Tatyana Kolina

      I have never seen this message but can think of 2 things to double check: there is a checkbox in Provisionning > Company Setting that needs to be checked for us to be able to import only the STATUS, USERID and COMPENSATION_PLANNER_… columns. It’s at the bottom of the screen and starts with “use default values”. I would check that it’s checked.

      The other thing I can think of is that in some cases when LMS is on there are a few columns at the end of the exportée UDF with a lot of number suites in them that need to be kept for the reimport to work. I would try keeping the last 2 columns on top of the ones you had (STATUS, USERID, COMPENSATION_PLANNER_…)

      All the best



      Author's profile photo Maria Concetta Amodei
      Maria Concetta Amodei

      Dear Xavier,

      thanks for this useful article! We are working on Compensation module implementation and we are designing 2 templates, one for Salary Increase process, one for MBO target.

      The client would like to use the same hierarchy, Compensation-specific hierarchy based on Second Manager, but with an important difference:

      • In Salary Review process -> use all the compensation planners, in all levels;
      • In MBO Target process -> select only some compensation planners, with a roll-up logic

      Let me add another requirement: the processes will be executed in the same period.

      So, if we use the second manager role, can we use the roll-up hierarchy in MBO Target template for managing the processes as described above? Can the roll-up hierarchy use the second manager relationship?

      Thanks so much for your collaboration



      Author's profile photo Xavier Le Garrec
      Xavier Le Garrec
      Blog Post Author

      Hi Maria Concetta Amodei

      If by MBO you mean the old way to calculate bonuses through the MBO tab pulling goals from Performance forms I should clarify that even though it is still available for configuration we don't recommend using it. For any new bonus calculation configuration we recommend using Variable Pay.

      That being said MBO being a tab within a Compensation template and Rollup hierarchy being a feature defined at the template level and not at the tab level, you wouldn't be able to build the customer requirement for approvals within the same template.

      I would do:

      • Salary Review using a Compensation template with Define Planner = Compensation Hierarchy
      • Incentive Planning using a Variable Pay template with Define Planner = Compensation Hierarchy with rollup (see code above). Please note that by doing that as mentionned above you will lose the ability to flag the planner directly in the UI (that is only supported for Standard hierarchy).

      All the best


      Author's profile photo Maria Concetta Amodei
      Maria Concetta Amodei

      Dear Xavier,


      thanks for your feedback and point of view!


      unfortunately, in our scenario, the MBO target process it is not linked to PM achievements: the PM rate is like a threshold, the bonus is like a certain % of the Gross Annual Salary. For this reason, we are using Compensation Template.


      As far as i understood from your video and also article above, through xml, you can manage the settings of roll-ups based on Second Manager Hierarchy at template level: we will share the "side effect" of UI with the client and let's them decide.