This page (revision-78) was last changed on 02-Dec-2021 08:39 by Kevin Higgs

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

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
78 02-Dec-2021 08:39 25 KB Kevin Higgs to previous
77 18-Nov-2021 16:36 25 KB Kevin Higgs to previous | to last
76 26-Nov-2021 10:22 24 KB Meg McFarland to previous | to last
75 26-Nov-2021 10:22 24 KB mmcfarland to previous | to last
74 26-Nov-2021 10:22 24 KB kparrott to previous | to last
73 26-Nov-2021 10:22 24 KB kparrott to previous | to last
72 26-Nov-2021 10:22 24 KB kparrott to previous | to last
71 26-Nov-2021 10:22 23 KB jescott to previous | to last
70 26-Nov-2021 10:22 23 KB rforbes to previous | to last
69 26-Nov-2021 10:22 23 KB jmyers to previous | to last
68 26-Nov-2021 10:22 23 KB jmyers to previous | to last
67 26-Nov-2021 10:22 22 KB jmyers to previous | to last
66 26-Nov-2021 10:22 22 KB jmyers to previous | to last
65 26-Nov-2021 10:22 22 KB jmyers to previous | to last
64 26-Nov-2021 10:22 22 KB jmyers to previous | to last
63 26-Nov-2021 10:22 22 KB jmyers to previous | to last
62 26-Nov-2021 10:22 22 KB jmyers to previous | to last
61 26-Nov-2021 10:22 22 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
IPPC
IPPC

Version management

Difference between version and

At line 4 changed one line
__Pay Components__ are any identifiable components of a pay, or any item that requires the ability to be stored or totaled. Pay components are used to store all the data calculated by the pay calculation.
[Pay Components|PAY COMPONENTS] are any identifiable components of a pay, or any item that requires the ability to be stored or totaled. Pay components are used to store all the data calculated by the pay calculation.
At line 6 changed one line
You may define and maintain pay components through the Define Pay Components (IPPC) form.
You may define and maintain [pay components|PAY COMPONENTS] through the Define Pay Components (IPPC) form.
At line 10 changed one line
Pay Component Data is stored in the [P2K_PR_PAY_COMPONENTS], [P2K_PR_PC_RULES] and [P2K_PR_PC_DETAILS] tables.
[Pay Component|PAY COMPONENTS] Data is stored in the [P2K_PR_PAY_COMPONENTS], [P2K_PR_PC_RULES] and [P2K_PR_PC_DETAILS] tables.
At line 13 changed 7 lines
;[PC Code|PC_CODE]:A PC code is a unique number code from 1 to 9,999 assigned to uniquely identify the paycomponent within the system. PC_Code is a 4-character numeric mandatory field that you must manually enter.
;[Abbr.|PC_ABBREVIATION]:This field holds the short alpha description of the pay component used for printing on check and deposit statements, lists and pay registers. Although this field accepts 30 characters, you should keep your abbreviation as short as possible. PC_Abbreviation is a 30-character alphanumeric mandatory field that you must manually enter.
;[Desc|DESCRIPTION]: This field displays a longer description of the pay component than may be entered in the abbreviation. Description is a 50 character alphanumeric mandatory field that you must manually enter.
;[PC Usage|PC_USAGE_CODE]:This field is used to categorize when and how the pay component is to be used during the pay calculation. For example, the Usages of Net Pay indicates that this will be the Pay Component used to store the net Pay amount that is calculated through [UPCALC] (Payroll Calculation). PC_Usage_Code from [P2K_PR_PC_USAGES] is a numeric value that you may manually enter or use the LOV (F9).
;[Usage Desc|DESCRIPTION]: This field gives a short description of the usage, specifically when and how the pay component is to be used during the pay calculation. For example, the Usages of Net Pay indicates that this will be the Pay Component used to store the net Pay amount that is calculated through [UPCALC] (Payroll Calculation). PC_Usage_Description from [P2K_PR_PC_USAGES] is an alphanumeric value that defaults from the usage.
;[Store Results|STORE_RESULTS]: If this toggle is checked, the value(s) of the pay component amount will be stored in detail in the PC Amount table and accumulated in the to-date PC Amount table. This option would be used for all Pay Register amounts. If the toggle is not checked, the pay component amount will not be stored or accumulated. This option is used for items such as rates used in calculations, or indicators used to trigger special processing. Store Results toggle must be checked in order for a Statistical pay component (usage 14) to work correctly. If this toggle is not checked, information will not be stored in the statistic attached to the pay component. Store_Results is an optional toggle field.
;[Assoc. PC|PC_CODE]: Associated pay components are used to store the number of another pay component that may be associated with this PC. For example, if the PC being defined were a Time PC then the Earnings PC would be its Assoc. PC. This field may need to be left blank until all of your pay components are completed. PC_Code is an optional 4 digit numeric field that you may manually enter or use the LOV (F9).
;[PC Code|PC_CODE]:A PC code is a unique number code from 1 to 9,999 assigned to uniquely identify the [pay component|PAY COMPONENTS] within the system. PC_Code is a 4-character numeric mandatory field that you must manually enter.
;[Abbr.|PC_ABBREVIATION]:This field holds the short alpha description of the [pay component|PAY COMPONENTS] used for printing on check and deposit statements, lists and pay registers. Although this field accepts 30 characters, you should keep your abbreviation as short as possible. PC_Abbreviation is a 30-character alphanumeric mandatory field that you must manually enter.
;[Desc|DESCRIPTION]: This field displays a longer description of the [pay component|PAY COMPONENTS] than may be entered in the abbreviation. Description is a 50 character alphanumeric mandatory field that you must manually enter.
;[PC Usage|PC_USAGE_CODE]:This field is used to categorize when and how the [pay component|PAY COMPONENTS] is to be used during the pay calculation. For example, the Usages of Net Pay indicates that this will be the Pay Component used to store the net Pay amount that is calculated through [UPCALC] (Payroll Calculation). PC_Usage_Code from [P2K_PR_PC_USAGES] is a numeric value that you may manually enter or use the LOV (F9).
;[Usage Desc|DESCRIPTION]: This field gives a short description of the usage, specifically when and how the [pay component|PAY COMPONENTS] is to be used during the pay calculation. For example, the Usages of Net Pay indicates that this will be the [pay component|PAY COMPONENTS] used to store the net Pay amount that is calculated through [UPCALC] (Payroll Calculation). PC_Usage_Description from [P2K_PR_PC_USAGES] is an alphanumeric value that defaults from the usage.
;[Store Results|STORE_RESULTS]: If this toggle is checked, the value(s) of the [pay component|PAY COMPONENTS] amount will be stored in detail in the PC Amount table and accumulated in the to-date PC Amount table. This option would be used for all Pay Register amounts. If the toggle is not checked, the [pay component|PAY COMPONENTS] amount will not be stored or accumulated. This option is used for items such as rates used in calculations, or indicators used to trigger special processing. Store Results toggle must be checked in order for a Statistical [pay component|PAY COMPONENTS] (usage 14) to work correctly. If this toggle is not checked, information will not be stored in the statistic attached to the [pay component|PAY COMPONENTS]. Store_Results is an optional toggle field.
;[Assoc. PC|PC_CODE]: Associated [pay components|PAY COMPONENTS] are used to store the number of another [pay component|PAY COMPONENTS] that may be associated with this PC. For example, if the PC being defined were a Time PC then the Earnings PC would be its Assoc. PC. This field may need to be left blank until all of your [pay components|PAY COMPONENTS] are completed. PC_Code is an optional 4 digit numeric field that you may manually enter or use the LOV (F9).
At line 21 changed 3 lines
;[Element|ELEMENT_CODE]: If the pay component is to hold the result of a pay element it needs to be indicated here. If (PPE) appears in the usage, the PC should be associated to an element. This field can be filled in after the pay elements are completed. Element_Code from [P2K_PR_ELEMENTS] is 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Action|PC_ACTION]: The PC Action determines whether a transaction item entered under this pay component will be:
*Accumulated to the total value of the pay component
;[Element|ELEMENT_CODE]: If the [pay component|PAY COMPONENTS] is to hold the result of a pay element it needs to be indicated here. If (PPE) appears in the usage, the PC should be associated to an element. This field can be filled in after the pay elements are completed. Element_Code from [P2K_PR_ELEMENTS] is 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Action|PC_ACTION]: The PC Action determines whether a transaction item entered under this [pay component|PAY COMPONENTS] will be:
*Accumulated to the total value of the [pay component|PAY COMPONENTS]
At line 28 changed 5 lines
;[Entity|ENTITY_CODE]:A pay component may need to vary its rules or detail by entity. Entity_Code from [P2K_CM_ENTITIES] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Unit|UNIT_CODE]: A pay component may need to vary its rules or detail by unit within entity. Unit_Code from [P2K_CM_UNITS] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Group|GROUP_CODE]: A pay component may need to vary its rules or detail by group within unit within entity. Group_Code from [P2K_CM_GROUPS] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Basis|TIME_BASIS]:If the pay component is to store time or units, the basis needs to be indicated. (i.e. days, hours, units) in this field. While this field is optional, it is recommended that you complete it if you are going to do a retro pay. Time_Basis is an optional fixed lexicon ([X_TIME_BASIS]) that you may use to look up the value.
;[Pay Point|PAY_POINT_TYPE]: From the pay point set previously set up, this field will indicate when this pay component needs to be picked up for processing during the pay calculation. Pay_Point_Type is an optional fixed lexicon ([X_PAY_POINT_TYPE]) that you may use to choose an option.
;[Entity|ENTITY_CODE]:A [pay component|PAY COMPONENTS] may need to vary its rules or detail by entity. Entity_Code from [P2K_CM_ENTITIES] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Unit|UNIT_CODE]: A [pay component|PAY COMPONENTS] may need to vary its rules or detail by unit within entity. Unit_Code from [P2K_CM_UNITS] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Group|GROUP_CODE]: A [pay component|PAY COMPONENTS] may need to vary its rules or detail by group within unit within entity. Group_Code from [P2K_CM_GROUPS] is a 16-character alphanumeric optional field that you may manually enter or use the LOV (F9) to choose an option.
;[Basis|TIME_BASIS]:If the [pay component|PAY COMPONENTS] is to store time or units, the basis needs to be indicated. (i.e. days, hours, units) in this field. While this field is optional, it is recommended that you complete it if you are going to do a retro pay. Time_Basis is an optional fixed lexicon ([X_TIME_BASIS]) that you may use to look up the value.
;[Pay Point|PAY_POINT_TYPE]: From the pay point set previously set up, this field will indicate when this [pay component|PAY COMPONENTS] needs to be picked up for processing during the pay calculation. Pay_Point_Type is an optional fixed lexicon ([X_PAY_POINT_TYPE]) that you may use to choose an option.
At line 39 changed 3 lines
;[Enter Sundry|ENTER_SUNDRY_LINES]: If the Enter Sundry toggle is ON, the pay component may be entered on a sundry line (i.e.a recurring type of transaction). If the toggle is OFF, the pay component may not be entered on sundry lines. Enter_Sundry_Line is an optional toggle field.
;[Enter Pay Lines|ENTER_PAY_LINES]: If the Enter Pay Lines toggle is ON the pay component may be entered on a pay line (i.e. a one-time type of transaction). If the toggle is OFF, the pay component may not be entered on pay lines. Enter_Pay_Lines is an optional toggle field.
;[Generate Details|GENERATE_DETAILS]: If the Generate Details toggle is ON, this pay component has associated pay component detail records. If the toggle is OFF, there are no related PC details. Generate_Details is an option toggle field.
;[Enter Sundry|ENTER_SUNDRY_LINES]: If the Enter Sundry toggle is ON, the [pay component|PAY COMPONENTS] may be entered on a sundry line (i.e.a recurring type of transaction). If the toggle is OFF, the [pay component|PAY COMPONENTS] may not be entered on sundry lines. Enter_Sundry_Line is an optional toggle field.
;[Enter Pay Lines|ENTER_PAY_LINES]: If the Enter Pay Lines toggle is ON the [pay component|PAY COMPONENTS] may be entered on a pay line (i.e. a one-time type of transaction). If the toggle is OFF, the [pay component|PAY COMPONENTS] may not be entered on pay lines. Enter_Pay_Lines is an optional toggle field.
;[Generate Details|GENERATE_DETAILS]: If the Generate Details toggle is ON, this [pay component|PAY COMPONENTS] has associated [pay component|PAY COMPONENTS] detail records. If the toggle is OFF, there are no related PC details. Generate_Details is an option toggle field.
At line 43 changed one line
;[Default Position|DEFAULT_THE_POSITION]: If the foundation structure is set up with positions then this toggle must be ON to allow the position indicated on the employee’s assignment file to be defaulted for this pay component. If the foundation structure was set up with only jobs then this toggle does not need to be marked. This toggle only needs to be marked for pay components that need to be related to the rate of pay and/or distribution code. Default_The_Position is an option toggle field.
;[Default Position|DEFAULT_THE_POSITION]: If the foundation structure is set up with positions then this toggle must be ON to allow the position indicated on the employee’s assignment file to be defaulted for this [pay component|PAY COMPONENTS]. If the foundation structure was set up with only jobs then this toggle does not need to be marked. This toggle only needs to be marked for [pay components|PAY COMPONENTS] that need to be related to the rate of pay and/or distribution code. Default_The_Position is an option toggle field.
At line 45 changed one line
;[Default Job|DEFAULT_THE_JOB]: If the Foundation structure is set up with jobs then this toggle must be ON to allow the job indicated on the employees assignment file to be defaulted for this pay component. This toggle only needs to be marked for pay components that need to be related to the Rate of pay and/or Distribution code. Default_The_Job is an optional toggle field.
;[Default Job|DEFAULT_THE_JOB]: If the Foundation structure is set up with jobs then this toggle must be ON to allow the job indicated on the employees assignment file to be defaulted for this pay component. This toggle only needs to be marked for [pay components|PAY COMPONENTS] that need to be related to the Rate of pay and/or Distribution code. Default_The_Job is an optional toggle field.
At line 69 changed 2 lines
;[PC|PC_CODE]: This field indicates the pay component number if Time or Amount is being used PC_Code is a 4-digit numeric mandatory field that you must manually enter.
;[Abbreviation|PC_ABBREVIATION]: This field is automatically populated when the pay component number is entered. PC_Abbreviation is a 30-character alphanumeric mandatory field whose value will be filled once the pay component is selected.
;[PC|PC_CODE]: This field indicates the [pay component|PAY COMPONENTS] number if Time or Amount is being used PC_Code is a 4-digit numeric mandatory field that you must manually enter.
;[Abbreviation|PC_ABBREVIATION]: This field is automatically populated when the [pay component|PAY COMPONENTS] number is entered. PC_Abbreviation is a 30-character alphanumeric mandatory field whose value will be filled once the pay component is selected.
At line 73 changed one line
;:''The ‘Computed Values’ are calculated based on the 'Calculation Method'. Only one ‘Computed Value’ is allowed per pay component detail.
;:''The ‘Computed Values’ are calculated based on the 'Calculation Method'. Only one ‘Computed Value’ is allowed per [pay component|PAY COMPONENTS]detail.
At line 80 changed one line
;[Rate Source|PC_RATE_SOURCE]: This field indicates from where the wage rate used to determine the value of the pay component detail is derived. Rate_Source is a fixed lexicon ([X_PC_RATE_SOURCE]) that you may use to look up the value.
;[Rate Source|PC_RATE_SOURCE]: This field indicates from where the wage rate used to determine the value of the [pay component|PAY COMPONENTS] detail is derived. Rate_Source is a fixed lexicon ([X_PC_RATE_SOURCE]) that you may use to look up the value.
At line 111 changed one line
;[Collect Back|NEGATIVE_ARREARS]: This toggle is only ever 'ON' for one pay component - Advance Recovery. If this toggle is ON, the negative deduction is considered to be a recoverable advance, and an arrears transaction is generated for the purpose of recovering the advance on a subsequent pay. If the toggle is OFF, the negative deduction is treated as a refund or reimbursement to the employee, for which no recovery is required.
;[Collect Back|NEGATIVE_ARREARS]: This toggle is only ever 'ON' for one [pay component|PAY COMPONENTS] - Advance Recovery. If this toggle is ON, the negative deduction is considered to be a recoverable advance, and an arrears transaction is generated for the purpose of recovering the advance on a subsequent pay. If the toggle is OFF, the negative deduction is treated as a refund or reimbursement to the employee, for which no recovery is required.
At line 129 changed one line
;:Collect Back toggle is only set ON for pay component usage of 5 - ‘Advance Recovered’. If Collect Back is set ON for deductions this will result in an incorrect calculation during the next pay as arrears will be generated and the gross amount reduced.
;:Collect Back toggle is only set ON for [pay component usage|PAY COMPONENT USAGES] of 5 - ‘Advance Recovered’. If Collect Back is set ON for deductions this will result in an incorrect calculation during the next pay as arrears will be generated and the gross amount reduced.
At line 131 changed one line
*__'Only One Per Pay’__ recovers the deduction on a single transaction basis, for example, when an employee is three deductions in arrears for the same pay component, the pay calculation process attempts to recover only the oldest arrears transaction for that pay component. If there are insufficient earnings to collect the whole amount of the arrears transaction, the uncollected balance is generated as a new arrears transaction.
*__'Only One Per Pay’__ recovers the deduction on a single transaction basis, for example, when an employee is three deductions in arrears for the same [pay component|PAY COMPONENTS], the pay calculation process attempts to recover only the oldest arrears transaction for that [pay component|PAY COMPONENTS]. If there are insufficient earnings to collect the whole amount of the arrears transaction, the uncollected balance is generated as a new arrears transaction.
At line 138 changed one line
;:This rule recovers arrears on a multiple transaction basis, for example when an employee is three deductions in arrears for the same pay component, the pay calculation process attempts to recover each of these three deductions on the next pay.
;:This rule recovers arrears on a multiple transaction basis, for example when an employee is three deductions in arrears for the same [pay component|PAY COMPONENTS], the pay calculation process attempts to recover each of these three deductions on the next pay.
At line 145 changed one line
Premium type usages provide the ability to specify the list of the premium type(s), if any, which are applicable to a pay component.
Premium type usages provide the ability to specify the list of the premium type(s), if any, which are applicable to a [pay component|PAY COMPONENTS].
At line 147 changed one line
If a premium type usage is not defined, premiums of this type may not be used with the pay component.
If a premium type usage is not defined, premiums of this type may not be used with the [pay component|PAY COMPONENTS].
At line 158 changed one line
If you wish retro pay to be calculated on the earnings of this pay component, you must use the retro pay tab.
If you wish retro pay to be calculated on the earnings of this [pay component|PAY COMPONENTS], you must use the retro pay tab.
At line 161 changed 4 lines
;[Retro PC|PPC_ID_RETRO]:This field holds the pay component into which retro earnings will be stored. This may be the original earnings pay component. Retro_PC is an optional numeric field that you may either manually enter or use the LOV (F9).
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the retro pay component. PC_Abbreviation is defaulted based on the Retro PC used.
;[Retro Method|RETRO_METHOD]:This field indicates how the retro pay will be evaluated, either by pay component or by pay line. Retro_Method is a mandatory field you may fill with the fixed lexicon ([X_RETRO_METHOD]) provided.
;[Retro User Calc|MUC_ID_RETRO]:This field provides any User Calcs associated with this retro pay. User Calcs are ‘only’ used for retro on ‘non-earnings’ pay components such as Benefits or an increase in a deduction. This feature is rarely used and UPRETRO is more commonly used to compute an increase in ‘Earnings’ into the past. Retro_User_Calc is an optional field you may fill manually or choose from the LOV (F9).
;[Retro PC|PPC_ID_RETRO]:This field holds the [pay component|PAY COMPONENTS] into which retro earnings will be stored. This may be the original earnings [pay component|PAY COMPONENTS]. Retro_PC is an optional numeric field that you may either manually enter or use the LOV (F9).
;[Abbreviation|PC_ABBREVIATION]:This field provides a short description of the retro [pay component|PAY COMPONENTS]. PC_Abbreviation is defaulted based on the Retro PC used.
;[Retro Method|RETRO_METHOD]:This field indicates how the retro pay will be evaluated, either by [pay component|PAY COMPONENTS] or by pay line. Retro_Method is a mandatory field you may fill with the fixed lexicon ([X_RETRO_METHOD]) provided.
;[Retro User Calc|MUC_ID_RETRO]:This field provides any User Calcs associated with this retro pay. User Calcs are ‘only’ used for retro on ‘non-earnings’ [pay components|PAY COMPONENTS] such as Benefits or an increase in a deduction. This feature is rarely used and UPRETRO is more commonly used to compute an increase in ‘Earnings’ into the past. Retro_User_Calc is an optional field you may fill manually or choose from the LOV (F9).
This page (revision-78) was last changed on 02-Dec-2021 08:39 by Kevin HiggsTop