There are two functions that load time sheets to payroll. The UPCTSP function will load time sheets directly to pay headers, where as the UPCTS will load time sheets to IPTR.
In the Load Time Sheets to Headers (UPCTSP) screen there are two parameters that will determine what stage a time sheet needs to be in order to be picked up.
If selections are:
If selections are:
If selections are:
If selections are:
Report Parameters | |
---|---|
Entity | Mandatory, LOV Available. This field identifies the entity associated with this report. |
Payroll | Mandatory, LOV Available. This field identifies the payroll associated with this report. |
Pay Period | Mandatory, LOV available. This field identifies the pay period that the report is being run for. |
From Date | Mandatory, Date, LOV Available. This is the first day of the pay period and will default from the Pay Period Date. |
To Date | Mandatory, Date, LOV Available. This is the last date of the pay period and will default from the Pay Period Date. |
Pay Category | Mandatory, LOV available. Only one `Pay Category' may be selected |
Batch By | Mandatory, LOV Available, <Department>. Users may batch by authorization area, department, department batch code, location, or payroll. |
Ready for PR Only | Optional, LOV Available. See note above on how to set YES / NO toggles. |
Add Open Time Sheets | Optional, LOV Available. See note above on how to set YES / NO toggles. |
Mark Batch as Eligible | Mandatory, LOV Available, <YES>. Should the transaction batch be created as eligible (ready)? The eligible flag is often used to communicate between payroll clerical staff entering time, and the payroll master. |
Allow Overlapping | |
Exception Level | Mandatory, LOV available, <Exception Only>. This field indicates the exception level (report messages) required. |
Trial | Mandatory, LOV Available, <YES>. If `No' then the update is committed. If `Yes' then the update is not committed and the process may be run again. This field allows users to see the results without committing them. |
Report Filters | |
---|---|
People List | Optional, Match, Multiple Selection, LOV available, <ALL>. A people list may be used to indicate specific employee transaction to be processed. |
Person | Optional, Match, Multiple Selection, LOV available, <ALL>. This field holds the person code(s) of specific employee(s) to be processed. This list should not be used if a people list is used. |
Department | Optional, Match, Multiple Selection, LOV available, <ALL>. This field limits the process to the specified departments |
Org Level | Optional, Match, Multiple Selection, LOV available, <ALL>. This field limits the process to the specified organizational levels. |
Authorization | Optional, Match, Multiple Selection, LOV available, <ALL>. This reduces the list of people to those employees within Auth Areas listed. |
Location | Optional, Match, Multiple Selection, LOV available, <ALL>. This field limits the process to the specified locations |
Unit | Optional, Match, Multiple Selection, LOV available, <ALL>. This field limits the process to the specified units. |
Group | Optional, Match, Multiple Selection, LOV available, <ALL>. This field limits the process to the specified groups |
Pay Type | Optional, Multiple Selection, LOV available, <ALL>. This field identifies the type(s) of pay being processed. |
Status | Optional, Match, Multiple Selection, LOV available, <ALL>. This field limits the process to the specified employment status. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation