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

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
13 26-Nov-2021 10:22 5 KB mmcfarland to previous
12 26-Nov-2021 10:22 5 KB mmcfarland to previous | to last
11 26-Nov-2021 10:22 4 KB kparrott to previous | to last
10 26-Nov-2021 10:22 4 KB kparrott to previous | to last
9 26-Nov-2021 10:22 4 KB jmyers to previous | to last
8 26-Nov-2021 10:22 4 KB jmyers to previous | to last
7 26-Nov-2021 10:22 5 KB jmyers to previous | to last
6 26-Nov-2021 10:22 4 KB jmyers to previous | to last
5 26-Nov-2021 10:22 4 KB RForbes to previous | to last
4 26-Nov-2021 10:22 4 KB JEscott to previous | to last
3 26-Nov-2021 10:22 4 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
UPTG
UPTG

Version management

Difference between version and

At line 5 changed one line
The Generate Pay Transactions (UPTG) process creates pay transactions for a selected number of employees based on their work rule definition.
The Generate Pay Transactions (UPTG) form is used to create pay transactions for a selected number of employees based on their work rule definition.
At line 7 changed 5 lines
Generation of batches of Pay Transactions is done for a:
* Defined payroll
* Set of employees within the payroll that match the report parameters
* Defined pay period or a date range within the defined pay period
* Defined pay category
Generation of batches of Pay Transactions is done for:
* a specified payroll;
* a set of employees within the payroll that match the report parameters;
* a specified pay period or a date range within the specified pay period; or
* a specified pay category.
At line 16 changed one line
!!UPTG Report Parameters
!!Report Parameters & Filters
At line 18 changed 3 lines
||Field||Description
|Entity|Mandatory, LOV Available. Limits the process to the entity defined.
|Payroll|Mandatory, LOV Available. Only one payroll can be selected per execution of this function.
||Report Parameters||
|Entity|Mandatory, LOV Available. Limits the process to the entity specified.
|Payroll|Mandatory, LOV Available. Only one payroll may be selected per execution of this function.
At line 22 changed 5 lines
|Pay Category|Mandatory, LOV Available. Users must define the category that the batches and pay headers are to be processed under.
|From Date|Mandatory, Date, LOV Available. Defaults from the pay period defined but can be changed.
|To Date|Mandatory, Date, LOV Available. Defaults from the pay period defined but can be changed.
|Batch Type|Mandatory, LOV Available. Batch and their pay headers can be created with hours and salary, hours only or salary only.
|Batch By|Mandatory, LOV Available. Defaults to <Payroll>. Users can batch by authorization area, department, department batch code, location, manager or payroll.
|Pay Category|Mandatory, LOV Available. Users must indicate the category that the batches and pay headers are to be processed under.
|From Date|Mandatory, Date, LOV Available. Defaults from the pay period chosen but may be changed.
|To Date|Mandatory, Date, LOV Available. Defaults from the pay period chosen but may be changed.
|Batch Type|Mandatory, LOV Available. Batch and their pay headers may be created with hours and salary, hours only or salary only. This setting, if used, overrides the work rule ([IDWR] - Time Codes tab) Time Generation Rule.
|Batch By|Mandatory, LOV Available, Defaults as <Payroll>. Users may batch by authorization area, department, department batch code, location, manager or payroll.
At line 30 changed one line
|(IDWR) TS/TM|Optional, Toggle. When this toggle is set to YES, the Employee selection completely disregards the 'Obtain Details From' on the Status Rules tab in [IDWR]. \\ \\This is used when hours must be generated into [IPTR] and the Work Rule is also used for Time Entry, allowing regular hours from UPTG and Exceptions in Time Scheduling.
|(IDWR) TS/TM|Optional, Toggle. If this toggle is set to 'YES' then the Employee selection completely disregards the 'Obtain Details From' on the Status Rules tab in [IDWR].// //This is used when hours must be generated into [IPTR] and the Work Rule is also used for Time Entry allowing regular hours from UPTG and Exception in Time Scheduling.
At line 32 changed 4 lines
|Prime Assign. Only|Optional, Toggle. When this toggle is set to ON, only the prime assignment will be used. When this toggle is set to OFF, any qualified assignment will be used.
|Split by Fiscal Periods|Optional. When this field is set to YES, or left blank, the time will be spit by fiscal periods, if required. When this field is set to NO, no fiscal period splits will be applied.
|Ignore Leave Lines|Optional, Toggle. When this toggle is set to OFF, the transactions will be inserted for employees on leave ([IAAL]).
|Create as Approved|Optional, Toggle. When this toggle is set to ON, the transaction batches will be created as pre-approved. The ‘approved’ flag can be used to indicate that the batch has been finished, audited, and/or approved by a supervisor. Organizations that do not wish to use this functionality can create pre-approved batches. The batch must be both eligible and approved to be picked up by the Update Pay Transactions ([UPTR]) process.
|Prime Assign. Only|Optional, Toggle. If Toggle is ON, only the prime assignment will be used, if toggle is OFF any qualified assignment will be used.
|Split by Fiscal Periods|Optional. If the value selected is YES (or left blank), the time will be spit by fiscal periods if required, if NO, then no fiscal period splits will be applied.
|Ignore Leave Lines|Optional, Toggle. If OFF, the transactions will be inserted for employees on leave ([IAAL]).
|Create as Eligible|Optional, Toggle. Should the transaction batch be created as eligible? The eligible flag is often used to communicate between payroll clerical staff entering time, and the payroll master. Users indicate that the batch is ‘eligible’ (ready). If users do not wish to use this functionality, they may create the batch as eligible. The batch must be both eligible and approved to be picked up by the Update Pay Transactions program ([UPTR]).
|Create as Approved|Optional, Toggle. Should the transaction batches be created as pre-approved? The ‘approved’ flag may be used to indicate that the batch has been finished, audited, and/or approved by a supervisor. Sites that do not wish to use this functionality may create pre-approved batches. The batch must be both eligible and approved to be picked up by the Update Pay Transactions program ([UPTR]).
At line 37 changed 3 lines
|Print Employee Details|Optional, Toggle. When this toggle is set to ON, each transaction generated for each employee will be printed.
|Trial|Optional, Toggle. When this toggle is set to ON, the update is not committed and UPTG can be run again. When this toggle is set to OFF, the update is committed.
|Exception Level|Mandatory, LOV Available. Defines the level of detail to be printed. Users can increase the level of logging done from exception to user, legislation, usercalc, program or utility levels.
|Trial|Optional, Toggle. If ‘ON’ then the update is not committed and UPTG may be run again. If ‘OFF’ then the update is committed.
|Exception Level|Mandatory, LOV Available. Users may increase the level of logging done from exception to user, legislation, usercalc, program or utility levels.
At line 42 changed one line
!!UPTG Report Filters
||Report Filters||
|People List|Optional, Multiple, and LOV Available. A people list may be used to indicate specific employee transaction to be processed.
|Person|Optional, Multiple, and LOV Available. The person code(s) of specific employee(s) to be processed.
|Department|Optional, Multiple, and LOV Available. The report may be limited to the departments specified in this field.
|Org Level|Optional, Multiple, and LOV Available. The report may be limited to the organization level specified in this field.
|Authorization|Optional, Multiple, and LOV Available. The report may be limited to the authorization level specified in this field.
|Location|Optional, Multiple, and LOV Available. The report may be limited to the locations specified in this field.
|Unit|Optional, Multiple, and LOV Available. The report may be limited to the units specified in this field.
|Group| Optional, Multiple, and LOV Available. The report may be limited to the groups specified in this field.
|Employment Status|Optional, Multiple, and LOV Available. May limit the processing of employees to their employment status.
|Employment Type|Optional,Multiple, LOV Available. May limit the processing of employees to specific employment types
|Assignment Type|Optional,Multiple, LOV Available. May limit the processing of employees to specific assignment types
|Pay Type|Optional, LOV Available. May limit processing of employees to the type of pay indicate on their group.
At line 44 removed 14 lines
||Field||Description
|People List|Optional, Multiple, and LOV Available. Users can define a people list for specific employee transactions to be processed.
|Person|Optional, Multiple, and LOV Available. Users can define specific person code(s) to be processed.
|Location|Optional, Multiple, and LOV Available. Users can define specific location(s) to be processed.
|Authorization|Optional, Multiple, and LOV Available. Users can define specific authorization level(s) to be processed.
|Department|Optional, Multiple, and LOV Available. Users can define specific departments to be processed.
|Org Level Type|Optional, LOV Available. Users can define specific organization level(s) to be processed.
|Org Level|Optional, Multiple, and LOV Available. Users can define specific organization level(s) to be processed.
|Unit|Optional, Multiple, and LOV Available. Users can define specific unit(s) specified to be processed.
|Group|Optional, Multiple, and LOV Available. Users can define specific group(s) specified to be processed.
|Employment Status|Optional, Multiple, and LOV Available. Users can define specific employment status(es) to be processed.
|Employment Type|Optional, Multiple, LOV Available. Users can define specific employment type(s) to be processed.
|Assignment Type|Optional, Multiple, LOV Available. Users can define specific assignment type(s) to be processed.
|Pay Type|Optional, LOV Available. Users can define specific pay type(s), defined on the employee's group, to be processed.
At line 59 removed one line
This page (revision-13) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop