CALCULATE PAYROLL#
Processing Information#
All batches and transactions that have been audited and prepared up to the pay period indicated will be calculated according to the rules that have been previously established during set up.If transactions pass the audit stage through UPAUDT as ‘Audited’, then UPCALC (payroll calculation) may be run.
If this process is completed, the Audited, Balanced, and Eligible toggles in IPBE will be turned on. In addition, the system marks the pay headers (IPPH) in that batch so that the Stage field displays “Audit’ and that both the Audit and Preparation toggles are ON. After UPCALC, the pay stage is now ‘Calculated/Paid’ on the IPPH (Pay Header).
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.
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.
Allows a user to generate trial amounts, to confirm that the employee will be paid the correct amount and that the correct deduction amounts are calculated.
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.
Other topics pertaining to the UPCALC function are:
- ATTENDANCE IN PAYROLL
- BENEFITS IN PAYROLL
- UACALC VS.UPCALC
- CDN TAXATION
- U.S. TAXATION
- Timer Logging Capability
Report Parameters & Filters#
| Report Parameters | |
|---|---|
| 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 |
| Exception Level | Mandatory, LOV available ‘0 – 9’ available |
| 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 while UPCALC is run with Exception Level=0. |
| Report List Filters | |
|---|---|
| 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. |
