Human Capital Management Blogs by SAP
Get insider info on SAP SuccessFactors HCM suite for core HR and payroll, time and attendance, talent management, employee experience management, and more in this SAP blog.
cancel
Showing results for 
Search instead for 
Did you mean: 
xavierlegarrec
Product and Topic Expert
Product and Topic Expert
621

In this recording we show how to build the following requirements using customization in Variable Pay:

  • If one specific business goal OR if at least one business goal doesn't meet a custom gate defined by the customer for the goal then prevent the employee from getting a payout on the individual performance for that record.
  • As per discussion in the comments below there is a standard feature for Gates and Accelerators that was documented in this blog. However there are also many other situations where the standard feature won't work and the type of customization explained in the recording below ends up being needed.

 

https://youtu.be/ZiOeUeRyXb4

 

Takeaways from the recording: 

  • Use numbers to build rollups and not text
  • Build the fields used in the rollup logic in their respective sections first, then save and log out log back in before connecting them using the Aggregate Field feature (if you don't do that you will run into error messages).
  • Remember that Assignment Level is the spine of the variable pay body, everything must go through it for bottom to top customized designs to work (from top to bottom it's actually not needed, one can simply paste the ID of an entry level column into the assignment sections - indDetail, indSection, etc.. - and it will work fine). Copy pasting the column ID of an assignment level custom field in the formula of an entry level custom field will only retrieve the value from the latest record (which can be useful sometimes, I've used this before to meet a very specific customer requirement where we needed the full history of records but only wanted a key information from the last record at the entry level for additional calculations and checks).
  • As of 2H 2024 such a design isn't possible when several business goal sections are in use (custom fields are not supported in case of multiple business goal sections). In that case you would have to use the standard Gates feature linked above with its potential limitations vs the requirement.
  • If you need to load a different gate for each business goal you can use a lookup table like this : 

xavierlegarrec_0-1738620900934.pngxavierlegarrec_1-1738621049424.png

  • Since the number of business goals within each bonus plan can be different per employee/record, you can use the "count" column trick (custom column of type amount at Business Goal level with formula =1 that aggregates to the Business Detail section for calculations.

xavierlegarrec_0-1738691997076.png

 

xavierlegarrec_1-1738692119215.png

 

 

Links to blogs on related topics: 

 

 

All the best,

Xavier 

If you found this blog useful please consider giving it a kudo !

2 Comments
Phil_MacGovern
Discoverer
0 Kudos

Hi

While I appreciate the technical details and the nice example of ways to use Assignment Level Custom Fields, I don't see how this cannot be accomplished with the standard Gates and Accelerators functionality as detailed here:

https://community.sap.com/t5/human-capital-management-blogs-by-sap/gates-and-accelerators-in-variabl...

There is a specific combination that says "If business goal X doesn't reach target Y, then the individual section pays out at 0".

Can you please explain the advantage of using the custom method over the standard?

xavierlegarrec
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi @Phil_MacGovern 

At SAP we often get pinged by implementation partners who are over their head working on very complex design requirements in Variable Pay. This is an example I can refer to for anybody looking for insights on how the Aggregate feature works to build complex relationships within and between sections (so that I hopefully can just send out this link and they can understand without me spending half a day on their issue).

To answer your question specifically here are a few examples of things that the custom design does that standard cannot do :

  • It works also if Business Goal function is not interpolate or step
  • It works if the gate is applied to the calculated result combined with something else. 
  • It is able to apply conditional logic to the payout within the section or cross section (for example "if more than 50% of business goals meet the gate, then lookup this to do that")

 

All the best,

Xavier