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 19 changed 8 lines
|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.
|Pay Period|Mandatory, LOV Available \\Defaults to period that contains the ‘As Of ‘date.
|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 <Department> \\Users may batch by authorization area, department, department batch code, \\location, or payroll.
|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.
|Pay Period|Mandatory, LOV Available. Defaults to period that contains the ‘As Of ‘date.
|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 <Department>. Users may batch by authorization area, department, department batch code, location, or payroll.
At line 31 changed 5 lines
|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, Toggle \\If toggle is ON, the time will be spit by fiscal periods if required, if Off, no fiscal period \\splits.
|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]).
|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, Toggle. If toggle is ON, the time will be spit by fiscal periods if required, if Off, no fiscal period \\splits.
|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 2 lines
|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.
|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 12 lines
|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.
|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.
[{If var='loginstatus' contains 'authenticated'
----
![Discussion|Edit:Internal.UPTG]
[{InsertPage page='Internal.UPTG' default='Click to create a new discussion page'}]
}]
This page (revision-13) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop