FT_TP_RLAT(SQL Table) | 
Index Back | 
|---|---|
Profile External RelationshipsEffective Date of a set of Profile External Relationships. We must track External Relationships as an Effectived-Dated GROUP because we allow multiple entries for a single Relationship Name to be in effect concurrently. | 
| # | PeopleSoft Field Name | PeopleSoft Field Type | Database Column Type | Description | 
|---|---|---|---|---|
| 1 | 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.
 Prompt Table: JPM_PROFILE  | 
|
| 2 | Date(10) | DATE | 
Effective Date
 Default Value: %date  | 
|
| 3 | Character(5) | VARCHAR2(5) NOT NULL | 
Optional property of an item in Profiles to provide a setid value, often used in conjunction with another property that is setid based.
 Prompt Table: SETID_TBL  | 
|
| 4 | 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).
 Prompt Table: %EDITTABLE  | 
|
| 5 | 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). | |
| 6 | 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). | |
| 7 | 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). | |
| 8 | 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.
 Prompt Table: JPM_JP_PID_VW  | 
|
| 9 | FT_TP_RLAT_GUID | Character(36) | VARCHAR2(36) NOT NULL | Profile Relations GUID | 
| 10 | FT_BUS_GROUP_GUID | Character(36) | VARCHAR2(36) NOT NULL | Business Group ID | 
| 11 | FT_RLAT_NAME_GUID | Character(36) | VARCHAR2(36) NOT NULL | RLAT Name | 
| 12 | FT_TP_GUID | Character(36) | VARCHAR2(36) NOT NULL | TalentProfileGUID | 
| 13 | FT_OBJECT_GUID | Character(36) | VARCHAR2(36) NOT NULL | Object Guid | 
| 14 | Date(10) | DATE | Effective Start Date | |
| 15 | FT_EFF_END_DATE | Date(10) | DATE | Effective End Date | 
| 16 | FT_OBJ_VER_NUM | Number(9,0) | DECIMAL(9) NOT NULL | Object Version Number | 
| 17 | FT_CREATED_BY | Character(64) | VARCHAR2(64) NOT NULL | Created By | 
| 18 | FT_CREATION_DATE | Date(10) | DATE | Creation Date | 
| 19 | FT_LAST_UPD_DATE | Date(10) | DATE | Last Updated Date | 
| 20 | FT_LAST_UPDATED_BY | Character(64) | VARCHAR2(64) NOT NULL | Last Updated By | 
| 21 | FT_LAST_UPD_LOGIN | Character(32) | VARCHAR2(32) NOT NULL | Last Updated Login | 
| 22 | FT_PROC_MARKER | Character(36) | VARCHAR2(36) NOT NULL | Process marker field | 
| 23 | FT_ERROR_FLAG | Character(1) | VARCHAR2(1) NOT NULL | 
Error Flag
 N=No Y=Yes Default Value: N  | 
| 24 | FT_BYPASS_FLAG | Character(1) | VARCHAR2(1) NOT NULL | 
Bypass Flag
 Default Value: N  | 
| 25 | FT_ALTERNATE_REC | Character(50) | VARCHAR2(50) NOT NULL | Source Record | 
| 26 | FT_ALTERNATE_KEY | Character(254) | VARCHAR2(254) NOT NULL | Alternate Key | 
| 27 | FT_EFFDT_PSFMT | Character(10) | VARCHAR2(10) NOT NULL | Effective Date in PS Format |