UPTL can load pay transactions to IPTR, pay lines to IPPH, or leave lines to IAAL.
Transactions matching the selection criteria are processed up to and including the ‘As Of’ date (Cut-off date) supplied in the parameters. Position, job, department and wage information is taken from the “prime” assignment record unless it is supplied on the transaction.
Each transaction processed is validated. A single transaction can have one or more warnings or errors. Warnings do not prevent transactions from being loaded; errors do. Transactions that pass the validations without any errors are recorded on the appropriate Wiki table and then automatically deleted from the Loaded Pay Line table. Transactions with errors are left in the Loaded Pay Lines table. Transactions that have not been selected by the UPTL parameters are also left in the Loaded Pay Lines table for subsequent processing.
Audit text is provided on each transaction to identify the errors associated with it. All errors are reported on the exceptions report. Transactions with warnings are loaded but are also highlighted on the exceptions report. The exception report ONLY prints details for transactions where there are errors or warnings. The exception report prints control totals of the number of transactions processed, rejected and unprocessed. The exception report also shows the total hours processed and rejected.
UPTL loading depends on the chosen destination for the transactions. Each run of UPTL must be for a single destination. Destinations can be optionally provided on individual transactions if necessary.
If no pay period is supplied, the date of the transaction determines the pay period the transaction falls in. The Eligible and Approved flags of newly created batches are set as per the parameters. Valid transactions are loaded into Pay Transactions and Pay Trans Time Codes
Report Parameters | |
---|---|
Entity | Mandatory, LOV Available Entity for which the transactions are to be loaded. |
Payroll | Mandatory, LOV Available Only one payroll may be selected per execution of this function. |
From Date | Mandatory, Date, LOV Available Transactions are selected based on date. |
To Date | Mandatory, Date, LOV Available Transactions are selected based on date. |
Print Processed Lines | Optional, Toggle Lines that qualify for processing are physically removed from the flat file. |
Destination Type | Mandatory, LOV Available IPTR, IPPH, IAAL Do not select 'UFLOAD' or 'IPTS', as these choices are not valid for UPTL. The destination type of UFLOAD will only work for the UFLOAD function and IPTS type will only work for UPLTS. |
Create Pays When Needed | Optional, Toggle Toggle ON, new pays will be created if an existing one can not be located. |
Prior Period Separate | Optional, Toggle If ON, a new pay will be created if the transaction is in a prior period. If OFF, all transactions will be put into the current pay even if for a prior period. |
Create one PTR/PTL | Optional, Toggle If ON, each transaction will created a separate IPTR record even if for the same day. |
Create as Eligible | Optional, Toggle Toggle ON, batch in IPPH will be created as eligible, OFF eligible flag will be OFF. |
Batch PPH By | Mandatory, LOV Available Authorization Area, Department, Dept Batch Code, Event Site, Location, Manager, Payroll or Work Area |
Exception Level | Mandatory, LOV Available The level of logging desired. |
Show Color | Optional, Toggle If ON report will be in color, if OFF no color on report |
Report Filters | |
---|---|
Department | Optional, LOV Available |
Pay Category | Optional, LOV Available Only one pay category may be selected |
Select Batch Code | Optional, Text Users may enter a ten-character code to aid in determining the correct batch to find the pay header for these transactions. |
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