This page (revision-6) 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
6 26-Nov-2021 10:22 4 KB kparrott to previous
5 26-Nov-2021 10:22 4 KB JMyers to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 5 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 removed one line
[{TableOfContents }]
At line 3 changed one line
Pay Points are the entry points within the pay calculation process where different items of processing logic occur.
__Pay Points__ are the entry points within the pay calculation process where different items of processing logic occur.
At line 8 added one line
You may access this feature through the Screen/Form menu: __Payroll > Setup and Definitions > Define Pay Points__
At line 10 changed one line
Pay Point Types are used to classify specific groups for entry points which the Payroll Calculation process has special logic.
__Pay Point Types__ are used to classify specific groups for entry points which the Payroll Calculation process has special logic.
At line 12 changed one line
Pay Point Tasks are assigned to pay point types. A task may be an Personality logic routine (Legislative Calculations) or may be a user assigned routine (User Calculations, Benefit Plans,or Attendance Policies).
__Pay Point Tasks__ are assigned to pay point types. A task may be an [{$applicationname}] logic routine (Legislative Calculations) or may be a user assigned routine (User Calculations, Benefit Plans,or Attendance Policies).
At line 33 changed one line
All [pay components|PAY COMPONENTS] must be assigned to a pay point type in the Maintain Pay Components ([IPPC]) screen.
All pay components must be assigned to a pay point type in the Maintain Pay Components ([IPPC]) screen.
At line 51 added one line
__‘Define Pay Points’ Usage and Examples__
At line 53 changed 4 lines
;[Pay Point Set|PAY_POINT_SET_CODE]:Pay Point Set is a user assigned code that uniquely identifies the pay point set.
;[Description|DESCRIPTION]:Describes the purpose and usage of the pay point set.
;[Pay Point Set|PAY_POINT_SET_CODE]:Pay Point Set is a user assigned code that uniquely identifies the pay point set. Pay_Point_Set_Code is a mandatory 16-character alphanumeric field that you must manually enter.
;[Description|DESCRIPTION]:Describes the purpose and usage of the pay point set. Description is an optional 50-character alphanumeric field that will default in from the pay point set code.
At line 58 changed 19 lines
;[Pay Point Type|PAY_POINT_TYPE]:This field indicates the type of logic that is assigned to a pay point.
;[Seq #|PAY_POINT_SEQUENCE]:This field defines the order of the tasks within each pay point type. It is recommended that sequential numbering tasks are in intervals of ten. This will allow room to move tasks around if necessary.
;[Pay Point Task|PAY_POINT_TASK]:A Pay Point Task identifies the item being processed.
;[Description|DESCRIPTION]:This field holds the description of the pay point. It is recommended that the description be the pay point type followed by the pay point task.
;[Plan Code|PLAN_CODE]: This field calls the benefits calculation routine to calculate the plans indicated, if an employee is enrolled.
;[Leave Type Code|LEAVE_TYPE_CODE]:This field calls the Attendance Calculation routine to calculate those policies indicated for which the employee is eligible. This code can be used at all pay points.
;[User Calc Code|USER_CALC_CODE]:This field triggers the UserCalc indicated. The UserCalc code may be used for all pay point types.
;[Override Trace Level|TRACE_LEVEL]:This field will be read and used to trace all employees of a Payrun for this Pay Point Task when UPCALC is run with Exception Level = 0
----
![Notes|Edit:Internal.IPPP]
[{InsertPage page='Internal.IPPP' default='Click to create a new notes page'}]
;[Pay Point Type|PAY_POINT_TYPE]:This field indicates the type of logic that is assigned to a pay point. Pay_Point_Type is a mandatory fixed lexicon ([X_PAY_POINT_TYPE]) that you may use to look up the value.
;[Seq #|PAY_POINT_SEQUENCE]:This field defines the order of the tasks within each pay point type.High Line recommends sequential numbering tasks in intervals of ten. This will allow room to move tasks around if necessary. Pay_Point_Sequence is an optional 5 digit numeric field.
;[Pay Point Task|PAY_POINT_TASK]:A Pay Point Task identifies the item being processed. Pay_Point_Task is a mandatory fixed lexicon ([X_PAY_POINT_TASK]) that you may use to look up the value.
;[Description|DESCRIPTION]:This field holds the description of the pay point. High Line recommends that the description be the pay point type followed by the pay point task. Description is an optional 50-character alphanumeric field that you may manually enter.
;[Plan Code|PLAN_CODE]: This field calls the benefits calculation routine to calculate the plans indicated, if an employee is enrolled. Plan_Code from [P2K_BE_PLAN_DEFINITIONS] is an optional 16-character alphanumeric field that you may manually enter or use the LOV (F9) to choose an option.
;[User Calc Code|USER_CALC_CODE]:This field triggers the UserCalc indicated. The UserCalc code may be used for all pay point types. User_Calc_Code from [P2K_AM_USER_CALCS] is an optional 16-character alphanumeric field that you may manually enter or use the LOV (F9) to choose an option.
;[Leave Type Code|LEAVE_TYPE_CODE]:This field calls the Attendance Calculation routine to calculate those policies indicated for which the employee is eligible. This code can be used at all pay points. Leave_Type_Code from [P2K_AT_LEAVE_POLICY_TYPES] is an optional 16-character alphanumeric field that you may manually enter or use the LOV (F9) to choose an option.