Wiki: UPTR

PROCESS PAY TRANSACTIONS#

Processing Information#

The Process Pay Transactions Report (UPTR) processes pay transactions according to the defined selection criteria on the Maintain Pay Transactions IPTR form and creates pay headers and pay lines. These pays are then audited through the (UPAUDT) process and prepares them for calculation for the (UPCALC) process.

The UPTR processes one batch of pay transactions at a time and conditionally updates the Batch Status to 'Processed by UPTR' at the end of the batch.

Transactions within a batch will be bypassed if the Time Code does not have an associated Pay Component in IDTC and also when the Associated Pay Component is not valid (Based on PCRULES) for the Employee Entity, Unit and Group.
By defining the UPTR CLEANUP(System_Preference) Preference, users can force UPTR to mark the batch as ‘Processed by UPTR’.
- When this Preference is set to YES, UPTR will mark the batch as 'Processed', regardless of any errors located on Transactions in the batch.
In addition, ANY Time codes that do NOT have an associated PC must have the 'Bypass UPTR' toggle set to ON (in IDTC) to allow the preference to work properly.

This process creates one batch per run and creates pay headers within that batch, or, adds to existing pay headers with the matching EE, Pay Period and Pay Category.

If the 'Updating Existing Pays' toggle is set to ON, UPTR will attempt to locate a pay to use before creating a new one.

If multiple transaction batches are chosen in one UPTR run, any employees in multiple batches will have one pay header generated with multiple transactions.

What are the conditions when UPTR will create a new pay header even if the employee has an existing pay header for the same payroll already?

Many columns in a Pay Header are used for Taxation requirements as well as determining a ‘Payroll Code’.
Whether or not a new Pay Header is generated is determined by comparing the values in all of the columns and they all must match for the Employee Pay to be considered ‘Existing’.
The parameter ‘Demographics Source’ will be used to determine which date to use when comparing columns from the employee’s information, which will then determine if changes in the employee’s data will cause a new pay header to be generated.
The ‘Prior Period Separate’ toggle setting in UPTR is also used to determine if a new pay header will be generated.
This determination is done one transaction at a time, as the records are processed from IPTR. Theoretically, a separate Pay Header could be created from each Transaction.
The information that must be identical are:
- Employment Pay Category
- Pay Period
- Group
- School District
- Work State/Province
- Home State/Province
- Work Jurisdiction
- Home Jurisdiction
The determination of the ‘Group Code’ also depends on the setting in the GROUP_SOURCE column in IDWR

UPTR Report Parameters #

Field	Description
Entity	Mandatory, LOV available. Users can define a specific entity to be processed.
Pay Calendar	Mandatory, LOV Available. Users can define specific pay calendars identified to be processed.
Current Pay Period	Mandatory, LOV Available. Users can define specific pay periods to be processed.
Demographics Source	Mandatory, Date Source lexicon available. Defines the date to process employee information, which will then determine if changes in an employee’s data will generate a new pay header. The values are: 01-Use the Transaction Date 02-Use Pay Period End Date (default value) 03-Use Pay Issue date 04-Use Pay Period Start Date (for use with UPCPAY created pay headers)
Pay Issue Period	Optional, LOV Available. If this field is not defined, the system will derive the IPPH Pay Issue Date from the Pay Transaction with the latest Transaction date. If a Pay Period is defined, the system will use the associated Pay Issue date from the Pay Calendar.
Override Batch Code	Optional, Text. Users can enter a specific batch code to override.
Pay By	Optional, Pay By lexicon available. This field defines the payment method.
Prior Period Separate	Optional, Yes or No Default is No. When this field is set to Yes, transactions from a prior period will be generated into a separate pay header.
Create as Eligible	Optional, Yes or No lexicon available. When this field is set to YES, the pay header batch will be created as eligible.
Update Existing Pays	Optional, Yes or No lexicon available. When this field is set to YES, if a pay header already exists for this pay period and category, and is not calculated or closed, it will be updated with the transactions being processed.
Bypass if Paid in Period	Optional, Yes or No lexicon available. When this field is set to YES, the pay header will be bypassed if already paid in this period.
Exception Level	Optional, Exception Level lexicon available. This field defines the exception level (report messages) to be printed.

UPTR Report Filters #

Field	Description
Payroll	Optional, Multiple, and LOV available. Multiple payrolls can be defined for each execution of this function.
Pay Category	Optional, Multiple, and LOV available. Users must define the category that the batches and pay headers are to be processed under.
Batch Number	Optional, Multiple, and LOV available. Defines the pay transaction batch to be processed.

Notes #

Click to create a new notes page