This page (revision-20) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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

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
20 26-Nov-2021 10:22 12 KB Karen Parrott to previous
19 26-Nov-2021 10:22 12 KB Lilia Urtan to previous | to last
18 26-Nov-2021 10:22 12 KB kparrott to previous | to last
17 26-Nov-2021 10:22 12 KB kparrott to previous | to last
16 26-Nov-2021 10:22 12 KB kparrott to previous | to last
15 26-Nov-2021 10:22 12 KB kparrott to previous | to last
14 26-Nov-2021 10:22 11 KB JMyers to previous | to last
13 26-Nov-2021 10:22 11 KB JMyers to previous | to last UPPAL ==> Processing Leave Lines In IAAL
12 26-Nov-2021 10:22 11 KB JEscott to previous | to last
11 26-Nov-2021 10:22 9 KB JEscott to previous | to last
10 26-Nov-2021 10:22 8 KB JEscott to previous | to last
9 26-Nov-2021 10:22 8 KB JEscott to previous | to last
8 26-Nov-2021 10:22 8 KB JEscott to previous | to last
7 26-Nov-2021 10:22 8 KB JEscott to previous | to last
6 26-Nov-2021 10:22 8 KB JEscott to previous | to last
5 26-Nov-2021 10:22 8 KB JEscott to previous | to last
4 26-Nov-2021 10:22 8 KB JEscott to previous | to last
3 26-Nov-2021 10:22 7 KB JEscott to previous | to last
2 26-Nov-2021 10:22 7 KB JEscott to previous | to last
1 26-Nov-2021 10:22 7 KB JEscott to last

Page References

Incoming links Outgoing links
GENERATE PAY TRANSACTIONS
GENERATE PAY TRANSACTIONS

Version management

Difference between version and

