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

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

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
12 26-Nov-2021 10:22 5 KB kparrott to previous
11 26-Nov-2021 10:22 5 KB rforbes to previous | to last
10 26-Nov-2021 10:22 5 KB JMyers to previous | to last
9 26-Nov-2021 10:22 5 KB JMyers to previous | to last
8 26-Nov-2021 10:22 35 KB JMyers to previous | to last
7 26-Nov-2021 10:22 34 KB JMyers to previous | to last
6 26-Nov-2021 10:22 34 KB JMyers to previous | to last
5 26-Nov-2021 10:22 33 KB JMyers to previous | to last
4 26-Nov-2021 10:22 32 KB JMyers to previous | to last
3 26-Nov-2021 10:22 1 KB JMyers to previous | to last
2 26-Nov-2021 10:22 5 KB JMyers to previous | to last
1 26-Nov-2021 10:22 5 KB JMyers to last

Page References

Incoming links Outgoing links
IVPPH
IVPPH

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: [IVPPH]
(INF_CV_PAYHEADERS)
!!!PAY HEADERS INTERFACE FILE
At line 4 changed one line
The INF_CV_PAYHEADERS table is used to import historical employee payroll information at a summary level into the software data structures.
The Pay Headers Interface File screen is used to import historical employee payroll information at a summary level into the software data structures.
At line 6 changed 2 lines
!!Table Columns
Pay Headers Interface File data is maintained on the [INF_CV_PAYHEADERS] table.
\\
----
!!Tab 1
;[ID|ID]:This field uniquely identifies the pay header record within the data base.
;[Entity|ENTITY_CODE]:The entity associated with the pay header is identified in this field.
;[Person|PERSON_CODE]:The individual associated with the pay header is identified in this field.
;[Employment Type|EMPLOYMENT_TYPE]:The employment type associated with the pay header is identified in this field.
;[Date of Hire|HIRE_DATE]:The individual's hire date is displayed in this field.
;[Pay Number|PAY_NUMBER]:This field shows the unique pay number assigned to each pay header that is created for a person.
;[User|USER_NAME]:The user associated with the pay header is identified in this field.
;[Unit|UNIT_CODE]:This is the unit to which the group indicated belongs.
;[Group|GROUP_CODE]:This is the group derived from the pay header assignment work rule.
;[Country Name|COUNTRY_CODE]:The country where the employee resides is indicated in this field.
;[Home State|HOME_STATE_PROVINCE_CODE]:This field holds the state or province where the employee resides.
;[Work State|WORK_STATE_PROVINCE_CODE]:This field shows the State or Province code standard abbreviation where the employee works.
;[Pay Category|PAY_CATEGORY_CODE]:The pay category associated with the pay header is displayed in this field.
;[Pay Calendar|PAY_CALENDAR_CODE]:The pay calendar associated with the pay header is displayed in this field.
;[Pay Period|PAY_PERIOD]:Pay periods are numbered by the year, followed by the period of the year.
;[Payroll|PAYROLL_CODE]:This field displays the payroll associated with the pay header.
;[Batch #|BATCH_NUMBER]:This field shows the batch to which this pay is attached.
;[Pay Run|PAY_RUN_NUMBER]:The pay run associated with the pay header is displayed in this field.
;[School|SCHOOL_DISTRICT_CODE]:For U.S. installations only: This field shows the school district to which the employee pays taxes.
;[Home GEO Code|GEO_CODE_HOME]:This field holds the GEO code of the home city, county or state used for taxation purposes.
At line 9 changed 45 lines
||Column name||Data Type / Size||Mand.||Notes
|[ID]|Number(10)| |Used internally to define a unique identification for the record. This field would not be loaded.
|[ENTITY_CODE]|Varchar2(16)|Y|Not moved to the software data structures, but used for validation of the employment record. Validation: The Entity Code provided must be defined on [P2K_CM_ENTITIES]
|[PERSON_CODE]|Varchar2(16)|Y|Not moved to the [P2K_CM_LOCATIONS] table, but used for validation of the employment record. Validation: Must be a valid [PERSON_CODE] already defined on the [P2K_HR_IDENTITIES] table.
|[EMPLOYMENT_TYPE]|Varchar2(30)| |Not moved to the software structures, but used for validation. Validation: The employee must have an active employment record for this employment type. Must be one of the fixed lexicon values from [X_EMPLOYMENT_TYPE]. Derivation: If you do not provide an employment type value, the conversion application will look for any [P2K_HR_EMPLOYMENTS] record that matches the other criteria. Suggestion: If you are loading employees, you can set this field to a fixed value of ‘01’.
|[HIRE_DATE]|Date()| |Not moved to the software structures, but used for validation of the employment record. Derivation: If you do not provide a hire date, the conversion application will look for any [P2K_HR_EMPLOYMENTS] record that matches the other criteria. Validation: Must be a valid date.
|[PAY_NUMBER]|Number(5)|Y|
|[USER_NAME]|Varchar2(30)| |
|[UNIT_CODE]|Varchar2(16)|Y|
|[GROUP_CODE]|Varchar2(16)|Y|
|[COUNTRY_CODE]|Varchar2(16)|Y|
|[STATE_PROVINCE_CODE_HOME]|Varchar2(16)|Y|
|[STATE_PROVINCE_CODE_WORK]|Varchar2(16)|Y|
|[PAY_CATEGORY_CODE]|Varchar2(16)|Y|
|[PAY_CALENDAR_CODE]|Varchar2(16)|Y|
|[PAY_PERIOD]|Number(10)|Y|
|[PAYROLL_CODE]|Varchar2(16)|Y|
|[BATCH_NUMBER]|Number(10)| |
|[PAY_RUN_NUMBER]|Number(10)| |
|[SCHOOL_DISTRICT_CODE]|Varchar2(16)| |
|[GEO_CODE_HOME]|Varchar2(16)| |
|[GEO_CODE_WORK]|Varchar2(16)| |
|[AUDITED]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True.
|[CHECK_NUMBER]|Number(10)| |
|[FINAL_PAY_METHOD]|Varchar2(30)| |Validation: Must be one of the fixed lexicon values from [X_FINAL_PAY_METHOD].
|[FIRST_PAY_IN_MONTH]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True.
|[FIRST_PAY_IN_PERIOD]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True.
|[HAND_CHECK]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True.
|[PAY_BY_CHECK]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True.
|[PAY_HEADER_SOURCE]|Varchar2(30)| | Validation: Must be one of the fixed lexicon values from [X_PAY_HEADER_SOURCE]
|[PAY_HEADER_STAGE]|Varchar2(30)| | Recommendation: Set this value to "70" (Closed)\\Validation: Must be one of the fixed lexicon values from [X_PAY_HEADER_STAGE]
|[PAY_RUN_SEQUENCE]|Number(5)| |
|[POSTED_BENEFITS]|Varchar2(4)| | Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True
|[POSTED_ATTENDANCE]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True
|[QUICK_PAY]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True
|[TAX_WEEKS]|Number(18)| |
|[TIMESHEET_RETURNED]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True
|[CHECK_AMOUNT]|Number(14)| |
|[PAY_ISSUE_DATE]|Date()| |Must be a valid date.
|[SUNDRY_ATTACHED]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True
|[JOURNALIZED]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N” , “NO” or “0”. All other values will translate to True
|[REVERSAL_PAY_NUMBER]|Number(5)| |
|[ASSIGNMENT_CODE]|Varchar2(16)| |
|[ASSIGNMENT_START_DATE]|Date()| |
|[JOURNALIZED_FUND]|Varchar2(4)| |
----
!! Tab 2
;[Work GEO Code|GEO_CODE_WORK]:This field holds the GEO code of the work city, county or state used for taxation purposes.
;[Audited|AUDITED]:This field indicates if the pay header has passed all the validation checks of the audit process (UPAUDT) and is ready to be processed through pay calculation.
;[Check #|CHECK_NUMBER]:The check number is assigned by you from the manual check range for the organization’s bank from IPBA.
;[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.
;[First Pay in Month|FIRST_PAY_IN_MONTH]:This field indicates if the pay header is for the first time the employee has been paid in the calendar month for a regular pay.
;[First |FIRST_PAY_IN_PERIOD]:This field indicates if this is a regular pay category header, and the first time the employee has been paid in this pay period.
;[Hand Check|HAND_CHECK]:This field indicates if the pay header is for a pay which includes a [hand written check|HAND CHECK] that needs to be recorded in the system.
;[Pay by Check|PAY_BY_CHECK]:This field indicates whether the payment will be overridden by check or prime deposit.
;[Source|PAY_HEADER_SOURCE]:This field indicates the process that created the pay header.
;[Stage|PAY_HEADER_STAGE]:This field indicates the status of a pay header.
;[Payrun Seq #|PAY_RUN_SEQUENCE]: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.
;[Posted Benefits|POSTED_BENEFITS]:
;[Posted Attendance|POSTED_ATTENDANCE]:
;[Quick Pay|QUICK_PAY]:
;[Tax Weeks|TAX_WEEKS]:This field shows the number of tax weeks associated with this pay for this pay frequency.
;[Time Sheet Returned|TIMESHEET_RETURNED]:This field indicates to the system that the employee has returned the time sheet.
;[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]’.
;[Pay Issue Date|PAY_ISSUE_DATE]:The Pay Issue Date is the date that payment is issued for the time sheet.
;[Sundry Attached|SUNDRY_ATTACHED]:This field indicates if the time sheet has been successfully processed by UPAUDT.
;[Journalized|JOURNALIZED]:If this toggle is ON, the pay line has been processed through the journalizing process (UPLG, UPGL). If the toggle is OFF, the pay line has not yet been journalized, or is not an item that requires journalizing.
\\
----
!!Tab 3
;[Pay Number|REVERSAL_PAY_NUMBER]:If the category indicated is a reversal, then the pay that is to be reversed must be indicated in this field.
;[Assignment Code|ASSIGNMENT_CODE]:This field will display the assignment for which this pay is generated.
;[Assignment Start Date|ASSIGNMENT_START_DATE]:This field will display the start date of the assignment.
;[Journalized Fund|JOURNALIZED_FUND]: This field indicates if the segment of the GL Distribution can be used as a 'Fund'.
At line 56 removed 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 59 changed 4 lines
![Discussion|Edit:Internal.IVPPH]
[{InsertPage page='Internal.IVPPH' default='Click to create a new discussion page'}]
}]
![Notes|Edit:Internal.IVPPH]
[{InsertPage page='Internal.IVPPH' default='Click to create a new notes page'}]
This page (revision-12) was last changed on 26-Nov-2021 10:22 by kparrottTop