UPG_JOB_COMP(SQL Table) |
Index Back |
---|---|
Upgrade Only - Legacy BackupUpgrade Only - Legacy Backup This table holds a backup of Legacy Data created during the upgrade to Profile Management 9.0. When the customer is satisfied with the upgrade or no longer needs a copy of the prior data, this table should be dropped from the Database. |
# | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description |
---|---|---|---|---|
1 | JOB_PROFILE_ID | Character(12) | VARCHAR2(12) NOT NULL | Job Profile ID |
2 | EFFDT | Date(10) | DATE |
Effective Date
Default Value: %date |
3 | COMPETENCY | Character(8) | VARCHAR2(8) NOT NULL | Competency |
4 | TARGET_PROFICIENCY | Character(1) | VARCHAR2(1) NOT NULL | Target Proficiency |
5 | EP_WEIGHT | Number(3,0) | SMALLINT NOT NULL | Weight factor |
6 | EP_MIN_WEIGHT | Number(3,0) | SMALLINT NOT NULL | Minumum weight used (percentage) |
7 | EP_ITEM_MANDTRY_SW | Character(1) | VARCHAR2(1) NOT NULL |
Yes/No switch used to determine if the mandatory field is available
Default Value: N |
8 | EP_ITEM_CRIT_SW | Character(1) | VARCHAR2(1) NOT NULL |
Yes/No switch used to determine if the critical field is available
Default Value: N |
9 | JPM_ITEM_KEY_ID | Number(12,0) | DECIMAL(12) NOT NULL | Unique identifier of an item within a profile. This is the primary key of profile items. It is a generic autoassigned value (a number). The unique key permits the addition of items that are not inheritently unique. They may have the same effective date, item type, item id, yet differ in a property or other value. The concept of key fields in a profile is a loose term as an object in a profile can have very different needs in identification. |