!!!LOAD PAY LINES
This function provides a means to import transactions from the Loaded Pay Lines table. This table must be populated with data from either an external source through the use of [LMTD] or manually entered into the form [IPTL]. The result is one or more batches of validated transactions ready for the Transaction Audit report ([UPAUDT]).

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 [{$applicationname}]  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.

----
!![IPTR] - Pay Transactions
[IPTR] transactions are processed by batch code, if supplied. If the batch code is not supplied, the transactions will be batched by payroll. New [IPTR] batches are created as required.

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

----
!![IPPH] - Pay Lines
Valid transactions are turned into pay lines and pay line details and if no matching pay header exists a new pay header is created. Existing batches and pay headers that have transactions added to them are marked as ‘to be audited’. Pay Headers can be pre-generated via the [UPCPAY]-Create Pay Header function. Pays are created only when the Create Pays When Needed toggle is on.
There are a number of conditions that must be met for UPTL to use an existing batch:
# The batch codes must be the same. This means for UPTL that either they were supplied to match or that both sides were batched by payroll.
# Batch Status must be 00 - Active.
# Batch Type must be 01 - Pay Header
# The batch must have the same Pay Category as the [IPTL] row.
# The Balanced flag must be null.
# The Audited flag should be off.

----
!![IAAL] - Leave Lines
Valid transactions for leave entitlements and leave time taken are turned into leave lines. The Accrual status is set to “not updated”. No leave line details are created. The Entitlement Earned flag is turned on for entitlements. The new Leave Reason field becomes the [IAAL] Leave Reason.
----
||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]’, as this choice is valid ONLY when executing the function \\'[UFLOAD]'. The UFLOAD destination type will do nothing in UPTL.
|__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.


[{If var='loginstatus' contains 'authenticated'

----
![Discussion|Edit:Internal.UPTL] 	
[{InsertPage page='Internal.UPTL' default='Click to create a new discussion page'}] 	

}]