JPM_PID_SUM_VW(SQL View) |
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. |
SELECT JPM_PROFILE_ID , JPM_CAT_SETID , JPM_RLAT_KEY1 , JPM_RLAT_KEY2 , JPM_RLAT_KEY3 , JPM_RLAT_KEY4 , JPM_RLAT_NAME , EFFDT , EFF_STATUS , JPM_JP_XRLAT_TYPE FROM PS_JPM_JP_X_RLAT A WHERE JPM_JP_XRLAT_TYPE = 'PIDO' AND EFFDT = ( SELECT MAX(EFFDT) FROM PS_JPM_JP_X_RLAT A1 WHERE A1.JPM_PROFILE_ID = A.JPM_PROFILE_ID AND A1.JPM_CAT_SETID = A.JPM_CAT_SETID AND A1.JPM_RLAT_KEY1 = A.JPM_RLAT_KEY1 AND A1.JPM_RLAT_KEY2 = A.JPM_RLAT_KEY2 AND A1.JPM_RLAT_KEY3 = A.JPM_RLAT_KEY3 AND A1.JPM_RLAT_KEY4 = A.JPM_RLAT_KEY4 AND A1.JPM_RLAT_NAME = A.JPM_RLAT_NAME) |
# | 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.
Prompt Table: JPM_PROFILE |
2 | JPM_CAT_SETID | 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 |
3 | 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).
Prompt Table: JPM_JP_PID_DVW1 |
4 | 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).
Prompt Table: JPM_JP_PID_DVW2 |
5 | 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).
Prompt Table: JPM_JP_PID_DVW3 |
6 | 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).
Prompt Table: JPM_JP_PID_DVW4 |
7 | 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.
Prompt Table: JPM_RLATCFGI_VW |
8 | EFFDT | Date(10) | DATE |
Effective Date
Default Value: %date |
9 | EFF_STATUS | Character(1) | VARCHAR2(1) NOT NULL |
Effective Status
A=Active I=Inactive Default Value: A |
10 | JPM_JP_XRLAT_TYPE | Character(4) | VARCHAR2(4) NOT NULL |
Indicates the type of relationship - profile identity, profile association, search filter, etc - that is represented for JPM Profiles
ASSC=Profile Association FLT=Search Filter PIDO=Profile Identity Option Default Value: PIDO |