This page (revision-18) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
18 26-Nov-2021 10:22 8 KB Karen Parrott to previous
17 26-Nov-2021 10:22 8 KB Karen Parrott to previous | to last
16 26-Nov-2021 10:22 8 KB Karen Parrott to previous | to last
15 26-Nov-2021 10:22 7 KB Lilia Urtan to previous | to last
14 26-Nov-2021 10:22 7 KB jtolentino to previous | to last
13 26-Nov-2021 10:22 7 KB mmcfarland to previous | to last
12 26-Nov-2021 10:22 6 KB rforbes to previous | to last
11 26-Nov-2021 10:22 6 KB kparrott to previous | to last
10 26-Nov-2021 10:22 6 KB rforbes to previous | to last
9 26-Nov-2021 10:22 6 KB kparrott to previous | to last
8 26-Nov-2021 10:22 5 KB rforbes to previous | to last
7 26-Nov-2021 10:22 5 KB JEscott to previous | to last
6 26-Nov-2021 10:22 5 KB JEscott to previous | to last
5 26-Nov-2021 10:22 5 KB JEscott to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 5 KB JEscott to last

Page References

Incoming links Outgoing links
UPTL
UPTL

Version management

Difference between version and

At line 2 changed one line
This function imports 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]. \\ \\
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].
At line 4 changed 4 lines
UPTL can load:
*Pay transactions to [IPTR]
*Pay lines to [IPPH] or
*Leave lines to [IAAL]
UPTL can load pay transactions to [IPTR], pay lines to [IPPH], or leave lines to [IAAL].
At line 9 changed one line
Transactions matching the selection criteria are processed up to and including the ‘As Of’ date (Cut-off date) defined in the parameters. Position, job, department and wage information is taken from the “Prime” assignment record unless it is provided on the pay transaction. Each transaction processed is validated. \\ \\
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.
At line 11 changed one line
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 validation without any errors are recorded on the appropriate Personality table and then automatically deleted from the Loaded Pay Line table, if the 'Remove Loaded Lines' parameter is set to YES. \\ \\
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 Personality 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.
At line 13 changed 10 lines
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
* Prints control totals of the number of transactions processed, rejected and unprocessed
* 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 are optional and can be defined on individual transactions, if necessary.
Removing loaded pay lines depends on the parameter. If set to YES, then all lines that are ’02-Loaded Clean’ and ’03-Loaded with Warnings’ will be removed from the file. If set to NO, then all lines will remain in the file after UPTL is completed.
\\ \\
When UPTL is launched, the employment record will be determined using the entry date from the IPTL.
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.
At line 24 changed one line
The employment record will be selected if: \\
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.
Removing loaded pay lines depends on the parameter; If YES, then all lines that are ’02-Loaded Clean’ and ’03-Loaded with Warnings’ will be removed from the file. If NO, the all lines will remain in the file after UPTL has completed.
At line 26 removed 5 lines
a) The employment type matches the value provided on the IPTL form. \\
b) The Transaction date from IPTL falls between the Hire Date and the Termination Date from the employment record. The system will assume the end of time value of 31-Dec-3999 for records where there is no termination date.
If multiple records are found that meet these specifications, the qualifying record with the most recent hire date will be used.
At line 33 changed one line
[IPTR] transactions are processed by batch code, if defined on IPTR. If the batch code is not defined, the transactions will be batched by payroll. New [IPTR] batches are created as required.\\ \\
[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.
At line 35 changed one line
If no pay period is defined, 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 defined on the parameters. Valid transactions are loaded into Pay Transactions and Pay Transactions Time Codes.
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
At line 37 removed 2 lines
When the IPTL record has the Work Tax Jurisdictions (GNIS Code), it will be considered an override on the Work Jurisdiction for the ITR form. The overridden Work Jurisdiction will be written on to the IPTR records.
At line 41 changed 2 lines
Valid transactions are turned into pay lines and pay line details. 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 through the Create Pay Header [UPCPAY] function. Pays are created only when the 'Create Pays When Needed' toggle is set to ON. \\ \\
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.
At line 44 changed one line
# The batch codes must be the same. This means for UPTL that either they were supplied to match or that both were batched by payroll.
# 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.
At line 47 changed one line
# The batch must have the same Pay Category as the [IPTL] line.
# The batch must have the same Pay Category as the [IPTL] row.
At line 49 changed one line
# The Audited flag should be set to OFF.
# The Audited flag should be off.
At line 51 removed 2 lines
When the IPTL record has the Work/Home Tax Jurisdictions (GNIS Code), it will be considered an override on the Work/Home Jurisdiction for the IPPH form. A new Pay Header will be created on IPPH for each jurisdiction.
At line 55 changed 5 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.
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.
At line 61 changed one line
When loading leave transactions into payroll, if an employee leave accrual balance has been exceeded:
When loading leave transactions into payroll if the employee leave accrual balance has been exceeded;
At line 63 changed 3 lines
# If IALP is set to No Warn, Allow - Transactions will load through UPTL
# If IALP is set to Warn but Alllow - Transactions will load through UPTL
# If IALP is set to Error, Do not Allow - Transactions will NOT load through UPTL and must be entered manually.
# If IALP is set to No Warn, Allow - Transactions will load via UPTL
# If IALP is set to Warn but Alllow - Transactions will load via UPTL
# If IALP is set to Error, Do not Allow - Transaction will NOT load via UPTL and must be handled manually.
At line 68 changed 18 lines
!UPTL Report Parameters
||Field||Description
|Entity|Mandatory. Defines the Entity the transactions are to be loaded for. \\LOV Available
|Payroll|Mandatory. Defines the payroll the transactions are to be loaded for.\\NOTE: Only one payroll can be selected per execution of this function. \\LOV Available
|From Date|Mandatory. Defines the start date to process the transactions for.
|To Date__|Mandatory. Defines the end date to process the transactions for.
|Print Processed Lines|When this toggle is set to YES, any lines that qualify for processing will be reported. \\Optional.
|Remove Loaded Lines__|When this toggle is set to YES, any lines that qualify for processing will be physically removed from the flat file (IPTL).
|Destination Type|Mandatory. Select [IPTR], [IPPH] or [IAAL] \\NOTE: Do not select 'IPTS', as it is not valid for UPTL. The IPTS type will only work for [UPLTS]. \\LOV Available
|Batch|Defines the transaction batch that is to be processed. \\Optional. LOV Available
|Create Pays When Needed|For generating IPPH pays.\\When this toggle is set to ON, new pays will be created, if an existing one can not be located. \\Optional
|Prior Period Separate|For generating IPPH Pays. \\When this toggle is set to ON, a new pay will be created if the transaction is in a prior period.\\When this toggle is set to OFF, all transactions will be put into the current pay, even if they are from a prior period. \\Optional
|One PTR per PTL|When this toggle is set to ON, each transaction will create a separate [IPTR] record, even if it is for the same day. \\Optional
|Create Eligible Pays|When this toggle is set to ON, the batch in [IPPH] will be created as eligible. When this toggle is set to OFF, the eligible flag will be OFF.\\This is used ONLY when creating pays (IPPH) records. When loading to IPTR, this parameter is not used. \\Optional
|Pick Up Not Loaded|When this toggle is set to ON, transactions that were in error will be picked up and processed again, without having to change the 'UPTL Status’ field to ‘To be Loaded’.
|Batch By|Mandatory. Defnes how the transactions will be batched. Options are: Authorization Area, Department, Dept Batch Code, Event Site, Location, Manager, Payroll or Work Area. \\LOV Available
|Exception Level|Mandatory. Defines the level of detail to be included in the report. \\LOV Available
|User Comment|Users can enter text that will print on the header of all pages of the report.
||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 reported on the output report.
|__Remove Loaded 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 'IPTS', as this choice is not valid for UPTL. IPTS type will only work for [UPLTS].
|__Batch__|__Optional, LOV Available__ \\This is the transaction batch that is to be processed.
|__Create Pays When Needed__|__Optional, Toggle__ For generating IPPH Pays\\Toggle ON, new pays will be created if an existing one can not be located.
|__Prior Period Separate__|__Optional, Toggle__ For generating IPPH Pays\\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.
|__One PTR per PTL__|__Optional, Toggle__ \\If ON, each transaction will create a separate [IPTR] record even if for the same \\day.
|__Create Eligible Pays__|__Optional, Toggle__\\Toggle ON, batch in [IPPH] will be created as eligible, OFF eligible flag will be OFF.\\This is used ONLY when creating pays (IPPH) records. When loading to IPTR, this parameter is not used.
|__Pick Up Not Loaded__|__Optional, Toggle__\\Toggle ON, transactions that were in error will be picked up and processed again, without having to change the 'UPTL Status’ field to ‘To be Loaded’.
|__Batch 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.
|__User Comment__|__Optional, Toggle__\\This field holds the user-supplied comment which will appear in the header of all pages of the report.
At line 87 changed 4 lines
!UPTL Report Filters
||Field||Description
|Department|Defines a specific department to run the process for. Optional. LOV Available
|Pay Category|Defines a specific pay category to run the process for. \\NOTE: Only one pay category can be selected per execution of this function.\\Optional. LOV Available
||Report Filters||
|__Department__|__Optional, LOV Available__
|__Pay Category__|__Optional, LOV Available__ \\Only one pay category may be selected
This page (revision-18) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop