This page (revision-32) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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
32 26-Nov-2021 10:22 12 KB Karen Parrott to previous
31 26-Nov-2021 10:22 12 KB mmcfarland to previous | to last
30 26-Nov-2021 10:22 12 KB kparrott to previous | to last
29 26-Nov-2021 10:22 12 KB jmyers to previous | to last
28 26-Nov-2021 10:22 12 KB JMyers to previous | to last
27 26-Nov-2021 10:22 12 KB JMyers to previous | to last
26 26-Nov-2021 10:22 13 KB JMyers to previous | to last
25 26-Nov-2021 10:22 16 KB JMyers to previous | to last
24 26-Nov-2021 10:22 16 KB JMyers to previous | to last
23 26-Nov-2021 10:22 16 KB RForbes to previous | to last
22 26-Nov-2021 10:22 16 KB JAiken to previous | to last
21 26-Nov-2021 10:22 15 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
IPSN
IPSN

Version management

Difference between version and

At line 7 changed one line
The processing frequency for the sundry transaction may be defined through the [IPPF] form. If the sundry transaction has a frequency of one time only, once it becomes a pay line in a pay header ([IPPH]), it is removed as a sundry (IPSN). The history is then kept with the pay header.
The processing frequency for the sundry transaction may be defined through the [IPPF] form. If the sundry transaction has a frequency of one time only, once it becomes a pay line in a pay header ([IPPH]), may be removed depending on the IPPF toggle [KEEP_HISTORY]. If this toggle is turned ON, then the IPSN record will not be removed, but the status will be changed to 'Completed-1 time'.
At line 17 added 2 lines
%%information Unlike the [IPPH] screen, IPSN will only generate the details when a sundry line is first entered. In most cases, and in particular for Declining Balance items, the generated details will need amounts to to be entered. When the record is saved, the details will not be regenerated.%%
At line 20 changed 3 lines
;[Assignment|ASSIGNMENT_CODE]:The assignment type from the employee’s assignment screen will allow you to enter the sundry that is applicable to this assignment code only. Assignment_Code from [P2K_HR_ASSIGNMENTS] is available as an LOV (F9) that you may use to look up the value for this employee.
;[Freq|FREQUENCY_CODE]:Processing frequencies indicates how often this payroll item (deduction, benefit, etc.) is processed from [P2K_PR_FREQUENCIES]. Frequency_Code is a mandatory 16-character alphanumeric field that you must manually enter or use the LOV (F9).
;[Cal|CALENDAR_CODE]:This field is used to associate ate Sundry Calendar from [IDCL] to a Sundry Line. This field is used:
;[Assignment|ASSIGNMENT_CODE]:The assignment type from the employee’s assignment screen will allow you to enter the sundry that is applicable to this assignment code only.
* IPSN 'Assignment Matching' is controlled by IPPC. If 'Sundry Assgn Matching' is OFF, then the Assignment Code in IPSN is ignored. If it is ON, then the Assignment Code on the Pay Header must match the Assignment Code in IPSN to qualify.
;[Freq|FREQUENCY_CODE]:Processing frequencies indicates how often this payroll item (deduction, benefit, etc.) is processed from [P2K_PR_FREQUENCIES].
;[Calendar|CALENDAR_CODE]:This field is used to associate a Sundry Calendar from [IDCL] to a Sundry Line. This field is used:
At line 26 changed 20 lines
;[Start Date|START_DATE]:This field shows the date that the sundry transaction commences. Start_Date is a mandatory date field that will default as the beginning of time (01-Jan-0001), but may be overridden.
;[End Date|END_DATE]:This field shows the date that the sundry transaction ends. End_Date is a mandatory date field that will default with the end of time (31-Dec-3999), but may be overridden.
;[PC|PC_CODE]:A [pay component|PAY COMPONENTS] code is a unique number code from 1 to 9,999 assigned to uniquely identify the [pay component|PAY COMPONENTS]. Only [pay components|PAY COMPONENTS] with the toggle ‘Enter Sundry’ turned on from the [IPPC] form will be accessible. PC_Code from [P2K_PR_PAY_COMPONENTS] is a 4 digit numeric mandatory field that you must manually enter or use the LOV (F9).
;[Abbreviation|PC_ABBREVIATION]:This field holds a short description of the [pay component|PAY COMPONENTS]. This abbreviation will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation is a 16-character alphanumeric mandatory field that will default from the pay component chosen
;[Value|TIME_ENTERED]:This field shows the amount or value of the sundry item. Time_Entered is an optional numeric field that needs to be completed if the [pay component|PAY COMPONENTS] chosen is for time.
;[Basis|TIME_BASIS]:The basis is the unit of measure that the associated value is being stored or displayed in:
*YR - Yearly/Annual
*MO - Monthly
*WK - Weekly
*DY - Daily
*HR - Hourly
*UN - Unit
*CT - Contract - Normally used for Premiums not Sundry Lines
*KM - Kilometers - Normally used for Premiums not Sundry Lines
*PC - Pieces - Normally used for Premiums not Sundry Lines
*PP - Pay Period - Normally used for Premiums not Sundry Lines
*DV - Days Variable
*HV - Hours Variable
*$ - Amount
;:Time_Basis is an optional fixed lexicon ([X_TIME_BASIS]) that will default from the [pay component|PAY COMPONENTS] set up but may be overridden.
;[Start Date|START_DATE]:This field shows the date that the sundry transaction commences.
;[End Date|END_DATE]:This field shows the date that the sundry transaction ends.
;[PC|PC_CODE]:A pay component code is a unique number code from 1 to 9,999 assigned to uniquely identify the pay component. Only pay components with the toggle ‘Enter Sundry’ turned on from the [IPPC] form will be accessible.
;[Abbreviation|PC_ABBREVIATION]:This field holds a short description of the pay component. This abbreviation will be printed on check and deposit statements, lists and pay registers.
;[Value|TIME_ENTERED]:This field shows the amount or value of the sundry item. Time_Entered needs to be completed if the pay component chosen is for time.
;[Basis|TIME_BASIS]:The basis is the unit of measure that the associated value is being stored or displayed in.
;:Time_Basis will default from the pay component set up but may be overridden.
At line 48 changed 4 lines
;[Show All|ACT_SHOW_ALL]:If this toggle is ON, all sundries will be displayed. If this toggle is OFF, only active sundries will be displayed. Active sundries are defined by the following conditions:
*Start Date falls on or before the As Of Date
*End Date falls on or after the As Of Date
*If the Sundry has a Declining Balance it has a value greater than zero (0).
;[History|ACT_VIEW_SUNDRY_HISTORY]:This button will open a view only dialog displaying the pay history.
;[Filter By|]:
;[Show All|ACT_SHOW_ALL]:If this toggle is ON, all sundries will be displayed. If this toggle is OFF, only active sundries will be displayed.
At line 55 changed one line
By applying the PC rules of the [pay component|PAY COMPONENTS], you will derive all of the required values associated with the sundry line. These results will be displayed in the Sundry Line details.
By applying the PC rules of the pay component, you will derive all of the required values associated with the sundry line. These results will be displayed in the Sundry Line details.
At line 57 changed 27 lines
;[PC|PC_CODE]:This field shows the [pay component|PAY COMPONENTS] code(s) that default in from the Sundry transaction [pay component|PAY COMPONENTS] code entered at the top of the screen. For example, if a deduction component is entered on the Sundry transaction then the deduction and declining balance [pay components|PAY COMPONENTS] may be generated on the pay detail line. PC_Code from [P2K_PR_PAY_COMPONENTS] is a 4-digit numeric mandatory field that will default from the PC entered on the sundry line but you make a selection from the LOV (F9) provided.
;[Abbreviation|PC_ABBREVIATION]:This field shows a short alpha description of the [pay component|PAY COMPONENTS]. This abbreviation will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation is a 16-character alphanumeric mandatory field that will default from the [pay component|PAY COMPONENTS] chosen. The information in this tab is generated when the Sundry Line is saved.
;[Type|PC_DETAIL_TYPE]:This field indicates how the [pay component|PAY COMPONENTS] amount is used. For example, the [pay component|PAY COMPONENTS] may be used to store time, an amount, a limit, or a declining balance. PC_Detail_Type is a mandatory fixed lexicon ([X_PC_DETAIL_TYPE]) that will default from the pay component but may be overridden.
;[Amount|AMOUNT]:This field shows the amount calculated as a result of applying the PC Calc Method. Amount is an optional numeric field that is system maintained.
;[Override|AMOUNT_OVERRIDE]:You may manually enter the amount to be used in the pay calculation into this field. Amount_Override is an optional numeric field that will be populated by the system based on the [pay component|PAY COMPONENTS] rules but may be overridden.
;[Description|DESCRIPTION]:This field provides a free form description of the sundry line. Description is a 50 character alphanumeric optional field that will be system populated but you may manually enter.
;[Wage Rate|WAGE_RATE]:This field shows the wage rate derived from the pay component rule. Wage_Rate is an optional 18 digit numeric field that is calculated from the wage rate source then re-derived based on the basis indicated.
;[Wage Override|WAGE_RATE_OVERRIDE]:You may override the wage rate in this field. Wage_Rate_Override is an 18 digit optional numeric field that you many manually enter.
;[Basis|RATE_BASIS]: The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis is a fixed lexicon ([X_RATE_BASIS]) that will default a value from the pay component.
;[Rate Override|RATE_BASIS_OVERRIDE]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate Basis may be overridden in the entry screen, or through the transaction loader process. Rate_Basis_Override is an optional fixed lexicon ([X_RATE_BASIS]) that will be derived from the basis indicated on the sundry line but may be overridden.
;[Distribution DR|DISTRIBUTION_DR_MASK]:The distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the debit GL code of the [pay component|PAY COMPONENTS]. Distribution_DR_Mask is an optional 50 alphanumeric field that you manually enter or use the Distribution Editor to enter the value.
;[Distribution CR|DISTRIBUTION_CR_MASK]:The distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the credit GL code of the [pay component|PAY COMPONENTS]. Distribution_CR_Mask is an optional 50 alphanumeric field that you manually enter or use the Distribution Editor to enter the value.
;[User Variable|USER_VARIABLE_CODE]: This field shows the user variable that may be used according to the [pay component|PAY COMPONENTS] details set up. User_Variable_Code is a 16-character alphanumeric optional field that will default a value from the pay component or be manually entered.
;[Override|USER_VARIABLE_OVERRIDE]:You may manually enter the user variable amount. For example, the user variable field may indicate a rate of 1.5 but for this particular transaction you may wish to enter 1.55. User_Variable_Override is an optional numeric field that you may manually enter.
;[Element|ELEMENT_CODE]:This field shows the element that is to be used according to the [pay component|PAY COMPONENTS] details set up. Element_Code is a 16-character alphanumeric optional field that will default from a value from the [pay component|PAY COMPONENTS] or be manually entered.
;[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], replace a prior transaction item, trigger a user calculation, or suppress a user calculation. PC_Action is a mandatory fixed lexicon ([X_PC_ACTION]) that will default from the pay component and may be overridden.
;[Rate Source|PC_RATE_SOURCE]:Indicates from where the wage rate is derived.
*Primary Assignment
*Matching Assignment
*Position or Job
*Job
*Prime + Premiums
*Assign + Premiums
*Job/Posn + Premiums
*Job + Premiums
;:PC_Rate_Source is an optional fixed lexicon ([X_PC_RATE_SOURCE]) that will default from the [pay component|PAY COMPONENTS].
;[Calc Meth|PC_CALC_METHOD]:Indicates the method by which an amount is calculated. PC_Calc_Method is an optional fixed lexicon ([X_PC_CALC_METHOD]) that will default from the [pay component|PAY COMPONENTS] but may be overridden.
;[PC|PC_CODE]:This field shows the pay component code(s) that default in from the Sundry transaction pay component code entered at the top of the screen. For example, if a deduction component is entered on the Sundry transaction then the deduction and declining balance pay component may be generated on the pay detail line. PC_Code will default from the PC entered on the sundry line but you make a selection from the LOV (F9) provided.
;[Abbreviation|PC_ABBREVIATION]:This field shows a short alpha description of the pay component. This abbreviation will be printed on check and deposit statements, lists and pay registers. PC_Abbreviation will default from the pay component chosen. The information in this tab is generated when the Sundry Line is saved.
;[Type|PC_DETAIL_TYPE]:This field indicates how the pay component amount is used. For example, the pay component may be used to store time, an amount, a limit, or a declining balance. PC_Detail_Type will default from the pay component but may be overridden.
;[Amount|AMOUNT]:This field shows the amount calculated as a result of applying the PC Calc Method.
;[Override|AMOUNT_OVERRIDE]:You may manually enter the amount to be used in the pay calculation into this field. Amount_Override will be populated by the system based on the pay component rules but may be overridden.
;[Description|DESCRIPTION]:This field provides a free form description of the sundry line. Description that will be system populated but you may manually enter.
;[Wage Rate|WAGE_RATE]:This field shows the wage rate derived from the pay component rule. Wage_Rate is calculated from the wage rate source then re-derived based on the basis indicated.
;[Wage Override|WAGE_RATE_OVERRIDE]:You may override the wage rate in this field.
;[Basis|RATE_BASIS]: The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis will default a value from the pay component.
;[Rate Override|RATE_BASIS_OVERRIDE]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate Basis may be overridden in the entry screen, or through the transaction loader process. Rate_Basis_Override that will be derived from the basis indicated on the sundry line but may be overridden.
;[Distribution DR|DISTRIBUTION_DR_MASK]:The distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the debit GL code of the pay component.
;[Distribution CR|DISTRIBUTION_CR_MASK]:The distribution mask contains the distribution derived from the assignment, position, or job, overlaid by the distribution mask based on the credit GL code of the pay component.
;[User Variable|USER_VARIABLE_CODE]: This field shows the user variable that may be used according to the pay component details set up.
;[Override|USER_VARIABLE_OVERRIDE]:You may manually enter the user variable amount. For example, the user variable field may indicate a rate of 1.5 but for this particular transaction you may wish to enter 1.55.
;[Element|ELEMENT_CODE]:This field shows the element that is to be used according to the pay component details set up. Element_Code will default from a value from the pay component or be manually entered.
;[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, replace a prior transaction item, trigger a user calculation, or suppress a user calculation. PC_Action will default from the pay component and may be overridden.
;[Rate Source|PC_RATE_SOURCE]:Indicates from where the wage rate is derived. ;:PC_Rate_Source will default from the pay component.
;[Calc Meth|PC_CALC_METHOD]:Indicates the method by which an amount is calculated. PC_Calc_Method will default from the pay component but may be overridden.
At line 90 changed 5 lines
;[User Calc|USER_CALC_CODE]:This field shows the UserCalc that may be attached to the [pay component|PAY COMPONENTS] chosen.
;[Pay Point Type|PAY_POINT_TYPE]:This field indicates when this [pay component|PAY COMPONENTS] needs to be picked up for processing during the pay calculation. Pay_Point_Type is a mandatory fixed lexicon ([X_PAY_POINT_TYPE]) that will default from the [pay component|PAY COMPONENTS]chosen for this sundry.
;[Seq.|PAY_POINT_SEQUENCE]:This field displays the unique sequence number assigned to each item processed in a pay point. Items processed in a pay point may include multiple pay lines, UserCalcs, Benefit Plans and Leave Policies. Pay_Point_Sequence is an optional numeric field that will default from the pay component chosen for this pay line.
;[Reference|REFERENCE_INFO PSL]: This field allows you to enter a note or reference for the sundry. This reference information may be either anecdotal or more structured (e.g. Union Code or Court Number). If the Reference field on [IPPC] is defined as 'Enter Vendor Code', you will select a code from an LOV. If there is no link, you may use this field to provide a description directly on the [IPSN] screen.You will be able to enter up to 200 characters as reference on the pay lines. This entry will not be checked against values within any lexicon. Reference_Info is a 50-character alphanumeric optional field.
;[Sundry Type|SUNDRY_LINE_TYPE]:Indicates whether the sundry line is for a regular amount, an arrears amount, or a retro pay amount Sundry_Line_Type is a mandatory fixed lexicon ([X_SUNDRY_LINE_TYPE]) that is system maintained.
;[User Calc|USER_CALC_CODE]:This field shows the UserCalc that may be attached to the pay component chosen.
;[Pay Point Type|PAY_POINT_TYPE]:This field indicates when this pay component needs to be picked up for processing during the pay calculation. Pay_Point_Type is a mandatory fixed lexicon ([X_PAY_POINT_TYPE]) that will default from the pay componentchosen for this sundry.
;[Seq.|PAY_POINT_SEQUENCE]:This field displays the unique sequence number assigned to each item processed in a pay point. Items processed in a pay point may include multiple pay lines, UserCalcs, Benefit Plans and Leave Policies. Pay_Point_Sequence will default from the pay component chosen for this pay line.
;[Reference|REFERENCE_INFO PSL]: This field allows you to enter a note or reference for the sundry. This reference information may be either anecdotal or more structured (e.g. Union Code or Court Number). If the Reference field on [IPPC] is defined as 'Enter Vendor Code', you will select a code from an LOV. If there is no link, you may use this field to provide a description directly on the [IPSN] screen.You will be able to enter up to 200 characters as reference on the pay lines. This entry will not be checked against values within any lexicon.
;[Sundry Type|SUNDRY_LINE_TYPE]:Indicates whether the sundry line is for a regular amount, an arrears amount, or a retro pay amount.
At line 97 changed 5 lines
;[Work Order|WORK_ORDER]:Work Order is used to define work orders attached to a specific sundry. The Work Order Validation is defined on the ‘Define G/L Company’ ([IDGC]) form. The work order on each pay line can be unedited (no validation) or validated from an external system that has been pre-programmed. Work_Order is a 50-character optional alphanumeric field.
;[Cost Center|COST_CENTER_CODE]:Cost Center is used to define a short cut for the cost center information attached to a specific sundry. Cost_Center from [P2K_CM_COST_CENTERS] is a 16-character alphanumeric optional field that you manually enter or use the LOV (F9).
;[Pay Point Task|PAY_POINT_TASK]:A pay point task identifies the kind of process within the pay point. Pay_Point_Task is a mandatory fixed lexicon ([X_PAY_POINT_TASK]) that you may use to look up the value.
;[WC Class|WCB_CLASS]:This field shows the Workers’ Compensation derived from the assignment indicated for this sundry line. WCB_Class is an optional user-defined lexicon ([X_WCB_CLASS]) that will default from the assignment type indicated.
;[Audit Text|AUDIT_TEXT]:This field will display the exception text generated for this line. Audit_Text is an optional alphanumeric field that will be updated by the system.
;[Work Order|WORK_ORDER]:Work Order is used to define work orders attached to a specific sundry. The Work Order Validation is defined on the ‘Define G/L Company’ ([IDGC]) form. The work order on each pay line can be unedited (no validation) or validated from an external system that has been pre-programmed.
;[Cost Center|COST_CENTER_CODE]:Cost Center is used to define a short cut for the cost center information attached to a specific sundry.
;[Pay Point Task|PAY_POINT_TASK]:A pay point task identifies the kind of process within the pay point.
;[WC Class|WCB_CLASS]:This field shows the Workers’ Compensation derived from the assignment indicated for this sundry line. WCB_Class will default from the assignment type indicated.
;[Audit Text|AUDIT_TEXT]:This field will display the exception text generated for this line. Audit_Text will be updated by the system.
At line 105 changed 5 lines
;[Premium|PREMIUM_CODE]:This field will identify the premium associated with the sundry. Premium_Code is a 16-character alphanumeric mandatory field that you may select from the LOV(F9).
;[Rate|PREMIUM_RATE]:This field shows the premium rate that is used in the premium calculation. Premium_Rate is an 18 digit numeric field.
;[Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis is an optional fixed lexicon ([X_RATE_BASIS]) that you may use to look up the value.
;[Override Rate|PREMIUM_RATE]:Premium override rate you have entered that is used in the premium calculation. Premium_Rate is an 18 digit numeric field.
;[Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis is an optional fixed lexicon ([X_RATE_BASIS]) that you may use to look up the value.
;[Premium|PREMIUM_CODE]:This field will identify the premium associated with the sundry.
;[Rate|PREMIUM_RATE]:This field shows the premium rate that is used in the premium calculation.
;[Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual.
;[Override Rate|PREMIUM_RATE]:Premium override rate you have entered that is used in the premium calculation.
;[Basis|RATE_BASIS]:The rate basis is the unit of measure that the associated rate is being stored or displayed in, for example, hourly, weekly, biweekly, semi-monthly, monthly, or annual.
At line 113 changed one line
This tab provides historical information regarding sundry transactions that have been processed through [IPPH].
This tab provides historical information regarding sundry transactions that have been processed through [IPPH]. \\ \\If the sundry transaction has a frequency of one time only, once it becomes a pay line in a pay header ([IPPH]), it is removed as a sundry (IPSN). The history is then kept with the pay header.
At line 116 removed one line
[{If var='loginstatus' contains 'authenticated'
At line 119 changed 4 lines
![Discussion|Edit:Internal.IPSN]
[{InsertPage page='Internal.IPSN' default='Click to create a new discussion page'}]
}]
![Notes|Edit:Internal.IPSN]
[{InsertPage page='Internal.IPSN' default='Click to create a new notes page'}]
This page (revision-32) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop