This page (revision-89) 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
89 26-Nov-2021 10:22 43 KB Karen Parrott to previous
88 26-Nov-2021 10:22 42 KB mmcfarland to previous | to last
87 26-Nov-2021 10:22 42 KB kparrott to previous | to last
86 26-Nov-2021 10:22 42 KB kparrott to previous | to last
85 26-Nov-2021 10:22 42 KB kparrott to previous | to last
84 26-Nov-2021 10:22 41 KB jescott to previous | to last
83 26-Nov-2021 10:22 41 KB jescott to previous | to last
82 26-Nov-2021 10:22 41 KB jescott to previous | to last
81 26-Nov-2021 10:22 41 KB jescott to previous | to last

Page References

Incoming links Outgoing links
IPPH
IPPH

Version management

Difference between version and

At line 16 changed one line
;[Period|PAY_PERIOD]: Pay periods are numbered by the year, followed by the period of the year. Pay_Periods from [P2K_PR_PAY_PERIODS] is a mandatory numeric field that is system updated from the information entered in the Pay Period field.
;[Period|PAY_PERIOD]: Pay periods are numbered by the year, followed by the period of the year.
At line 18 changed one line
;[Payroll|PAYROLL_CODE]:This field shows the payroll associated to the group indicated. Payroll_Code from [P2K_PR_PAYROLLS] a 16-character alphanumeric mandatory field that will default from the group indicated.
;[Payroll|PAYROLL_CODE]:This field shows the payroll associated to the group indicated.
At line 24 changed one line
;:Group_Code from [P2K_CM_GROUPS] a mandatory 16-character alphanumeric field that will be defaulted from the Group Source tab located in IDWR.
;:Group_Code will be defaulted from the Group Source tab located in IDWR.
At line 26 changed one line
;[Unit|UNIT_CODE]:This is the unit to which the group indicated belongs. Unit_Code from [P2K_CM_UNITS] a mandatory 16-character alphanumeric field that will default from the group indicated.
;[Unit|UNIT_CODE]:This is the unit to which the group indicated belongs.
At line 28 changed one line
;[Stage|PAY_HEADER_STAGE]:This field indicates the status of a pay header. Pay_Header_Stage is a mandatory fixed lexicon ([X_PAY_HEADER_STAGE]) that will be system updated.
;[Stage|PAY_HEADER_STAGE]:This field indicates the status of a pay header.
At line 36 changed one line
;[Seq #|DRV_PAY_RUN_SEQUENCE_NUMBER]: This field denotes the order that the pay header was processed within the pay run. This field will be displayed as ‘N/A’ if this pay headers is not attached to a pay run. Pay_Run_Number from [P2K_PR_PAY_RUNS] is an optional numeric field that will be system populated if this pay is calculated.
;[Seq #|DRV_PAY_RUN_SEQUENCE_NUMBER]: This field denotes the order that the pay header was processed within the pay run. This field will be displayed as ‘N/A’ if this pay headers is not attached to a pay run. Pay_Run_Number will be system populated if this pay is calculated.
At line 48 removed one line
;:Pay_Header_Source is a mandatory fixed lexicon ([X_PAY_HEADER_SOURCE]) that will be system updated.
At line 62 changed one line
;[Assignment|ASSIGNMENT_CODE]:This field will display the assignment for which this pay is generated. This assignment is also established by UPTR or UPTL when loading transactions in bulk. During that process, multiple pays per period may be created for multiple assignments. Assignment_Code from [P2K_HR_ASSIGNMENTS] is a mandatory field that will default to the employee’s prime assignment and can be manually entered or use the LOV (F9).
;[Assignment|ASSIGNMENT_CODE]:This field will display the assignment for which this pay is generated. This assignment is also established by UPTR or UPTL when loading transactions in bulk. During that process, multiple pays per period may be created for multiple assignments. Assignment_Code will default to the employee’s prime assignment and can be manually entered or use the LOV (F9).
At line 64 changed one line
;[Batch #|BATCH_NUMBER]: This field shows the batch to which this pay is attached. Batch_Number is a mandatory field you may select from the LOV (F9).
;[Batch #|BATCH_NUMBER]: This field shows the batch to which this pay is attached.
At line 66 changed one line
;[Pay Period|PAY_PERIOD]:This field identifies the pay period for which this pay is being generated. Pay periods are numbered by the year, followed by the period of the year. Pay_Periods from [P2K_PR_PAY_PERIODS] is a mandatory numeric field that will default from the batch entered but you may manually enter or use the LOV (F9).
;[Pay Period|PAY_PERIOD]:This field identifies the pay period for which this pay is being generated. Pay periods are numbered by the year, followed by the period of the year. Pay_Periods from [P2K_PR_PAY_PERIODS] will default from the batch entered but you may manually enter or use the LOV (F9).
At line 68 changed one line
;[Starting|PAY_PERIOD_START_DATE]:Period start is the date of the first day of the pay period. Pay_Period_Start_Date from [P2K_PR_PAY_PERIODS] is a mandatory date field that will default from the pay period entered.
;[Starting|PAY_PERIOD_START_DATE]:Period start is the date of the first day of the pay period. Pay_Period_Start_Date will default from the pay period entered.
At line 70 changed one line
;[Ending|PAY_PERIOD_END_DATE]:Period end is the date of the last day of the pay period. Pay_Period_End_Date from [P2K_PR_PAY_PERIODS] is a mandatory date field that will default from the pay period entered.
;[Ending|PAY_PERIOD_END_DATE]:Period end is the date of the last day of the pay period. Pay_Period_End_Date will default from the pay period entered.
At line 72 changed one line
;[Category|PAY_CATEGORY_CODE]:This field shows the user-assigned code that uniquely identifies the pay category. Pay_Category_Code from [P2K_PR_PAY_CATEGORIES] is a mandatory 16-character alphanumeric field that will default from the batch entered but you may manually enter or use the LOV (F9).
;[Category|PAY_CATEGORY_CODE]:This field shows the user-assigned code that uniquely identifies the pay category. Pay_Category_Code will default from the batch entered but you may manually enter or use the LOV (F9).
At line 74 changed one line
;[Pay Point Set|PAY_POINT_SET_CODE]:This field defines the set of tasks that will be used when calculating the pay. Pay_Point_Set_Code is a mandatory 16-character alphanumeric field that will default from the pay category but you may manually enter or use the LOV (F9).
;[Pay Point Set|PAY_POINT_SET_CODE]:This field defines the set of tasks that will be used when calculating the pay. Pay_Point_Set_Code will default from the pay category but you may manually enter or use the LOV (F9).
At line 76 changed one line
;[Trace Level|TRACE_LEVEL]:When performing a trial calculation, you may specify the level of message that the calculation report should display. This field is used for troubleshooting purposes. Trace_Level is an optional fixed lexicon ([X_TRACE_LEVEL]) that you may use to look up the value.
;[Trace Level|TRACE_LEVEL]:When performing a trial calculation, you may specify the level of message that the calculation report should display. This field is used for troubleshooting purposes.
At line 78 changed one line
;[Pay By|PAY_BY_CHECK]:This field indicates whether the payment will be overridden by check or prime deposit. If this field is left blank, the pay method rules as defined in [IPPM] will be used for this pay. Pay_By_Method is an optional fixed lexicon ([X_PAY_BY_METHOD]) that you may use to choose the method of payment.
;[Pay By|PAY_BY_CHECK]:This field indicates whether the payment will be overridden by check or prime deposit. If this field is left blank, the pay method rules as defined in [IPPM] will be used for this pay.
At line 80 changed one line
;[First Pay in Period|FIRST_PAY_IN_PERIOD]: This field is populated during the [UPAUDT] process and is used to qualify processing frequencies. If the First Pay In Period toggle is ON, this is a regular pay category header, and the first time the employee has been paid in this pay period. If the toggle is OFF, the employee has already been paid in the pay period. First_Pay_In_Period is an optional toggle field that is system updated during [UPAUDT].
;[First Pay in Period|FIRST_PAY_IN_PERIOD]: This field is populated during the [UPAUDT] process and is used to qualify processing frequencies. If the First Pay In Period toggle is ON, this is a regular pay category header, and the first time the employee has been paid in this pay period. If the toggle is OFF, the employee has already been paid in the pay period. First_Pay_In_Period is system updated during [UPAUDT].
At line 82 changed one line
;[1st Pay in Month|FIRST_PAY_IN_MONTH]: This field is populated during the [UPAUDT] process and is used to qualify processing frequencies. If the First Pay In Month toggle is ON, the pay header is for the first time the employee has been paid in the calendar month for a regular pay. If the toggle is OFF, there has already been a regular pay created or paid for this (or a prior) period in the month. First_Pay_In_Month is an optional toggle field that is system updated.
;[1st Pay in Month|FIRST_PAY_IN_MONTH]: This field is populated during the [UPAUDT] process and is used to qualify processing frequencies. If the First Pay In Month toggle is ON, the pay header is for the first time the employee has been paid in the calendar month for a regular pay. If the toggle is OFF, there has already been a regular pay created or paid for this (or a prior) period in the month. First_Pay_In_Month is system updated.
At line 84 changed one line
;[Audited|AUDITED]:This field is populated during the [UPAUDT] process. If the Audited toggle is ON, the pay header has passed all the validation checks of the audit process ([UPAUDT]) and is ready to be processed through pay calculation. If the toggle is OFF, either the pay header has not yet been audited, or it has failed to pass the transaction audit. The Audited toggle on the pay header is not set unless all of the individual pay lines associated with that header have also passed the transaction audit. Audited is an optional toggle field that is system updated.
;[Audited|AUDITED]:This field is populated during the [UPAUDT] process. If the Audited toggle is ON, the pay header has passed all the validation checks of the audit process ([UPAUDT]) and is ready to be processed through pay calculation. If the toggle is OFF, either the pay header has not yet been audited, or it has failed to pass the transaction audit. The Audited toggle on the pay header is not set unless all of the individual pay lines associated with that header have also passed the transaction audit. Audited is system updated.
At line 86 changed one line
;[Sundry Attached|SUNDRY_ATTACHED]: This field is populated during the [UPAUDT] process. If the Prepared toggle is ON, the time sheet has been successfully processed by [UPAUDT]. To prepare this time sheet to be paid, [UPAUDT] has pulled together all related information (e.g. user calculations, sundry items, benefits, etc.) for this pay header from the Pay Point set (as defined in [IPPP]). If you are changing any ‘Pay Point Set’ information on [IPPP] form, you will need to run [UPUNPREP] and then run [UPAUDT] again to prepare. Sundry_Attached is an optional toggle field that is system updated.
;[Sundry Attached|SUNDRY_ATTACHED]: This field is populated during the [UPAUDT] process. If the Prepared toggle is ON, the time sheet has been successfully processed by [UPAUDT]. To prepare this time sheet to be paid, [UPAUDT] has pulled together all related information (e.g. user calculations, sundry items, benefits, etc.) for this pay header from the Pay Point set (as defined in [IPPP]). If you are changing any ‘Pay Point Set’ information on [IPPP] form, you will need to run [UPUNPREP] and then run [UPAUDT] again to prepare. Sundry_Attached is system updated.
At line 90 changed one line
;:If the toggle is OFF, all or some of the pay lines have not yet been journalized. Journalized is an optional toggle field that is system updated.
;:If the toggle is OFF, all or some of the pay lines have not yet been journalized. Journalized is system updated.
At line 92 changed one line
;[Journalized Fund|JOURNALIZED_FUND]: This field is populated during the UPGL process. If the Journalized Fund toggle is ON, that segment of the GL Distribution can be used as a 'Fund'. Journalized_Fund is an optional toggle field that is system updated.
;[Journalized Fund|JOURNALIZED_FUND]: This field is populated during the UPGL process. If the Journalized Fund toggle is ON, that segment of the GL Distribution can be used as a 'Fund'. Journalized_Fund is system updated.
At line 94 changed one line
;[Time Sheet Returned|TIMESHEET_RETURNED]:This field indicates to the system that the employee has returned the time sheet. If the Time sheet Required toggle on [IDWR] - Status Rules tab is ON, then a physical time sheet for the employee must be received at data entry time. You must physically turn the Time Sheet Returned toggle on, otherwise this time sheet will not pass the [UPAUDT] process. Timesheet_Returned is an optional toggle field.
;[Time Sheet Returned|TIMESHEET_RETURNED]:This field indicates to the system that the employee has returned the time sheet. If the Time sheet Required toggle on [IDWR] - Status Rules tab is ON, then a physical time sheet for the employee must be received at data entry time. You must physically turn the Time Sheet Returned toggle on, otherwise this time sheet will not pass the [UPAUDT] process.
At line 105 changed one line
;[Check Amount|CHECK_AMOUNT]:This field shows the amount of the check associated with the pay, only if it is a ‘[hand check|HAND CHECK]’. Check_Amount is an optional 18 digit numeric field that is either manually or system updated.
;[Check Amount|CHECK_AMOUNT]:This field shows the amount of the check associated with the pay, only if it is a ‘[hand check|HAND CHECK]’.
At line 107 changed one line
;[Pay Issue Date|PAY_ISSUE_DATE]: The Pay Issue Date is the date that payment is issued for the time sheet. Pay_Issue_Date is a mandatory date field that will default from the pay period chosen, but may be overridden.
;[Pay Issue Date|PAY_ISSUE_DATE]: The Pay Issue Date is the date that payment is issued for the time sheet. Pay_Issue_Date will default from the pay period chosen, but may be overridden.
At line 109 changed one line
;[Check #|CHECK_NUMBER]:The check number is assigned by you from the manual check range for the organization’s bank from [IPBA]. This field is only used for manually issued checks. Check_Number is an optional numeric field that is system updated.
;[Check #|CHECK_NUMBER]:The check number is assigned by you from the manual check range for the organization’s bank from [IPBA]. This field is only used for manually issued checks. Check_Number is system updated.
At line 111 changed one line
;[Hand Check|HAND_CHECK]:If the Hand Check toggle is ON, the pay header is for a pay which includes a [hand written check|HAND CHECK] that needs to be recorded in the system. If the toggle is OFF, this is a normal computer generated payment. Hand_Check is an optional toggle field.
;[Hand Check|HAND_CHECK]:If the Hand Check toggle is ON, the pay header is for a pay which includes a [hand written check|HAND CHECK] that needs to be recorded in the system. If the toggle is OFF, this is a normal computer generated payment.
At line 121 changed one line
;[Work State/Prov|DSP_ID_WORK]:This field shows the State or Province code standard abbreviation where the employee works. State_Province from [P2K_CM_STATE_PROVINCES] is a 16-character alphanumeric mandatory field that will default from the employee’s Assignment form but you may manually enter or use the LOV (F9).
;[Work State/Prov|DSP_ID_WORK]:This field shows the State or Province code standard abbreviation where the employee works. State_Province from [P2K_CM_STATE_PROVINCES] will default from the employee’s Assignment form but you may manually enter or use the LOV (F9).
At line 123 changed one line
;[Work Jurisdiction|DTX_ID_WORK]:This field holds the Geo code of the employee’s work tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] is a 16-character alphanumeric optional field that will default from the employee’s Assignment form however, you may manually enter or use the LOV (F9).
;[Work Jurisdiction|DTX_ID_WORK]:This field holds the Geo code of the employee’s work tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] will default from the employee’s Assignment form however, you may manually enter or use the LOV (F9).
At line 125 changed one line
;[Home State/Prov|DSP_ID_HOME]: This field holds the state or province where the employee resides. State_Province from [P2K_CM_STATE_PROVINCES] is a mandatory 16-character alphanumeric field that will default from the employee’s Personal form but you may manually enter or use the LOV (F9).
;[Home State/Prov|DSP_ID_HOME]: This field holds the state or province where the employee resides. State_Province will default from the employee’s Personal form but you may manually enter or use the LOV (F9).
At line 127 changed one line
;[Home Jurisdiction|DTX_ID_HOME]:This field holds the Geo code of the employee’s residence tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] is a 16-character alphanumeric optional field that will default from the employee’s Personal form but you may manually enter or use the LOV (F9).
;[Home Jurisdiction|DTX_ID_HOME]:This field holds the Geo code of the employee’s residence tax jurisdiction. Jurisdiction from [P2K_CM_TAX_JURISDICTIONS] will default from the employee’s Personal form but you may manually enter or use the LOV (F9).
At line 129 changed one line
;[School District|SCHOOL_DISTRICT_CODE]: For U.S. installations only: This field shows the school district to which the employee pays taxes. School_District is a 16-character alphanumeric optional field that will default from the employee’s personal form but you may manually enter or use the LOV (F9).
;[School District|SCHOOL_DISTRICT_CODE]: For U.S. installations only: This field shows the school district to which the employee pays taxes. School_District will default from the employee’s personal form but you may manually enter or use the LOV (F9).
At line 131 changed one line
;[Final Pay Method|FINAL_PAY_METHOD]:The final pay method indicates whether or not a pay is considered to be an employee's final pay. The final pay method is set to 'final pay' automatically when this pay header’s employment has a termination date within the pay period and a termination reason defined as final pay on [IDTR]. When 'final pay' is set, certain events or processes may be triggered to happen automatically, such as the paying out of leave policy balances from attendance. Final_Pay_Method is an optional fixed lexicon ([X_FINAL_PAY_METHOD]) that will default based on the employee’s termination date falling within the pay period specified or you may use to look up the value.
;[Final Pay Method|FINAL_PAY_METHOD]:The final pay method indicates whether or not a pay is considered to be an employee's final pay. The final pay method is set to 'final pay' automatically when this pay header’s employment has a termination date within the pay period and a termination reason defined as final pay on [IDTR]. When 'final pay' is set, certain events or processes may be triggered to happen automatically, such as the paying out of leave policy balances from attendance. Final_Pay_Method will default based on the employee’s termination date falling within the pay period specified or you may use to look up the value.
At line 133 changed one line
;[Tax Weeks|TAX_WEEKS]:This field shows the number of tax weeks associated with this pay for this pay frequency. The Tax Weeks field enables you to override the default number of pay weeks associated with a pay period. Changing the tax weeks changes the calculation of the normal period taxation that will be applied to that employee. For example, this is used when an employee who is on a biweekly payroll cycle is only receiving pay for working one of the two weeks in the biweekly pay period. Tax_Weeks is an optional numeric field that will default from the pay weeks indicated on the pay calendar of the pay period specified, but may be overridden.
;[Tax Weeks|TAX_WEEKS]:This field shows the number of tax weeks associated with this pay for this pay frequency. The Tax Weeks field enables you to override the default number of pay weeks associated with a pay period. Changing the tax weeks changes the calculation of the normal period taxation that will be applied to that employee. For example, this is used when an employee who is on a biweekly payroll cycle is only receiving pay for working one of the two weeks in the biweekly pay period. Tax_Weeks will default from the pay weeks indicated on the pay calendar of the pay period specified, but may be overridden.
At line 135 changed one line
;[Reversal #|PAY_NUMBER]:If the category indicated is a [reversal|PAY REVERSAL], then the pay that is to be reversed must be indicated in this field. The original pay # to be reversed must be disbursed (through [UPDISB]) before it can be reversed. Pay_Number is a 5-digit mandatory field (if the category is reversal) you must manually enter or use the LOV (F9).
;[Reversal #|PAY_NUMBER]:If the category indicated is a [reversal|PAY REVERSAL], then the pay that is to be reversed must be indicated in this field. The original pay # to be reversed must be disbursed (through [UPDISB]) before it can be reversed.
This page (revision-89) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop