- Multiple active rows:
Academic Career table (PS_ACAD_CAREER_TBL) has multiple entries within the same career.
For example, UMF has two GRAD and two UGRD data. I think one of the eff_status should be "I" (inactive), but all are active.
I had to create a complicate subquery to pick the max(effdt), so the records will not be doubled when I join the tables.
If the data was clean, I didn't need to create the subquery.
UPDATE from Ursula 7/11/18:
Since information for programs and plans can change over time you create a new effective dated row. Students are governed by the requirements in effect when they entered the program. So many effective dated rows have to be active at the same time.
2. Inconsistent description:
Admit Type table (PS_ADMIT_TYPE_TBL) has different description for the same admit type.
For example, the description for admit_type= 'TRF' is "Transfer Applicant" for all except UM.
So, when we set up prompt, the prompt will show two options even though they are the same. (Or we need to create case statement to make it to one.)
UPDATE 7/3/18:
JIRA ticket was opened.
REPORT-374
-
Inconsistent descriptions on PS_ADMIT_TYPE_TBL
Closed
