PAY TRANSACTION LABOR MERGE#
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.Although there is ‘Trial’ capabilities, there is no undo process to cancel or redo what has been updated by the process.
UPGL can then be run against the closed Pay that now contains both the dollars and the worked labour time.
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.
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.
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).
4 Sample Output This sample output shows transactions that are left in the original batch due to errors.
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#
| Report Parameters | |
|---|---|
| Entity | Mandatory, LOV available This field limits the process to the entity specified. |
| Pay Calendar | Mandatory, LOV available This field limits the process to the pay calendar specified. |
| Current Pay Period | Mandatory, LOV available This field limits the process to the current pay period specified. |
| Exception Level | Optional, Exception Level lexicon available A ‘trace’ report of exception messages may be produced to assist in the testing phase. This field defines the exception level (report messages) required. |
| Trial | Optional, Yes or No lexicon available//You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>. |
| User Comments | Optional, Text This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other. |
| Report Filters | |
|---|---|
| Payroll | Optional, LOV Available This field is used to limit the report to the payrolls indicated. |
| Pay Category | Optional, LOV Available This field is used to limit the report to the pay categories indicated. |
| Batch Number | Optional, LOV Available This field is used to limit the report to the batch numbers indicated. |
