EC field to determine compensation eligibility

[former_member61861]

Hi all

We have been using eligibility rules directly in compensation for all our templates for compensation. These are quite complex and not able to hit all eligible / non-eligible. We would therefore like to create a field in EC where you either have a 'yes' or 'no' to eligibility. Compensation should then look at this field to either take the employee in or out.

But, we are facing some difficulties, since we would like to have this field in job information. So, let's say that an employees has 'Yes'. This employee is then promoted as of March 1. The rule states, that anyone promoted after January 1, should not be part of the cycle. So when the promotion is done, the field should be changed to 'no'. The effective date of this 'no' will then be March 1, as that is the effective date of the promotion.

We are looking at data in the compensation template as of February 1 - and in this case, the employee has a 'yes' on February 1, since the promotion isn't effective until March 1. This means, that the compensation template will see a 'yes' and take in the employee.

How can we get around this effective dating - keeping the field in job information, but not giving issues to the comp module?

Or would you suggest a completely different solution?

Br

Maja

[nlgro02343]

You can go 2 ways.

Option 1 --> put the field in a non-effective dated portlet (you could even keep this solution in job info but sync the field to a custom field in the user data file and then use that for eligibility purposes). Otherwise putting the data in a custom field in employment info (i'd not recommend biographical info due to potential issues with concurrent employment/global assignments etc.).

Option 2 --> Change the date on which you check eligibility (i.e. put it to March). I doubt you'll want that, but from a technical perspective it's an option.