LM_PER_JBOBJ_VW (SQL View)	Index Back
Person Job Data Effective dates are not filtered based on current effective date

LM_PER_JBOBJ_VW

(SQL View)

Person Job Data

Effective dates are not filtered based on current effective date

SELECT DISTINCT A.LM_PERSON_ID , A.EFFDT , B.LM_JOBCODE_ID , B.LM_OBJV_ID , A.LM_END_EFFDT FROM PS_LM_CURR_JOB_VW A , PS_LM_JOB_OBJV B WHERE %CurrentDateIn BETWEEN A.EFFDT AND A.LM_END_EFFDT AND B.LM_JOBCODE_ID = A.LM_JOBCODE_ID

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description

1 LM_PERSON_ID Number(15,0) DECIMAL(15) NOT NULL ELM Person ID

2 EFFDT Date(10) DATE NOT NULL Effective Date
Default Value: %date

3 LM_JOBCODE_ID Number(15,0) DECIMAL(15) NOT NULL JobCode ID
Prompt Table: LM_JOBCODE_VW

4 LM_OBJV_ID Number(10,0) DECIMAL(10) NOT NULL Objective ID. System Generated ID Number associated with each Objective.

5 LM_END_EFFDT Date(10) DATE The end effective date, automatically maintained, there's a doc on how this works, so read it

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	LM_PERSON_ID	Number(15,0)	DECIMAL(15) NOT NULL	ELM Person ID
2	EFFDT	Date(10)	DATE NOT NULL	Effective Date Default Value: %date
3	LM_JOBCODE_ID	Number(15,0)	DECIMAL(15) NOT NULL	JobCode ID Prompt Table: LM_JOBCODE_VW
4	LM_OBJV_ID	Number(10,0)	DECIMAL(10) NOT NULL	Objective ID. System Generated ID Number associated with each Objective.
5	LM_END_EFFDT	Date(10)	DATE	The end effective date, automatically maintained, there's a doc on how this works, so read it