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)

[FrantisekHumpal]

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.

[Tanya9]

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

Regards,

T

[xavierlegarrec]

Hi tanya1

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

Xavier

 

[mamodei]

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

 

Maria

[xavierlegarrec]

Hi m_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

Xavier

[mamodei]

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.

Thanks,

 

Maria

[sgrintchenko]

Has anyone used People Leader hierarchy in SF as the hierarchy in Compensation?  What is the best practice to build Compensation hierarchy?

[xavierlegarrec]

@sgrintchenko Leading practice hierarchy is the line manager one (visible in the orgchart).

Please see here for more information: https://community.sap.com/t5/human-capital-management-blogs-by-sap/compensation-implementation-leadi...

[prashantpriya8]

Hi @xavierlegarrec 

Just a clarification . 

Client need everyone in one sheet. So if I am using Rollup Hierarchy, I will make CEO as the planner and then launch the worksheet. So everyone comes in that sheet except CEO. As CEO is missing i will go to Add Employee and then add CEO also in the same worksheet. In system I am able to do this . But do you think it will create any problem?

Thanks, 

PP

[xavierlegarrec]

Hi @prashantpriya8 

Do NOT have everyone in one worksheet, you will have serious performance issues when saving updated entries in Executive Review or in the worksheet. It's in the blog above:

Launch a worksheet for each planner, have they all route to Comp Admin one and only step, then give Executive Review access to whoever needs to have it. You can also remove the CEO as an approver for specific worksheets once they are created so that CEO doesn't receive many worksheets in their inbox.

All the best,

Xavier

[prashantpriya8]

Hi @xavierlegarrec 

In our worksheet we dont have to update any columns . its all calculated columns so once worksheet is launched the final amount will get auto calculated. 

Worksheet is not going to CEO for any approval. We are making him planner in roll up hierarchy just to launch the worksheet. Worksheet will go to CompAdmin as 1st step in route map and then compAdmin will move it to final step. 

The query is that if we are making CEO as Planner in Rollup Hierarchy then he is getting skipped in worksheet . So I am adding him again in same worksheet manually, so that everyone will be in same worksheet. Is adding planner in worksheet will create any issue?

Thanks, 

Prashant

[xavierlegarrec]

Hi @prashantpriya8 

It shouldn't create any issues to manually add the CEO. OK then if worksheets are read-only for everybody then I guess that would be an acceptable exception to the "Do not add all employees in one worksheet". But even if you make an override field editable to Comp Admin only for example, be ready to wait 2 minutes or more when you hit save in executive review. 

All the best,

Xavier

[ErikaT]

Hi Xavier,

We are facing the following issue: for our Variable Pay plan we use Roll up Hierarchy and want to include inactive users. We adjusted the xml with 

<comp-plan-creation rollup-users="1"/>

<comp-manager-hierarchy type="3"/>

However when we Import Employee History from Employee Central we don't get the inactive users imported.

We use the following Eligibility Rule for Employee History Records:

We want to include inactive user terminated on or after 31/12/2024. Do you have any idea why the inactives are not imported?

Thanks,

Erika

[xavierlegarrec]

Hi @ErikaT 

It's most likely an issue with your EC rules rather than the rollup code you use with the template.

Unfortunately I cannot see the screenshot of your rule. Can you share it again as well as the filtering one if you have one in place ?

What I do in these cases is I remove any conditions in the rules or make a very simple one to check whether it does import inactive employees. And then I add back my conditions little by little until I single out the root cause.

All the best

Xavier

[ErikaT]

Hi Xavier,

Here are de settings:

Thanks, Erika

[xavierlegarrec]

Hi @ErikaT 

I replicated your rule in my demo and I am not having any issue retrieving the right inactive users.

Please watch the recording I made for you here : https://youtu.be/Dsb1AClnv6g

Do you uncheck the "Active Users only" box when you view Employee History ?

Thanks 

All the best

Xavier

[ErikaT]

Hi Xavier,

Thank you for all your efforts and support!

The issue turned out to be that the "Active Users Only" box was checked when I viewed the Employee History. It’s indeed a simple detail, but now I’ve learned from it. Once again, thank you!

BR, Erika

[CharishmaGowda]

Hi Xavier,

In our Variable Pay program, we are using the roll up hierarchy (including inactive users) to define planners. However, since planners are not directly visible in the UI under define planners, it is difficult to verify the assigned planners and the eligible employees under them.

Could you please assist me on generating a report that includes the following details?
• Planner assigned
• Employees under each planner
• Eligibility Status (Eligible/Ineligible)
• Active/Inactive Status

Looking forward for your response!