on 10-05-2023 5:01 PM
If someone has gone on a Global Assignment part way through the year, the requirement is to show both records in VP, e.g. 3 months bonus calculated based on home record and 9 months bonus calculated based on host record. I am seeing two rows for for them in VP, however only one is populated and relates to the Paused record and the other is blank.
Where a global assignment spans the entire year, the requirement is to see one row in VP and have 100% of the bonus calculated based on their host record. I am seeing one row in VP but the bonus is calculated based on the paused record.
In my Global and EE History eligibility rules, I have stated Employee Status must be 'Active', 'Leave of Absence', 'Paid Leave of Absence' or 'Dormant'.
Please can you advise how to write the eligibility rules so that VP meets the requirements mentioned above?
It is not possible to put both the home and host records in a single row. As far as VP is concerned, the home and host records are two people, as different as you and I. There is no sharing of data between the home and host record. There will always be two rows.
You need to have the eligibility rule create history records for three months for "home" employee and nine months for "host" employee. All of the data needed to calculate a bonus must be on both records.
It is more or less impossible for me to debug your scenario. All I can say that in the Best Practices EC configuration, we have added a custom field called "Home/Host Designation" to the Job Information portlet for exactly this scenario. This field is a picklist with three possible values: Home, Host, and Home - On Assignment. Business rules set this field in reaction to the "Going on GA" and "Returning from GA" event reasons; it is never manually set. As you might imagine, all employees active at their home assignment have a value of "Home". When an employee goes on GA, the home record field is updated to be "Home - On Assignment" and the host record is populated with "Host". When the employee returns from assignment, the home record is reset to "Home".
The Employee History eligibility rule is checks for "Home" and "Host" and ignores the "Home - On Assignment" value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi phil.macgovern I have just posted an update on this and have just re-read the comment that you submitted last week.
If I have understood correctly, you are suggesting that we add a custom field to Job Info called "Home/Host Designation" and have a business rule set up to auto-populate that field with values 'Home', 'Host' and 'Home - On Assignment'. The auto-population triggers when event reasons are added for 'Going on GA' or 'Returning from GA'. Once this is in place, I update my EE History rule to include criteria that says 'home/host designation = 'home' or 'host'. If I do that, then both home and host records will show with the correct pro-ration in variable pay.
Have I understood that correctly? And can you confirm that this is what SAP advise to get Global Assignments working correctly in Variable Pay?
Also, are you able to share any documentation that you may have regarding the Home/Host Designation field? I'm particularly keen to see the business rule that you set up so we can get this right, if this is the way forward.
Thank you for your support with this.
HOMEHOST3:
HOMEHOST4:
HOMEHOST 1 is an 'onInit' rule on the Employee Information Model. 2 is an "onInit" rule on JobInformation. Rule 1 sets the flag to "Home" on hire. Rule 2 sets it to "Host" when the new record is created when the employee goes on assignment.
HOMEHOST 3 and 4 are both "onSave" rules on JobInfo. Rule 3 sets the home record to "Home - On Assignment" and 4 sets it to "Home" once more when they return.
Of course, your event reason codes may be different.
User | Count |
---|---|
6 | |
3 | |
3 | |
3 | |
2 | |
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.