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

Page References

Incoming links Outgoing links
IVPTD
IVPTD

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: [IVPTD]
(INF_CV_TODATES)
[{TableOfContents }]
!!!TODATE INTERFACE FILE
At line 4 changed one line
The INF_CV_TODATES table is used to import employee’s to-date (YTD, MTD, QTD) amounts into the software data structures. The TODATES table stores pay component information for year, quarter, month, fiscal and assignment to-date periods. The information is stored in two tables: a “header” and “pay component details”. A new header record is created for each combination of the following fields: Employment record (entity, person_code, employment_type, hire_date), group (for specific unit), state/province of work, state/province of residence (within the country specified), School District Code, GEO Code for work, GEO Code for residence, type of To-date (year, month, etc.) and specific period for that to-date type.
The ToDate Interface File screen is used to import employee’s to-date (YTD, MTD, QTD) amounts into the software data structures. The TODATES table stores pay component information for year, quarter, month, fiscal and assignment to-date periods. The information is stored in two tables: a “header” and “pay component details”. A new header record is created for each combination of the following fields: Employment record (entity, person_code, employment_type, hire_date), group (for specific unit), state/province of work, state/province of residence (within the country specified), School District Code, GEO Code for work, GEO Code for residence, type of To-date (year, month, etc.) and specific period for that to-date type.
At line 6 removed 24 lines
Tables loaded:
*[P2K_PR_TODATE_HEADERS] (first record for each set only)
*[P2K_PR_TODATE_PC_AMOUNTS] (each record)
!!Table Columns
\\
||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|Used for validation of the employment record. Validation: The Entity Code provided must be defined on [P2K_CM_ENTITIES].
|[PERSON_CODE]|Varchar2(16)|Y|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)| |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()| |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.
|[UNIT_CODE]|Varchar2(16)|Y|Validation: Must be a valid [ENTITY_CODE] defined on [P2K_CM_UNITS].
|[GROUP_CODE]|Varchar2(16)|Y|Validation: Must be a valid [GROUP_CODE] defined on [P2K_CM_GROUPS].
|[COUNTRY_CODE]|Varchar2(16)|Y|Validation: Must be a valid [COUNTRY_CODE] on [P2K_CM_COUNTRIES]. If you provide a [STATE_PROVINCE_CODE], then you must provide a [COUNTRY_CODE].
|[STATE_PROVINCE_CODE_HOME]|Varchar2(16)| |Validation: Must be a valid state code or province code, for the [COUNTRY_CODE] indicated on [P2K_CM_STATE_PROVINCES]. If you provide a [STATE_PROVINCE_CODE], then you must provide a [COUNTRY_CODE].
|[STATE_PROVINCE_CODE_WORK]|Varchar2(16)| |Validation: Must be a valid state code or province code, for the [COUNTRY_CODE] indicated on [P2K_CM_STATE_PROVINCES]. If you provide a [STATE_PROVINCE_CODE], then you must provide a [COUNTRY_CODE].
|[TODATE_TYPE]|Varchar2(30)|Y|Validation: The employee must have an active employment record for this employment type. Must be one of the fixed lexicon values from [X_TODATE_TYPE]
|[CALENDAR_PERIOD]|Number(10)| |
|[SCHOOL_DISTRICT_CODE]|Varchar2(16)| |Validation: Must be a valid school district code already defined on [P2K_CM_SCHOOL_DISTRICTS]
|[GEO_CODE_WORK]|Varchar2(16)| |Validation: The [GEO_CODE] must be a valid GEO code on the [P2K_CM_TAX_JURISDICTIONS] table. If the [STATE_PROVINCE_CODE_WORK] is provided, then the [GEO_CODE] must be within that specific state, as well.
|[GEO_CODE_HOME]|Varchar2(16)| |Validation: The [GEO_CODE] must be a valid GEO code on the [P2K_CM_TAX_JURISDICTIONS] table. If the [STATE_PROVINCE_CODE_HOME] is provided, then the [GEO_CODE] must be within that specific state, as well.
|[PC_CODE]|Number(4)| |Validation: Must be a valid pay component already defined on [P2K_PR_PAY_COMPONENTS].
|[AMOUNT]|Number(18)| |
|[DESCRIPTION]|Varchar2(50)| |
At line 31 changed one line
[{If var='loginstatus' contains 'authenticated'
ToDate Interface File data is maintained on the [INF_CV_TODATES] table.
At line 9 added 19 lines
;[ID|ID]:This field uniquely identifies the todate record within the data base.
;[Entity|ENTITY_CODE]:This field displays the entity associated with the todate record.
;[Person Code|PERSON_CODE]:This field displays the person associated with the todate record.
;[Employment Type|EMPLOYMENT_TYPE]:This employee's employment type is displayed in this field.
;[Date of Hire|HIRE_DATE]:The employee's hire date is displayed in this field.
;[Unit|UNIT_CODE]:This is the union that the employee’s pays were processed under.
;[Group|GROUP_CODE]:This is the group code that the employee’s pays were processed under.
;[Country Name|COUNTRY_CODE]:The employee's country of residence is displayed in this field.
;[Home State|HOME_STATE_PROVINCE_CODE]:This field displays the state or province from the employee’s home address.
;[Work State|WORK_STATE_PROVINCE_CODE]:This field displays the state or province from the employee’s work location.
;[ToDate Type|TODATE_TYPE]:This field indicates the type of to-date record this record relates to.
;[Calendar Period|CALENDAR_PERIOD]:This field identifies the calendar associated with the record.
;[School|SCHOOL_DISTRICT_CODE]:The School District code for the employee’s home address.
;[Work GEO Code|GEO_CODE_WORK]:The field shows the Tax Jurisdiction code for the employee’s work location.
;[Home GEO Code|GEO_CODE_HOME]:This field shows the Tax Jurisdiction code for the employee’s home address.
;[PC Code|PC_CODE]:This field shows the pay component associated with the record.
;[Amount $|AMOUNT]:This field shows the amount associated with the record.
;[Description|DESCRIPTION]:This field provides a short description of the the record.
At line 34 changed 2 lines
![Discussion|Edit:Internal.IVPTD]
[{InsertPage page='Internal.IVPTD' default='Click to create a new discussion page'}]
![Notes|Edit:Internal.IVPTD]
[{InsertPage page='Internal.IVPTD' default='Click to create a new notes page'}]
At line 37 removed one line
}]
This page (revision-9) was last changed on 26-Nov-2021 10:22 by kparrottTop