GENERATE PAY TRANSACTIONS#
Processing Information#
The Generate Pay Transactions (UPTG) process creates pay transactions for a selected number of employees based on their work rule definition.
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
For more information on how to run the UPTG please see the page GENERATE PAY TRANSACTIONS.
UPTG Report Parameters #
| 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. |
| Pay Period | Mandatory, LOV Available. Defaults to period that contains the ‘As Of ‘date. |
| 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 as <Payroll>. Users can batch by authorization area, department, department batch code, location, manager or payroll. |
| Source Payroll | Optional, LOV Available |
| Destination Payroll | Optional, LOV Available |
| Rate Meth. For Salary | Optional, LOV Available |
| (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. |
| Assignment Selection | Mandatory, LOV Available |
| 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. |
| Rerun Selected EEs | Optional, LOV Available |
| 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. |
UPTG Report Filters #
| 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, and 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. |