At line 1 added 2 lines
[{TableOfContents }]
\\
At line 9 added 6 lines
The Generate Pay Transactions ([UPTG]) form is used to create pay transactions for a selected number of employees based on their work rule definition.
The Enter Pay Transactions ([IPTR]) form is used to modify transactions already generated and to add new transactions with a minimum of data entry.
The Process Pay Transactions ([UPTR]) form is used to create batches, pay headers, and pay lines from transactions generated or entered though [IPTR].
At line 9 changed one line
All HR changes that will affect the current payroll MUST be made prior to UPTG.
All HR changes that will affect the current payroll MUST be made prior to [UPTG].
At line 25 added 23 lines
Prior leaves will not be processed by [UPTG]. The [UPPAL] process must be run to pick up prior leaves. The prior leave date prompt has been removed from the [UPTG] program.
The 'Allow Duplicates' parameter has been removed from [UPTG]. The [UPTG] program has been updated to now process in the following manner:
* For Salary, if already exists, will NOT generate again (regardless of the date it was already generated for)
* For Time, if Same Day/Same Time Code/Same Assignment - will NOT generate
* For Time, if Same Day/No Time Code/Same Assignment - will NOT generate
* Will NEVER generate Holidays more than once
* Will NEVER generate LEAVE records more than once
In the [UPTG] run, the 'Bypassed leave line' message will appear only for employee who have leave on non-scheduled day.
Multiple runs of [UPTG] are allowed including runs for time only or salary only and for the purpose of picking up new hires.
New parameter added to [UPTG] 'Rate Method for Salary'. This is an option on [UPTG] for salary generation to allow clients to choose which way they want to compute the hourly rate that will be used for special situations. A special situation may be an employee starts or terminates part way through the pay period or has a pay increase part way through the pay period and
their salary needs to be calculated. The options available for the parameter 'Rate Method for Salary' are:
* Standard Hours (default value if not selected)
** Compute the hourly rate from Annualized Salary: (Hourly Rate = Annualized Salary / (Std hours/wk * 52)
** Using this method, employees would always have the same hourly rate no matter what pay period they are in. This method is not very precise.
* Scheduled Hours:
** Compute the hourly rate from the Pay Period:(Hourly Rate = Pay Period Salary * (Hours worked in PP/Scheduled Hours in PP)
** Using this method, the rate would vary depending on the month they are in and the scheduled hours. This method is extremely accurate.
At line 19 changed one line
*If the Time Generation work rule is “By Day with Time” or “By Day w/o Time” the generation of time is done by day. This is referred to as the “qualifying time frame”. The days that will be generated will be:
*If the [Time Generation Rule|TIME_GENERATION_RULE] is “By Day with Time” or “By Day w/o Time” the generation of time is done by day. This is referred to as the “qualifying time frame”. The days that will be generated will be:
At line 38 changed one line
***If Hours Per Day is specified ([IDHC] for that holiday), uses those hours. Otherwise, derives the hours per day from the standard hours on [IDWR] or from the Work Calendar.
***If [Hours Per Day|HOURS_PER_DAY] is specified ([IDHC] for that holiday), uses those hours. Otherwise, derives the hours per day from the [standard hours|STD_HOURS_PER_DAY] on [IDWR] or from the Work Calendar.
At line 52 changed one line
***If the Time Generation Rule is “without time”, the time code will be generated, but the hours will be NULL
***If the [Time Generation Rule|TIME_GENERATION_RULE] is “without time”, the time code will be generated, but the hours will be NULL
At line 55 changed one line
If the Time Generation work rule is “By Week with Time”, “By Week w/o Time”, “By Period with Time” or “By Period w/o Time”, summary pay transactions will be created by week or pay period with the following exceptions:
If the [Time Generation Rule|TIME_GENERATION_RULE] is “By Week with Time”, “By Week w/o Time”, “By Period with Time” or “By Period w/o Time”, summary pay transactions will be created by week or pay period with the following exceptions:
At line 61 changed one line
If a Salary $ Code work rule is specified, salary earnings will be generated on the last day of the qualifying time frame with the following exceptions:
If a [Salary $ Time Code|DTC_ID_SALARY] is specified, salary earnings will be generated on the last day of the qualifying time frame with the following exceptions:
At line 68 changed one line
* If the Group ([IDGR]) Pay Type is “Hourly”, no salary dollar amount will be generated since the wages will be derived entirely from the time generated (based on Pay Component Pay Details).
* If the Group ([IDGR])[Pay Type|PAY_TYPE] is “Hourly”, no salary dollar amount will be generated since the wages will be derived entirely from the time generated (based on Pay Component Pay Details).
At line 70 changed one line
* If the Group ([IDGR]) Contract Type is “$ Paid as Earned”, no salary dollar amount will be generated since the wages will be derived entirely from the time generated (based on Pay Component Pay Details)
* If the Group ([IDGR]) [Contract Type|CONTRACT_TYPE] is “$ Paid as Earned”, no salary dollar amount will be generated since the wages will be derived entirely from the time generated (based on Pay Component Pay Details)
At line 72 changed one line
*If the Pay Type is “Salary” and the Contract Type is “Null”, counts the # eligible days in the qualifying period, excluding “off” days, generated holidays, leave days. \\''Salary $ = Pay Period Wage x (# eligible days / # normal working days in the qualifying period)''
*If the [Pay Type|PAY_TYPE] is “Salary” and the [Contract Type|CONTRACT_TYPE] is “Null”, counts the # eligible days in the qualifying period, excluding “off” days, generated holidays, leave days. \\''Salary $ = Pay Period Wage x (# eligible days / # normal working days in the qualifying period)''
At line 74 changed one line
*If the Contract Type is “$ Prorated Over Term”, count the # eligible days in the qualifying period, excluding “off” days, generated holidays, leave days.
*If the [Contract Type|CONTRACT_TYPE] is “$ Prorated Over Term”, count the # eligible days in the qualifying period, excluding “off” days, generated holidays, leave days.
At line 78 changed one line
* If the Contract Type is “n Fixed Payments” and if “n” payments have not yet been made \\''Salary $ = Contract Limit - CT $ Paid) / # Periods Remaining''
* If the [Contract Type|CONTRACT_TYPE] is “n Fixed Payments” and if “n” payments have not yet been made \\''Salary $ = Contract Limit - CT $ Paid) / # Periods Remaining''
At line 80 changed one line
* If the Contract Type is “n Payments With Bank” and if “n” payments have not yet been made, if the Assignment End Date has been passed or the “nth” payment is being made, \\''Salary $ = (Contract Bank) / # Periods Remaining'' \\Otherwise, \\''Salary $ = (Contract Limit - CT $ Paid) / # Periods Remaining''
* If the [Contract Type|CONTRACT_TYPE] is “n Payments With Bank” and if “n” payments have not yet been made, if the Assignment End Date has been passed or the “nth” payment is being made, \\''Salary $ = (Contract Bank) / # Periods Remaining'' \\Otherwise, \\''Salary $ = (Contract Limit - CT $ Paid) / # Periods Remaining''
When UPTG is requested to generate 'SALARY' in addition to 'HOURS' the FTE is not considered when computing the Period Earnings. UPTG looks at either the actual Work Calendar or Standard Hours depending on the method selected in the 'Rate Method for Salary' Report Parameter.
Once UPTG has the 'Actual' hours worked, the salary is calculated by taking their Full Time Hourly wage and multiplying it be the hours worked.
For Part Time employees, the scheduled or standard hours should be less than that worked by a Full time Employee.
At line 86 changed one line
After all transactions for the qualifying time frame have been generated, a second pass is done to handle leaves that are governed by leave policies.
After all transactions for the qualifying time frame have been generated, a second pass is done to handle leaves that are governed by [leave policies|LEAVE POLICIES].
At line 90 changed one line
Leave bank balance checking is done in accordance with the leave policies.
Leave bank balance checking is done in accordance with the [leave policies|LEAVE POLICIES].
At line 94 changed one line
If there is still not enough time and the Time Warn Rule field on [IALP] indicates “Error, don’t allow”, the leave time is generated using the “LWOP Time Code” specified on the policy.
If there is still not enough time and the [Time Warn Rule|TIME_WARNING_RULE] field on [IALP] indicates “Error, don’t allow”, the leave time is generated using the “LWOP Time Code” specified on the [policy|LEAVE POLICIES].
At line 136 added 37 lines
----
!!Transactions
The pay transaction 'Schedule Time' field (on [IPTR]) will only be populated if the work rule 'Regular Time Code' on the work rule ([IDWR]) has the 'Adjust Scheduled Time' toggle (on [IDTC]) turned on.
Nothing will be done to force balance time of the 'Schedule Time' field if it is empty, even if other time codes have the 'Adjust Scheduled Time' toggle on.
If the 'Schedule Time' and a time code have the 'Adjust Scheduled Time' toggle on, the 'Regular Time Code' hours will be reduced by the time exception.
----
!!Regenerating the Timesheet Details
This will be done when assignment details change as follows:
Triggers:
# position is changed
# job is changed
# department is changed
# work rule is changed
# work calendar is changed
# hours per day is changed
# employment status is changed
# FTE is changed
# effective date is changed
# effective record is deleted
Rules: In general, regeneration occurs on any open timesheet for that EE with following exceptions:
# if there are more than 5 open timesheet the none of the timesheet will be regenerated
# if the timesheet is generated by assignment than we skip any open timesheet for other assignments
# we regenerate only the open timesheets for the changed assignment
The above process to rebuild the details will take place only the new preference [EAS CHNG REBLD T(System Preference)] is set to YES - see detail description on [IMPF], [SYSTEM PREFERENCE]
----
![Notes|Edit:Internal.GENERATE+PAY+TRANSACTIONS]
[{InsertPage page='Internal.GENERATE+PAY+TRANSACTIONS' default='Click to create a new notes page'}]
This page (revision-20) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop