cancel
Showing results for 
Search instead for 
Did you mean: 

Reduce the number of lines in Variable Pay History File

RRKUMAR
Explorer
0 Kudos
347

Hi

We are building a Variable Pay solution that pulls a host of data from Job Information and Compensation Information from EC and builts the Variable Pay Background element. This then creates the Variable Pay History file.

We have noticed that due to data changes in Job Information and also Compensation information, a number of line items are being created in the Variable Pay History file, some of these fields are informational only and not necessary contribute to the calculation of Annual Incentive(Bonus). This in turn is contributing to data/information overload in the Assignment/details view.

Tried looking up the following blog written by Xavier Le Garrec on it and performed the steps but it did not have the desired effect.

  • #2 – Know how to control the number of records that show in employee history by using the Merge criteria in the varPayEmpHist background element.

Would like to understand how can we resolve this situation. Should we completely drop the information only fields from the Variable Pay Background element and then the no changes for these objects/fields will result in additional lines in VP History file or is there any approach that can work.

Please note that our solution is being built using a custom formula that takes into account the salary as of 31st Dec only for all bonus schemes throughout the calendar year. Normal salary changes happen during the mid-year and then as the "Salary" field has changed it itself automatically generates two undesired line items.

We can consider dropping the "Salary" field completely from VP Background element as the calculation is being done on "31st Dec Salary" field which is being pulled from an independent MDF field in Compensation information.

Any help or suggestions are most welcome.

Thanks

R Kumar

View Entire Topic
Fernando_Silva
Participant
0 Kudos

Hi! I would either remove the Salary field from the variable pay MDF or review the merge flag settings for the Salary field. Remember that the merge MDF property works kinda backwards: it must be false for the module not to create a new row whenever changes in the mapped field are detected.

RRKUMAR
Explorer
0 Kudos

Thanks Fernando!