UPCTSP
Back to current versionRestore this version

LOAD TIME SHEETS TO PAY HEADERS#

Processing Information#

There are two functions that load time sheets to payroll. The UPCTSP function will transfer From/To and Hours based time sheets directly to pay headers, where as the UPCTS will load time sheets to IPTR.

The intent is that the end result is the same as it would be if the user had run the UPCTS / UPTR processes. The UPCTSP function processes time rules, premiums, leaves, manual offsetting adjustments and adjustments to prior periods. The program will automatically create a batch, as does the UPTR, so the users do not have to manually create one. If one of the time sheets is bypassed, the user can run the UPCTSP at exception level 1 to determine why.

When an offset record is entered (as a negative amt.) and saved, the original record gets changed to a value that would net itself and the offset back. For example:

The Offset record was saved and the Original record hours was changed to:

When UPCTSP is run, the amount for the day is 8.0 hrs Reg.


Once the time sheet entries have been brought to the Maintain Employee Pays (IPPH) screen, the time sheets are marked as “Sent to PR” and are closed.

UPCTSP can be run in trial mode so that clients can run a test to ensure the desired results will be achieved.

The UPCTSP has the capability of allowing overlapping time entries or not, this will be left to the discretion of the user running the program.

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.

'Ready for PR ONLY'
'Add Open Time Sheets'
This parameter determines if additional time sheets should be picked up

If selections are:

Will process 40- Submitted and 50- Ready for PR and leave 30- Rules Applied untouched

If selections are:

Will process 50- Ready for PR and leave 30- Rules Applied and 40- Submitted untouched

If selections are:

Will process all time sheets; 30- Rules Applied, 40- Submitted and 50- Ready for PR

If selections are:

Will process 30- Rules Applied and 50- Ready for PR and leave 40- Submitted untouched

Report Parameters & Filters#

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.
If YES, then only time sheets that are "50- Ready for PR" will be processed
If NO, then any time sheet in the "40- Submitted" or "50- Ready for PR" stage will be processed
Add Open Time Sheets Optional, LOV Available. See note above on how to set YES / NO toggles.
If YES, then time sheets that have NOT been submitted (30- Rules Applied) will be processed
If NO, then no additional time sheets will be added.
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