In this 30 minutes recording we look at two different ways to make recently increased employees in EC ineligible in the Compensation worksheets (before or during the cycle) which is not possible with Compensation eligibility rule engine (as mentioned at the bottom of this blog).

Designs

This recording covers the two following designs :

• The leading practice of adding a field called “Date of last salary increase” in EC Comp info which will be populated on save (see design details here) of an increase on Base Salary.
  • This design which is recommended when Compensation is implemented at the same time than EC has a major drawback for customers trying to implement it after EC is live which is that it doesn’t come with prepopulated current data for the field (for example if the field gets added to CompInfo only on February 15 for the purpose of launching the cycle on March 1st and the requirement is to capture all changes to Base Salary since January then the customer will have to make data loads for all employees in Comp Info as the new field doesn’t come with current data situation).
• An alternative which involves the creation of a custom object with business rules that gets fed from Integration center and which will allow us to capture this information even if the actual salary cycle is already live or is happening imminently and without any data loads.

Technical features demoed in this recording:

• MDF business rules comparing the previous value of a field to the current value to return a third data on save.
• Integration center with hard coded effective date for all records.