This content has been marked as final. Show 4 replies
Might this have something to do with the "Table Event Updates" window?
OK I figured it out. For the current implementation, we are not using the salary administration window. The total salary is made of basic, housing, transport and this is entered manually.
If these elements were calculated from the formula a change in the annual salary would trigger proration or retropay in all.
For a workaround, I am going to create an annual salary element, then try to build a user hook to update this each time a change is made to one of the standard elements.
Just need to figure out how to build user hooks for PAY_ELEMENT_ENTRIES table.
you might also include a recurring element and attach a formula to it.
ok got the answer to this one.
say I have 3 elements - basic salary, housing salary and car allowance
then I have another element , say, motivation allowance
the formula for motivation allowance is - (basic + housing + car)/30
If I make a change to only basic, and run retropay, by default, I only get a basic salary retro element. the motivation allowance is not recalculated.
To solve this, we do the following:
Go to Payroll -> Element Set
Create a new element set with type - Event Model Set
Then include the elements, basic, housing, car and motivation allowance
Now, we head to Other Definitions -> Event Group
We find our event group for retropay (typically Entry Changes)
Find or create datetrack event:
Datetrack Update for PAY_ELEMENT_ENTRY_VALUES_F, column - SCREEN_ENTRY_VALUE
Then we click on the "Set Usages" button
After this, Add our newly created element set to this list
After this is done, retropay will then be processed for Motivation Allowance as well even though a change wasn't made on it