Wiki: UPCPAY

UPCPAY - GENERATE PAY HEADERS#

Processing Information#

This feature provides the ability to mass generate large numbers of employee pay headers. It generates one payroll at a time and a single pay header per employee for the selected pay period.

UPCPAY only generates 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.

When the 'Incl Prior Terminations' parameter is set to 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. Terminiated employees are included only if an employee had at least one pay in the prior year.

The pay header generator automatically creates batches and pay headers. The generated batches then become part of the normal pay cycle and may be accessed through the Administer Batches (IPBE) process. This process does NOT mark generated transaction as ‘Audited’. In the same manner as any other pay header, pay headers generated by this function must be audited through (UPAUDT) before becoming eligible for calculation by UPCALC.

Organizations who 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 Define Pay Categories (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 set to 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) process will create the necessary batches and pay headers.

UPCPAY Report Parameters #

Field	Description
Entity	Mandatory. Defines the Entity to generate pay headers/transactions for. Users can select from the LOV.
Payroll	Mandatory. Defines the payroll to generate pay headers/transactions for. Users can select from the LOV.
Pay Period	Mandatory. Defines the payroll to generate pay headers/transactions for. Users can select from the LOV.
Pay Category	Mandatory. Defines the pay category to generate pay headers/transactions for. Users can select from the LOV.
ONLY Stat Code	Optional If a Stat code is defined, UPCPAY will generate pay headers for employees who have non-zero values in this Stat code. When a 'Stat Code' is defined, 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. When set to YES, the report will include only prime assignments only. Yes or No lexicon
Incl Prior Terminations	Optional. When set to YES, the report will include prior terminations. Yes or No lexicon
Terminated Sundry	Optional. If this element is defined, then terminated employees with sundries in this element will have a pay created. This can be used when a terminated employee must receive payments, such as a Bonus, after they have been terminated.
Create Batch Code	Optional. Text field.
Create Batch Type	Mandatory. Defines the batch type. BATCH TYPE lexicon
Batching Method	Mandatory. Defines the batching method. UPCPAY BATCH BY lexicon.
Audit Text	Optional. Text field.
Create as Eligible	Optional. When set to YES, the batches created will be eligible for UPCALC. Yes or No lexicon.
Sort Employees By	Mandatory. Defines how the people information will be sorted. Sort People By lexicon.
Exception Level	Optional. Defines the exception level (report messages) to be printed. Exception Level lexicon.

UPCPAY Report Filters #

Field	Description
People List	Optional. Users can enter one or more people lists to process. Multiple selections allowed. Users can select from the LOV.
Person	Optional. Users can enter one or more person codes to process. Multiple selections allowed. Users can select from the LOV.
Location	Optional. Defines a specific location to process. Multiple selections allowed. Users can select from the LOV.
Auth Area	Optional. Multiple selections allowed. Users can select from the LOV.
Department	Optional. Defines a specific department to process. Multiple selections allowed. Users can select from the LOV.
Unit	Optional. Defines a specific Unit to process. Multiple selections allowed. Users can select from the LOV.
Group	Optional. Defines a specific Group to process. Multiple selections allowed. Users can select from the LOV.
Status	Optional. Defines a specific Status to process. Multiple selections allowed. Users can select from the LOV.

Notes #

Click to create a new notes page