This page (revision-6) was last changed on 26-Nov-2021 10:22 by jmyers

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

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
6 26-Nov-2021 10:22 3 KB jmyers to previous
5 26-Nov-2021 10:22 3 KB jmyers to previous | to last
4 26-Nov-2021 10:22 3 KB jmyers to previous | to last
3 26-Nov-2021 10:22 4 KB jmyers to previous | to last
2 26-Nov-2021 10:22 1 KB jmyers to previous | to last
1 26-Nov-2021 10:22 46 bytes UnknownAuthor to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 2 lines
[{TableOfContents }]
At line 2 removed 2 lines
The UPTRLB form loads pay transactions into existing Pay Headers that match a specified pay category for the person, pay period and payroll. It does not create Pay Headers or Batches so if there is no Pay Header found the time will be left in Pay Transactions and will be recorded as exceptions. All Pay Lines added will be ‘Generated’ within the previously closed Pay Header.
At line 5 changed one line
Although there is ‘Trial’ capabilities, there is no undo process to cancel or redo what has been updated by the process.
!!Overview
The Pay Transaction Labor Merge (UPTRLB) form loads pay transactions into existing pay headers that match a specified pay category for the person, pay period and payroll. It does not create either pay headers or batches so if no pay header is found, the time will be left in pay transactions and will be recorded as exceptions. All pay lines added will be generated within the previously closed pay header.
At line 7 changed one line
UPGL can then be run against the closed Pay that now contains both the dollars and the worked labour time.
Although there is a ‘Trial’ capability with this form, there is no undo process to cancel or redo what has been updated by the process.
At line 9 changed one line
Note that UPTRLB updates the ‘To Date’ files the same way that UPCLOZ does. There is no way to ‘Undo’ the UPCLOZ process so it would be wise to run this trial or have some other method of ensuring that the hours are correct before running this process in update mode.
After UPTRLB has been run, [UPGL] can then be run against the closed pay that now contains both the dollars and the worked labor time.
At line 12 added one line
%%information UPTRLB updates the ‘To Date’ files the same way that [UPCLOZ] does. There is no way to undo the UPCLOZ process, so it would be wise to run this trial or have some other method of ensuring that the hours are correct before running this process in update mode.%%
At line 14 added 2 lines
!!Transactions that affect Net Pay
Since the Time transactions being merged are for a period where the employee has already been paid, any transaction that generates money that would affect net pay is not valid.
At line 17 added one line
It is possible for leaves to generate money, but it is not a requirement. If any are encountered, an exception message is issued and the transaction is left behind in the original batch.
At line 19 added one line
If any premiums that generate money are encountered, an exception message is issued and the transaction is also bypassed.
At line 15 changed 4 lines
2 Transactions that affect Net Pay
Since the ‘Time’ transactions being merged are for a Period where the employee has already been paid, any transaction that generates money that would affect Net Pay is not valid.
It is possible for Leaves to generate money, but it is not a requirement. If any are encountered an exception message is issued and the transaction is left behind in the original Batch.
If any Premiums are encountered that generate money are encountered, then an exception message is issued and the transaction is also bypassed.
----
!!Report Parameters & Filters
At line 20 changed 6 lines
3 Report Parameter Form
The user enters the Pay Period of the Pay Transactions (IPTR) that are to be merged into existing closed Pay Headers in the same Pay Period. Only Time codes that are tied to Pay Components that are PC Usage of ‘Time’ are selected. Any other type of time will be logged as an exception, and the transaction will be bypassed.
There must be a closed Pay for the employee in the same Pay Period as the one selected, otherwise an exception message is issues and the transaction is bypassed.
All bypassed transactions are left in the original batch and the batch will remain active.
Batches of Time are marked as ‘Processed by UPTR’ if all transaction are taken into Payroll. If there are any errors, then the batch will be left open (Active).
Enter the pay period of the pay transactions [IPTR] that are to be merged into existing closed pay headers within the same pay period. Only Time codes tied to pay components that are PC Usage of ‘Time’ are selected. Any other type of time will be logged as an exception and the transaction will be bypassed.
At line 27 changed one line
There must be a closed pay for the employee in the same pay period as the one selected, otherwise an exception message is issued and the transaction is bypassed.
At line 29 changed 2 lines
4 Sample Output
This sample output shows transactions that are left in the original batch due to errors.
All bypassed transactions are left in the original batch and the batch will remain active.
At line 32 changed one line
Batches of Time are marked as ‘Processed by UPTR’ if all transaction are taken into Payroll. If there are any errors, then the batch will be left open (Active).
At line 34 removed 22 lines
For Customer Support
Any questions, comments, or suggestions for High Line may be entered on-line at:
http://www.highlinecorp.com//ccare/login.htm
Please contact your Application Administrator if you are not a registered user.
----
!!Report Parameters & Filters
At line 44 added 4 lines
!!Sample Output
This sample output shows transactions that are left in the original batch due to errors.\\ \\
[UPTRLB_01.JPG]
At line 74 removed one line
[cleanup]