FT_JP_ROLE(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 | JPM_PROFILE_ID | Character(12) | VARCHAR2(12) NOT NULL | The id, autoassigned or user assigned of the profile. This id is used to group items and other related material together into one coherent profile. |
2 | EFFDT | Date(10) | DATE |
Effective Date
Default Value: %date |
3 | POSITION_NBR | Character(8) | VARCHAR2(8) NOT NULL | Position Number |
4 | JOB_FAMILY | Character(6) | VARCHAR2(6) NOT NULL | Job Family |
5 | SETID | Character(5) | VARCHAR2(5) NOT NULL | SetID |
6 | JOBCODE | Character(6) | VARCHAR2(6) NOT NULL | Job Code |
7 | JOB_TASK | Character(6) | VARCHAR2(6) NOT NULL | Job Task |
8 | EVAL_METHOD | Character(1) | VARCHAR2(1) NOT NULL | Method of Evaluation |
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. |
10 | JPM_RLAT_NAME | Character(30) | VARCHAR2(30) NOT NULL | Name of the relationship being established between JPM Data and External Data. Example - JOB CODE might be used to indicate that the relationship is between a JPM Profile of Job and External Data such as the Job Code on the Job Code table. |
11 | JPM_RLAT_KEY1 | Character(30) | VARCHAR2(30) NOT NULL | Key value identifying the external data being related to JPM data. Example- Job Codes (external data) being related to a Profile of a Job (JPM data). |
12 | JPM_RLAT_KEY2 | Character(30) | VARCHAR2(30) NOT NULL | Key value identifying the external data being related to JPM data. Example- Job Codes (external data) being related to a Profile of a Job (JPM data). |
13 | JPM_RLAT_KEY3 | Character(30) | VARCHAR2(30) NOT NULL | Key value identifying the external data being related to JPM data. Example- Job Codes (external data) being related to a Profile of a Job (JPM data). |
14 | JPM_RLAT_KEY4 | Character(30) | VARCHAR2(30) NOT NULL | Key value identifying the external data being related to JPM data. Example- Job Codes (external data) being related to a Profile of a Job (JPM data). |
15 | DESCR | Character(30) | VARCHAR2(30) NOT NULL | Description |
16 | DESCRSHORT | Character(10) | VARCHAR2(10) NOT NULL | Short Description |
17 | DESCRLONG | Long Character | CLOB | Long Description |
18 | FT_ALTERNATE_REC | Character(50) | VARCHAR2(50) NOT NULL | Source Record |
19 | FT_ALTERNATE_KEY | Character(254) | VARCHAR2(254) NOT NULL | Alternate Key |