This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
24 26-Nov-2021 10:22 26 KB kparrott to previous
23 26-Nov-2021 10:22 25 KB rforbes to previous | to last
22 26-Nov-2021 10:22 25 KB jmyers to previous | to last
21 26-Nov-2021 10:22 26 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
USING SALARY RATE METHODS
USING SALARY RATE METHODS

Version management

Difference between version and

At line 4 changed one line
Personality provides for the ability to compute an hourly rate for salaried employees so that when hours are entered into the system from any of the various sources, the rate of pay is computed in such a way that the proper wages are generated.
[{$applicationname}] provides for the ability to compute an hourly rate for salaried employees so that when hours are entered into the system from any of the various sources, the rate of pay is computed in such a way that the proper wages are generated.
At line 6 changed one line
In releases prior to 30502, generating hours and dollars for salaried employees required that the dollars be generated separate from the earnings since they did not necessarily balance with each other. It is not recommended that Personality be configured to pay salaried employees by generating earnings from the hours keyed, accomplished by varying the wage rate.
In releases prior to 30502, generating hours and dollars for salaried employees required that the dollars be generated separate from the earnings since they did not necessarily balance with each other. It is not recommended that [{$applicationname}] be configured to pay salaried employees by generating earnings from the hours keyed, accomplished by varying the wage rate.
At line 12 changed one line
There is also a new Pay Line Based premium that can be used in place of the UPTG Period $$$ premium. The problem with the [UPTG] premium is that it creates ‘Dollars Only’ into the [IPTR] screen, which means that the premium dollars from the hours worked in the period are not naturally generated into payroll. If not generated from hours, the [UPRETRO] would not be able to create the retro in the past. The correct way to handle a Pay Period premium is to use this new type. It will be generated from the hours worked (which may vary), and the dollars assigned to each hour will be computed by Personality correctly so that the total will equal the Period Premium amount. To account for any penny difference, the premium is force balanced when the transaction is brought into payroll during the execution of [UPTR].
There is also a new Pay Line Based premium that can be used in place of the UPTG Period $$$ premium. The problem with the [UPTG] premium is that it creates ‘Dollars Only’ into the [IPTR] screen, which means that the premium dollars from the hours worked in the period are not naturally generated into payroll. If not generated from hours, the [UPRETRO] would not be able to create the retro in the past. The correct way to handle a Pay Period premium is to use this new type. It will be generated from the hours worked (which may vary), and the dollars assigned to each hour will be computed by [{$applicationname}] correctly so that the total will equal the Period Premium amount. To account for any penny difference, the premium is force balanced when the transaction is brought into payroll during the execution of [UPTR].
At line 18 changed one line
On the [IPPC] form in the PC Details Rules tab, a new salary rate method is added to point individual pay components to the Variable Rate or Variable Time. This will allow you to select a different rate calculation for different types of time (i.e. Regular or LWOP).
On the [IPPC] form in the PC Details Rules tab, a new salary rate method is added to point individual pay components to the Variable Rate or Variable Time. This will allow you to select a different rate calculation for different types of time (i.e. Regular or [LWOP]).
At line 54 changed one line
!!Variable Rate Hours
!!Variable Rate Hours
At line 72 removed 5 lines
%%information For Salary Rate Method 'Variable Rate Hours#'
If Variable Rate Method is used but NOT using UPTG, the IDCL ‘DAILY CALENDAR’ should be extended annually
NOTE: it is ‘hard-coded’ that you cannot manually update the DAILY CALENDAR’, you must re-name it, extend it and re-name it back.%%
At line 251 changed one line
To deal with this issue, Personality will perform ‘Force Balancing’ for variable rate employees when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
To deal with this issue, [{$applicationname}] will perform ‘Force Balancing’ for variable rate employees when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
At line 271 removed 5 lines
%%information Force Balancing can now be allowed when there is a Wage, Position, or Job change in a Period, and also when an employee has more than one assignment.
The client must add User field (IMUF) 'VARIABLE RATE' to table P2K_CM_ENTITY_DETAILS. The conditions above will NOT prevent Force Balancing is the UDF contains the value '1'.
* Force Balancing happens in UPTR to ensure that Variable Rate employees receive their full SM/MO Salary in a Pay Period.%%
At line 303 changed one line
To deal with this issue, Personality will perform force balancing for variable rate employees when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
To deal with this issue, [{$applicationname}] will perform force balancing for variable rate employees when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
At line 343 changed one line
To deal with this issue, Personality will perform ‘Force Balancing’ when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
To deal with this issue, [{$applicationname}] will perform ‘Force Balancing’ when the transactions are brought into payroll ([UPTR]). This balancing will occur after the last transaction for an employee has been loaded into [IPPH].
At line 376 added 2 lines
[CLEANUP]
At line 382 added one line
This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrottTop