UPCPAY will only generate a ‘regular pay’ header for an employee if there is no other pay header identified as ‘regular pay’ for that period. It also will not select an employee if the hire date is greater than the period end date or if the termination date is less than the period begin date.
The pay header generator will automatically create batches and pay headers. The generated batches then become part of the normal pay cycle and may be accessed via the Batch Control (IPBE) function. This function does NOT mark generated transaction as ‘Audited’. In the same manner as any other pay header, those generated by this function must be audited (UPAUDT) before becoming eligible for calculation by UPCALC.
Those clients who need to manually enter transactions based on time sheets will use this function. Employees will be processed if they are paid Weekly, Biweekly, Semi-Monthly, or Monthly.
Pay categories are identified as ‘Regular Pay’ through the Regular Pay field on the Pay Category (IPPGU or IPPGC) form.
Terminated employees are always selected when the Termination date is within the pay period. When the 'Inc Prior Terminations' parameter is ON during the first pay period of a year, employees that were terminated in the last pay period of the prior year can be included as well. The terminated employee is included only if the employee has a least on pay in the prior year.The Generate Pay Header of Transactions (UPCPAY) form will create the necessary batches and pay headers.
Report Parameters | |
---|---|
Entity | Mandatory, LOV Available |
Payroll | Mandatory, LOV Available |
Pay Period | Mandatory, LOV Available |
Pay Category | Mandatory, LOV Available |
ONLY Stat Code | Optional If a Stat code is specified, UPCPAY will generate pay headers for employees who have non-zero values in this Stat code. When you enter a 'Stat Code', a pay will NOT be generated if there are any unprocessed transactions in IPTR for the employee in any pay period. |
Prime Assignment Only | Optional,Yes or No lexicon available If <YES>, the report will include only prime assignments only. |
Incl Prior Terminations | Optional,Yes or No lexicon available If <YES>, the report will include prior terminations. |
Terminated Sundry | Optional If this element is provided, then terminated employees with sundries in this element will have a pay created. This facilitates situations where a terminated employee must receive payments (eg. Bonus) after they have been terminated. |
Create Batch Code | Text, Optional, Manual |
Create Batch Type | Mandatory,BATCH TYPE lexicon available This field will indicate the batch type |
Batching Method | Mandatory,UPCPAY BATCH BY lexicon available This field will indicate the batching method. |
Audit Text | Optional, Text, Manual |
Create as Eligible | Optional Toggle, ON or OFF |
Sort Employees By | Mandatory,Sort People By lexicon available This field will indicate how the people information will be sorted. |
Exception Level | Mandatory, LOV Available ‘0 – 9’ available |
Report Filters | |
---|---|
People List Code | Optional, Multiple selections, LOV available |
Person Code | Optional, Multiple selections, LOV available |
Department | Optional, Multiple selections, LOV available |
Authorization | Optional, Multiple selections, LOV available |
Location | Optional, Multiple selections, LOV available |
Unit | Optional, Multiple selections, LOV available |
Group | Optional, Multiple selections, LOV available |
Status | Optional, Multiple selections, LOV available |
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