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

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 rforbes 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 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 2 KB JMyers to previous | to last
3 26-Nov-2021 10:22 5 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 3 KB JMyers to last

Page References

Incoming links Outgoing links
IVSRW
IVSRW

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: [IVSRW]
(INF_CV_REVIEWS)
[{TableOfContents }]
!!!REVIEW INTERFACE FILE
At line 4 changed one line
The INF_CV_REVIEWS table is used to import employee review information into the software data structures. Reviews are used to record the evaluation and assessment of an employee.
The Review Interface File screen is used to import employee review information into the software data structures.
At line 6 changed one line
Reviews are carried out for different reasons, for example, to evaluate an employee's performance, to determine their employment status, or to implement disciplinary procedures.
Review Interface File data is maintained on the [INF_CV_REVIEWS] table.
At line 8 added 26 lines
;[ID|ID]:This field identifies the review record within the data base.
;[Entity|ENTITY_CODE]:
;[Person Code|PERSON_CODE]:
;[Employment Type|EMPLOYMENT_TYPE]:
;[Date of Hire|HIRE_DATE]:
;[Assignment|ASSIGNMENT_CODE]:
;[Start Date|ASSIGNMENT_START_DATE]:
;[Number|REVIEW_NUMBER]:
;[Review Type|REVIEW_TYPE_CODE]:
;[Status|REVIEW_STATUS]:
;[Date of Review|REVIEW_DATE]:
;[User|USER_NAME]:
;[Date of Next Review|NEXT_REVIEW_DATE]:
;[Method|REVIEW_METHOD]:
;[Review Done By|REVIEW_DONE_BY]:
;[Overall Rating|OVERALL_RATING]:
;[Overall Points|OVERALL_POINTS]:
;[Based on Prior Job|BASED_ON_PRIOR_JOB]:
;[Review Comments|REVIEW_COMMENTS]:
;[Salary Matrix|MATRIX_CODE]:
;[Start Date|MATRIX_START_DATE]:
;[Category|REVIEW_CATEGORY]:
;[Rating|REVIEW_RATING]:
;[Points|REVIEW_POINTS]:
;[Approved|APPROVED]:
;[Merit Months|MERIT_MONTHS]:
At line 9 removed 34 lines
Tables loaded:
*[P2K_SA_REVIEWS]
*[P2K_SA_REVIEW_RATINGS]
*[P2K_AM_USER_FIELD_VALUES]
!!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|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.
|[ASSIGNMENT_CODE]|Varchar2(16)|Y|
|[ASSIGNMENT_START_DATE]|Date()|Y|Validation: Must be a valid date.
|[REVIEW_NUMBER]|Number(10)|Y|
|[REVIEW_TYPE_CODE]|Varchar2(16)|Y|Validation: Must be a valid review type already defined on [P2K_SA_REVIEW_TYPES].
|[REVIEW_STATUS]|Varchar2(30)|Y|Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_REVIEW_STATUS]
|[REVIEW_DATE]|Date()|Y|Validation: Must be a valid date.
|[USER_NAME]|Varchar2(30)| |Validation: Must be a valid user already defined on [P2K_AM_USERS].
|[NEXT_REVIEW_DATE]|Date()| |Validation: Must be a valid date.
|[REVIEW_METHOD]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_REVIEW_METHOD].
|[REVIEW_DONE_BY]|Varchar2(50)| |
|[OVERALL_RATING]|Varchar2(30)| |Validation: Must be either a valid lexicon code or a valid lexicon description from [X_OVERALL_RATING]
|[OVERALL_POINTS]|Number(5)| |
|[BASED_ON_PRIOR_JOB]|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.
|[DESCRIPTION]|Varchar2(50)| |
|[REVIEW_COMMENTS]|Varchar2(2000)| |
|[MATRIX_CODE]|Varchar2(16)| |Validation: Must be a valid Matrix code previously defined on [P2K_SA_SALARY_MATRICES]
|[MATRIX_START_DATE]|Date()| |Validation: Must be a valid date.
|[REVIEW_CATEGORY]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_REVIEW_CATEGORY]
|[REVIEW_RATING]|Varchar2(16)| |
|[REVIEW_POINTS]|Number(5)| |
|[APPROVED]|Varchar2(4)| |
|[MERIT_MONTHS]|Number(10)| |
At line 44 removed one line
This page (revision-9) was last changed on 26-Nov-2021 10:22 by rforbesTop