The Pay Component used to insert the UPFILL Pay Lines must be set up in IPPC. It must have the ‘PC Usage’ of UPFILL. This is how the UPFILL process determines the Pay Component to use. The Pay Component must be Hours and must be Usage ’22 – UPFILL Hours’.
In addition, the Hours Pay Component MUST be stored into the Pay Line Detail as PC Detail Type ‘Entered Value’.
Optionally, employees can be exempt from the UPFILL process. To exempt employees, a user field must be attached to the ‘Personal’ table (P2K_HR_PERSONALS). This user field MUST use the ‘X_YES_NO’ lexicon.
When this User Field is set to YES, the employee will be exempt, based on the ‘Pay Period Begin Date’ and the ‘Personal’ Date Effective record.
Since the ‘Personal’ record is date sensitive, the exemption can be turned on and off in advance.
The UPFILL process requires that an element (on IPBE) be set up to determine the Pay Components (Hours) to be accumulated.
The UPFILL process provides flexible employee selection capabilities, to identity the Groups of employees that should be processed. Once the selection criteria are defined correctly, it can be saved as a ‘Named Parameter Set’ and be set as the default. This saved parameter set can be reused for each Pay Period.
The ‘Fill Method’ report parameter determines how Hours will be determined. Employee Pays can be incremented, decremented, or both, depending of the setting of this parameter.
The UPFILL process generates an exception report which includes:
Report Parameters | |
---|---|
Entity | Mandatory,LOV available This field lets you identify the entity associated with the report. |
Payroll | Mandatory,LOV available This field lets you identify the payroll associated with the report. |
Pay Period | Mandatory,LOV available This field lets you identify the pay period associated with the report. |
Fill Method | Mandatory, Fill Method lexicon available This field allows you define the fill method for this process. |
Fill By Week | Optional, Yes or No lexicon available If <Yes>, the fill will be done by week. |
Hours Element | Mandatory, LOV available This field allows you to choose the hours element for this report. |
Trial Run | Optional, Yes or No lexicon available//You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>. |
Use PC Distr Mask | Optional, Yes or No lexicon available//If <Yes>, the report will use the PC distribution mask. |
Exception Level | Mandatory, Exception Level lexicon available This field defines the exception level (report messages) required. |
User Comments | Optional, Text This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other. |
Report Filters | |
---|---|
People List | Optional, Multiple Selection Available, LOV Available This will limit the report to the people lists selected. |
Person | Optional, Multiple Selection Available, LOV Available This will limit the report to the persons selected. |
Department | Optional, Multiple Selection Available, LOV Available This will limit the report to the departments selected. |
Auth Area | Optional, Multiple Selection Available, LOV Available This will limit the report to the authorization areas selected. |
Location | Optional, Multiple Selection Available, LOV Available This will limit the report to the locations selected. |
Unit | Optional, Multiple Selection Available, LOV Available This will limit the report to the units selected. |
Group | Optional, Multiple Selection Available, LOV Available This will limit the report to the groups selected. |
Employment Status | Optional, Multiple Selection Available, LOV Available This will limit the report to the employment statuses selected. |
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