on 2023 Nov 30 11:07 AM
Hi all,
I would like to know if somebody knows off a workaround for the following challenge we are facing:
we are calculating merit increase on monthly salary, but our compa-ratio is based on annualized salary including allowances. We use salary ranges from EC to calculate compa-ratio (but also using the pay range table in compensation module gives us the same result).
Because we use monthly salary for merit calculation, salary ranges are shown in monthly numbers as well (although they are stored as annual numbers in EC / pay range table). However, since we calculate compa-ratio based on annualized salary, we also would like to show the pay ranges in annual number on the compensation forms.
This is possible if we pick up annualized salary in compensation form and use this to calculate merit, but we do not want that as we use monthly amounts to calculate merit.
Do you feel there is a workaround / solution for this?
One workaround I am thinking of myself is to create a lookup table in compensation with annual pay ranges (from EC) and pick this up with custom fields in the compensation form, then use another custom field to calculate the compa ratio with the annualized salary dividing by the mid point from this custom table.
Let me know what you think 🙂 thank you!
Request clarification before answering.
Map curSalary to the pay component group rather than the pay component. Same for units per year. Create a custom money field with ID meritTarget and map that to the pay component. In the XML change (or add) the tag "merit-calc" from basedOn='CurrentSalary' to 'Target' (<merit-calc basedOn="Target"/>). That should do it. Basically, you are telling the system you are loading an annual amount but telling the merit field to use the monthly amount as the target.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you Philip!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
8 | |
5 | |
5 | |
4 | |
3 | |
2 | |
2 | |
2 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.