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

Page References

Incoming links Outgoing links
INF_CV_TODATES
INF_CV_TODATES

Version management

Difference between version and

At line 1 changed 8 lines
!!!Alias: [IVPTD]
(INF_CV_TODATES)
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.
Tables loaded:
*[P2K_PR_TODATE_HEADERS] (first record for each set only)
*[P2K_PR_TODATE_PC_AMOUNTS] (each record)
!!!Alias: IVPTD
The INF_CV_TODATES table is used to import employee’s work assignment information and attendant data 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 11 changed 28 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|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].
|[HOME_STATE_PROVINCE_CODE]|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].
|[WORK_STATE_PROVINCE_CODE]|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 [WORK_STATE_PROVINCE_CODE] 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 [HOME_STATE_PROVINCE_CODE] 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)| |
|[CREATE_DATE]|Date()| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CREATE_USER]|Varchar2(30)| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CHANGE_DATE]|Date()| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CHANGE_USER]|Varchar2(30)| | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
----
![Notes|Edit:Internal.INF_CV_TODATES]
[{InsertPage page='Internal.INF_CV_TODATES' default='Click to create a new notes page'}]
||Column name||Data Type / Size||Domain||Mand.||Notes
|[ID]|Number(10)|[ID]| |
|[ENTITY_CODE]|Varchar2(16)|[CODE]|Y|
|[PERSON_CODE]|Varchar2(16)|[CODE]|Y|
|[EMPLOYMENT_TYPE]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[HIRE_DATE]|Date()|[DATE]| |
|[UNIT_CODE]|Varchar2(16)|[CODE]|Y|
|[GROUP_CODE]|Varchar2(16)|[CODE]|Y|
|[COUNTRY_CODE]|Varchar2(16)|[CODE]|Y|
|[STATE_PROVINCE_CODE_HOME]|Varchar2(16)|[CODE]| |
|[STATE_PROVINCE_CODE_WORK]|Varchar2(16)|[CODE]| |
|[TODATE_TYPE]|Varchar2(30)|[VARCHAR30|VARCHARnn]|Y|
|[CALENDAR_PERIOD]|Number(10)|[NUMBER10|NUMBERn]| |
|[SCHOOL_DISTRICT_CODE]|Varchar2(16)|[CODE]| |
|[GEO_CODE_WORK]|Varchar2(16)|[CODE]| |
|[GEO_CODE_HOME]|Varchar2(16)|[CODE]| |
|[PC_CODE]|Number(4)|[CODE NUMERIC]| |
|[AMOUNT]|Number(18)|[AMT12V6|AMTnn]| |
|[DESCRIPTION]|Varchar2(50)|[DESCRIPTION]| |
|[CREATE_DATE]|Date()|[DATE]| |
|[CREATE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[CHANGE_DATE]|Date()|[DATE]| |
|[CHANGE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
This page (revision-9) was last changed on 26-Nov-2021 10:22 by kparrottTop