cancel
Showing results for 
Search instead for 
Did you mean: 

Bonus Calculations Guidelines not updated in worksheet..

Ritanshi
Participant
0 Kudos
538

Hi Team,

We have not yet integrated the perf management and picking the ratings via EE profile.

I have updated guidelines for calculating bonus based upon custom fields. which is working for few employees and for rest the percentage is not getting updated.

For example: - if custom pay grade=18 and rating is 4 then 5% should be applied. Similarly for other grades and rating =4 then 3% should be applied

under bonus worksheet guidelines is calculating for few employees having pay grade=18 and for some employees it is not getting calculated.

Did anyone faced this kind of issues. wherein half of the portion of the guidelines are working and for rest it is not working.

I have already tried re-loading the guidelines/updated several times in order to refresh the values.

Pl suggest

Thanks

Ritanshi

Accepted Solutions (1)

Accepted Solutions (1)

Ritanshi
Participant
0 Kudos

HI Xavier/Leslyr

Thanks for all your suggestion

If I just put 18_E or 18_N and * then guidelines comes with zero %. thats why I updated all 60 pay grade as guidelines percentages and then it worked fine.

If we provide * then it read that % by default

Thanks

Ritanshi

lesleyr
Product and Topic Expert
Product and Topic Expert
0 Kudos

If you put your * guidelines at the bottom it would work as they get processed in order.

Answers (4)

Answers (4)

Ritanshi
Participant
0 Kudos

Hey Xavier

Thanks

I tried already with pay grade= 18N or 18E. The individual payout guidelines gets zero percent. Then I tried with uploading entire salary grade18 N text.

Surprised that it worked for bonus target value =2 and not bonus target value=3.

Should I raise support ticket with sap?

xavierlegarrec
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ritanshi, looking at your screenshots it’s not 18N but 18_N but I’m sure that what you tried. You can ask support for sure so that someone can spend more time on this but I would be surprised if this doesn’t end up as a configuration issue.

Ritanshi
Participant
0 Kudos

Just to add it is reading the pay grade=* value instead of 18_N or 18_E

Instead of

Incorrect worksheet

Pl let me know in case if you need more screenshots

xavierlegarrec
Product and Topic Expert
Product and Topic Expert
0 Kudos

ritanshi_07

I would try reloading the same exact guideline table with 18_E and 18_N in the Pay Grade column instead of "Salary Grade 18 (18_E)". And then recreate worksheets and test.

lesleyr
Product and Topic Expert
Product and Topic Expert
0 Kudos

I noticed in these screenshots that your items with "edit" under pay grade are numbered 12,13, 14 but then your more specific ones are 20,21,22

When processing guidelines the system starts at line 1 and goes down until it finds a match and then it stops - so you need to ensure that your guideline order goes from the most specific to more broad and have your "wildcard" or "catch all" type entries after that so that they are only reached if no match is found within your specific guidelines.

Based on these screenshots I am wondering if the issue is a combination of the order and also data as xavierlegarrec has mentioned where the Pay Grade should be "18_E".

I would suggest reviewing the order and put the ones with "edit" at the bottom and also ensure there is no overlap with the bonus target ranges. Also ensure that for every data point your data in the guidelines is an exact match with the expected data in those columns.

Ritanshi
Participant
0 Kudos

Thanks for help Lesley

I have attached the document with guideline and worksheet screenshot. Kindly check and guide

Guidelines

Indiv guideline should be 100% instead of 34.65%

Where as for Bonus Target=2 and pay grade =18 . Guidelines are updated and working correctly.

lesleyr
Product and Topic Expert
Product and Topic Expert
0 Kudos

Can you provide screenshots of your guidelines as well as those guideline data fields for the employees who are not working? It sounds like there's a gap or something missing data-wise if it works for some people and not others.