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

This page was created on 26-Nov-2021 10:22 by UnknownAuthor

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
6 26-Nov-2021 10:22 6 KB mmcfarland to previous
5 26-Nov-2021 10:22 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 2 KB JMyers 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 JMyers to previous | to last
1 26-Nov-2021 10:22 46 bytes UnknownAuthor to last

Page References

Incoming links Outgoing links
UPFILL
UPFILL

Version management

Difference between version and

At line 1 changed 3 lines
!!!GENERATE FILL HOURS
The UPFILL function evaluates employees in specified Groups and ensures that their paid hours match a specified amount. Example: Employees in Group ‘FT OSAP’ are guaranteed 80 hours biweekly and hours are adjusted up or down to ensure that employees in this group are paid for exactly 80 hours. \\
!!!PROCESS EQUIPMENT JOURNALS FROM TIME SHEET ENTRIES
\\
At line 5 changed one line
There must be an existing pay in an ‘Audited’ or ‘To be Audited’ stage or the employee will not be processed. These employees are identified by an appropriate exception message. \\
The (UPEQPTS) file allows you to process equipment journals from time sheet enteries.
At line 7 removed 50 lines
* Any pay that has a Pay Line inserted will be reset to the ‘To be Audited’ stage. The ‘UPAUDT’ audit report must be executed before these revised pays can be calculated.
* Any hours inserted are on a separate Pay Line so that distribution and Premiums can be attached appropriately to the new lines. The Pay Component used on these Pay Lines is determined by the ‘PC Usage’ of ‘UPFILL Hours’.
**This process will only ever insert Pay Lines with ‘Hours’ and dollars (Normal and Premiums) and are generated through the Pay Component definition of the ‘UPFILL’ Pay Component.
* An element (on IPPE) must be created to hold the hours which are utilized by the process. This element is entered as a report parameter when executing the UPFILL process.
* The number of hours worked in a pay period is obtained from the ‘Std Hours per Pay’ on the Work Rule (IDWR) associated with the employees Group (IDGR).
* Certain employees can be exempt and should be bypassed. These employees are identified by a User Field attached to the employee’s ‘Personal’ record.
* If there is more than one Pay Header for an employee, then all pays are reviewed to determine the hours worked, however there must be an existing pay for the prime assignment to insert the UPFILL hours.
* If an employee is hired or terminated mid period, then the adjustment is prorated based on the number of Weekdays in the Pay Period.
!Setting up the UPFILL Pay Component
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’.
!Setting Up Exempt Employees
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.
!Hours Element
The UPFILL process requires that an element (on IPBE) be set up to determine the Pay Components (Hours) to be accumulated.
* Ensure that the “UPFILL Hours” Pay Component is included in this element. This allows the UPFILL process to be executed more than once, without incorrect adjustments.
!Employee Selection
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.
!UPFILL Method
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.
!REPORTING
The UPFILL process generates an exception report which includes:
* Total Employees Processed
* Total Pay Lines Inserted
* Exceptions for Employees Bypassed
* Exceptions reporting employees filled including hours
* Total Hours Filled
At line 64 changed 5 lines
|Fill Method|Mandatory, [Fill Method|X_UPFILL_METHOD] lexicon available\\This field allows you define the fill method for this process.
|Fill By Week|Optional, [Yes or No|X_YES_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|X_YES_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|X_YES_NO] lexicon available//If <Yes>, the report will use the PC distribution mask.
|From/To Date|Mandatory, Date, LOV Available\\Only information that falls within these dates will be processed.
|EQ Time Code|Optional,LOV available\\This field lets you identify the equipment time code associated with the report.
|EQ Request File|Optional, Text\\This field allows you to provide an interface file name for the equipment.
|EQ Errors File|Optional, Text\\This field allows you to provide an interface file name for the equipment errors.
|Interface Directory|Mandatory, Text\\This field must indicate a directory on the [data base server|DATA BASE SERVER] for which the current user (as signed onto the \\client’s network) has write capability. For example the entry ‘C:\TEMP’ accesses the \\‘TEMP’ directory on the server, not the local directory for the computer terminal\\ being used.
|Trial Interface Run|Optional, [Yes or No|X_YES_NO] lexicon available//You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>.
At line 70 removed one line
|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.
At line 75 changed 6 lines
|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.
|Time Sheet Status|Optional, Multiple Selection Available, LOV Available\\This will limit the report to the time sheet statuses selected.
At line 26 added 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 83 changed 2 lines
![Notes|Edit:Internal.UPFILL]
[{InsertPage page='Internal.UPFILL' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.UPFILL]
[{InsertPage page='Internal.UPFILL' default='Click to create a new discussion page'}]
At line 32 added 2 lines
}]
This page (revision-6) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop