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

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
22 26-Nov-2021 10:22 5 KB kparrott to previous
21 26-Nov-2021 10:22 4 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
UPCALC
UPCALC

Version management

Difference between version and

At line 11 changed one line
UPCALC generates a pay run for each run according to [IMCS] Code Sequencing for [PAY_RUN_NUMBER] for entity. Payrun information can be viewed through the Pay Run Information ([IPVP]) form.
UPCALC generates a pay run for each run according to [IMCS] Code Sequenicng for [PAY_RUN_NUMBER] for entity. Payrun information can be viewed through the Pay Run Information ([IPVP]) form.
At line 13 removed 2 lines
Normally UPCALC will be executed according to the parameter setting 'Exception Level'. If a particular pay has been causing issues of some kind, it can be run at Utility Level by setting it in the [IPPH] screen, Trace Level field for the desired employee/pay.
At line 17 changed one line
If performance is an issue with UPCALC, the function may be configured to use multiple processing threads to speed up performance. For more information on this please see the page titled [Multiple Processing Threads|MULTIPLE PROCESSING THREADS] and [TIMER LOGGING CAPABILITY].
If performance is an issue with UPCALC, the function may be configured to use multiple processing threads to speed up performance. For more information on this please see the page titled [Multiple Processing Threads|MULTIPLE PROCESSING THREADS].
At line 25 changed one line
* [VERTEX TRACING]
At line 30 changed 8 lines
|Entity|Mandatory, LOV available. Limits the process to the entity specified.
|Payroll|Mandatory, LOV available. Only one payroll may be selected per execution of this function.
|Pay Period|Mandatory, LOV available. This is used to determine which timeframe the pays are to be processed for and is used when selecting the batches that are to be processed.
|Future Pay Period|Optional, date, LOV available. This will be used to allow for batches/pays that have future pay periods on them to be processed.
|Override Pay Issue|Optional, date, LOV available. When entered, this date will override the Pay Issue Date that is found on the Pay Calendar table [IPCL] for the Pay Period being processed
|Validate All Calendars|Optional, Toggle, Defaults to ‘No’. \\If ‘Yes’, will validate Calendars of all types. All regular calendars (IDCL) as well as Payroll Calendars (IPCL) are validated for date continuity as well as data integrity. Any errors are logged as exceptions. UPCALC will however continue after validation is complete.
|Validate Demographics|Optional, Toggle, Defaults to ‘No’. \\If ‘Yes’, at the beginning of the run, UPCALC will valid all Pay Headers of this Payrun and will print Warning messages when the Employee's demographic information has been changed since the Pay Headers were added
|Message Level|Optional, LOV available. This allows the user to choose which IMMS messages are to be included in the execution run log to print on the UPCALC report.\\00 - Not Specified\\01 - Errors Only\\02 - Warnings Only\\03 - Both
|Entity|Mandatory, LOV available
|Payroll|Mandatory, LOV available
|Pay Period|Mandatory, LOV available
|Future Pay Period|Optional, date, LOV available
|Override Pay Issue|Optional, date, LOV available
At line 39 removed 2 lines
|Show IPPP OVD Trace|Optional, Toggle, Defaults to ‘No’. \\If ‘Yes’, the [IPPP] 'Override Trace Level' of the a Pay Point Task will be read to trace all employees of thie Payrun at this Pay Point Task when UPCALC is run with Exception Level=0.
|Timer|Optional, LOV available\\The Timer selection is is a diagnostic tool for performance analysis. This feature is used by developers to enable this functionality.
At line 42 removed one line
At line 44 changed 8 lines
|People List Code|Optional, Multiple selections, LOV available. A people list may be used to indicate specific employees that are to be processed.
|Person Code|Optional, Multiple selections, LOV available. The person code(s) of specific employee(s) to be processed.
|Pay Category|Optional, Multiple selections, LOV available. Users can indicate which pay categories are to be processed. These pay categories will be compared to the batches to determine if the batch is to be selected.
|Department|Optional, Multiple selections, LOV available. Users can indicate which departments the employees are in are to be processed.
|Location|Optional, Multiple selections, LOV available. Users can indicate which locations the employees are in are to be processed.
|Unit|Optional, Multiple selections, LOV available. Users can indicate which units the employees are in are to be processed.
|Group|Optional, Multiple selections, LOV available. Users can indicate which groups the employees are in are to be processed.
|Batch Number|Optional Multiple selections, LOV available. Users can select which batches are to be processed.
|People List Code|Optional, Multiple selections, LOV available
|Person Code|Optional, Multiple selections, LOV available
|Pay Category|Optional, Multiple selections, LOV available
|Department|Optional, Multiple selections, LOV available
|Location|Optional, Multiple selections, LOV available
|Unit|Optional, Multiple selections, LOV available
|Group|Optional, Multiple selections, LOV available
|Batch Number|Optional Multiple selections, LOV available
This page (revision-22) was last changed on 26-Nov-2021 10:22 by kparrottTop