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

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
13 26-Nov-2021 10:22 5 KB mmcfarland to previous
12 26-Nov-2021 10:22 5 KB mmcfarland to previous | to last
11 26-Nov-2021 10:22 4 KB jmyers to previous | to last
10 26-Nov-2021 10:22 4 KB jmyers to previous | to last
9 26-Nov-2021 10:22 4 KB jmyers to previous | to last
8 26-Nov-2021 10:22 3 KB jmyers to previous | to last
7 26-Nov-2021 10:22 3 KB jmyers to previous | to last
6 26-Nov-2021 10:22 3 KB jmyers to previous | to last
5 26-Nov-2021 10:22 3 KB jmyers to previous | to last
4 26-Nov-2021 10:22 3 KB rforbes to previous | to last
3 26-Nov-2021 10:22 3 KB jmyers to previous | to last
2 26-Nov-2021 10:22 2 KB JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
UPCPAY
UPCPAY

Version management

Difference between version and

At line 4 changed one line
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.
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. \\ \\
At line 6 changed one line
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.
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. \\ \\
At line 8 changed one line
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].
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. Terminated employees are included only if an employee had at least one pay in the prior year. \\ \\
At line 10 changed one line
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.
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]. \\ \\
At line 12 changed one line
Pay categories are identified as ‘Regular Pay’ through the Regular Pay field on the Pay Category ([IPPGU] or [IPPGC]) form.
Organizations who manually enter transactions based on time sheets will use this function. \\ \\
At line 14 added 4 lines
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. \\
At line 15 changed one line
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.%%
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.%%
At line 17 changed one line
The Generate Pay Header of Transactions (UPCPAY) form will create the necessary batches and pay headers.
The Generate Pay Header of Transactions (UPCPAY) process will create the necessary batches and pay headers.
At line 19 removed 2 lines
----
!!Report Parameters & Filters
At line 22 changed 16 lines
||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|X_YES_NO] lexicon available\\If <YES>, the report will include only prime assignments only.
|Incl Prior Terminations|Optional,[Yes or No|X_YES_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|X_BATCH_TYPE] lexicon available\\This field will indicate the batch type
|Batching Method|Mandatory,[UPCPAY BATCH BY|X_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|X_PERSON_SORT] lexicon available\\This field will indicate how the people information will be sorted.\\
|Exception Level|Mandatory, LOV Available \\‘0 – 9’ available
!!UPCPAY Report Parameters
At line 26 added 17 lines
||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|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. Optional.
|Prime Assignment Only|When set to YES, the report will include only prime assignments only. [Yes or No|X_YES_NO] lexicon. Optional.
|Incl Prior Terminations|When set to YES, the report will include prior terminations. [Yes or No|X_YES_NO] lexicon. Optional.
|Terminated Sundry|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. Optional.
|Create Batch Code|Text field. Optional.
|Create Batch Type|Mandatory. Defines the batch type. [BATCH TYPE|X_BATCH_TYPE] lexicon
|Batching Method|Mandatory. Defines the batching method. [UPCPAY BATCH BY|X_UPCPAY_BATCH_BY] lexicon.
|Audit Text|Text field. Optional.
|Create as Eligible|When set to YES, the batches created will be eligible for UPCALC. [Yes or No|X_YES_NO] lexicon. Optional.
|Sort Employees By|Mandatory. Defines how the people information will be sorted. [Sort People By|X_PERSON_SORT] lexicon.
|Exception Level|Defines the exception level (report messages) to be printed. [Exception Level|X_TRACE_LEVEL] lexicon. Optional.
At line 40 changed 9 lines
||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
!!UPCPAY Report Filters
||Field||Description
|People List|Users can enter one or more people lists to process. Multiple selections allowed. Users can select from the LOV. Optional.
|Person|Users can enter one or more person codes to process. Multiple selections allowed. Users can select from the LOV. Optional.
|Location|Defines a specific location to process. Multiple selections allowed. Users can select from the LOV. Optional.
|Auth Area|Multiple selections allowed. Users can select from the LOV. Optional.
|Department|Defines a specific department to process. Multiple selections allowed. Users can select from the LOV. Optional.
|Unit|Defines a specific Unit to process. Multiple selections allowed. Users can select from the LOV. Optional.
|Group|Defines a specific Group to process. Multiple selections allowed. Users can select from the LOV. Optional.
|Status|Defines a specific Status to process. Multiple selections allowed. Users can select from the LOV. Optional.
This page (revision-13) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop