2024 Dec 06 9:46 AM - edited 2024 Dec 06 10:05 AM
Hello everyone!
I’m facing an issue related to Variable Pay, and I’m wondering if anyone else has encountered the same problem.
The "Salary" field in Employee History is mapped to the sum of a Pay Component Group. This Pay Component Group has several associated pay components in EC: one with an hourly frequency. When the employee has a monthly pay component, the value is annualized correctly and pulled into the Employee History. However, when the employee has the hourly pay component, the salary shows as 0 in the Employee History.
In EC, everything looks fine, and the Pay Component Group is annualizing correctly for both the monthly and hourly pay components. However, the Employee History remains at 0.
Has anyone faced this issue before, or does anyone have any suggestions for resolving it?
Request clarification before answering.
I can't think of anything after looking at your screenshots a few times. It looks like you've configured everything as expected so I'm thinking the issue may be in EC in the data or in settings of the PCG.
Here is what I would try: create a new paycomponent group only aggregating this Hourly PC and map the new paycomponent group to VarPayEmpHist> Salary field. Re-import employee history and check if it shows correctly. If it does then add the monthly one to the PCG definition and retry.
Please let us know the outcome.
All the bestXavier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @xavierlegarrec for the quick response and suggestion!
I tested the suggestion of creating a new pay component group, but it still shows as 0.
My only explanation for this issue is that the annualization logic between EC and Variable Pay may differ. Although we can view the annualization of the pay component in EC, this value is not stored there (2080171 - Employee Pay Group Sums do not retrieve any data when selected in Ad Hoc Reports - Employe...). As a result, when we map a salary field to the sum of a pay component group, the value is recalculated in Variable Pay.
In EC, the annualization of non-hourly pay components is performed by multiplying by the annualization factor based on the frequency. For hourly pay components, the annualization factor is 0. When the annualization factor is 0, EC assumes the pay component is hourly and, instead of using the annualization factor, it multiplies by the Standard Weekly Hours and the Weeks per year (2162127 - Compensation Information: Pay Component Group Calculations).
What I believe is happening in Variable Pay is that the annualization is always calculated by multiplying the pay component by the annualization factor, even if it is set to 0. In contrast, in EC, when the annualization factor is 0, it recognizes the pay component as hourly and multiplies by the weekly hours and the weeks in the year.
However, I can't find any information from SAP indicating that there is a limitation on using hourly pay components in VarPay.
I wonder why in your explanation you say that you do NOT have an annualization factor on the Hourly pay component ? I understand that there is an EC feature that makes EC PCG sums work without it but what would be the impact if you did add one ? Could you try that and add 2080 as annualization factor for the hourly pay component then relaunch Variable Pay employee history ? @MariaCarlotaAbreu @gregwilliams
Yes it is also relevant for Compensation. @Sarnendu_Chatte
User | Count |
---|---|
4 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.