| Data element |
Definition |
| Activity_Date Indexed - no
Format - Date
May be Null? Y | The latest date the source table was updated. Source: SCRCORQ |
| Corequisite_Crse_Numb Indexed - no
Format - Varchar2(5)
May be Null? Y | The course number of the co-requisite course. Source: SCRCORQ_CRSE_NUMB_CORQ |
| Corequisite_Subject Indexed - no
Format - Varchar2(4)
May be Null? Y | The subject area of the co-requisite course. Source: SCRCORQ_SUBJ_CODE_CORQ |
| Course_Id Indexed - no
Format - Varchar2(9)
May be Null? Y | The subject area and course number of the course, stored together (no spaces) |
| Course_Num Indexed - no
Format - Varchar2(5)
May be Null? Y | The course number of the course that has a co-requisite. Source: SCBCORQ_CRSE_NUMB |
| Crse_Coreqs_Pk Indexed - yes
Format - Varchar2(24)
May be Null? N | Internal warehouse primary key |
| Effective_Term Indexed - no
Format - Varchar2(6)
May be Null? Y | The term in which the co-requisite relationship went into effect. Source: SCRCORQ_EFF_TERM |
| Refresh_Date Indexed - no
Format - Date
May be Null? Y | The latest refresh date for this warehouse table |
| Subject Indexed - no
Format - Varchar2(4)
May be Null? Y | The subject area of the course that has a co-requisite. Source: SCRCORQ_SUBJ_CODE |
| Term Indexed - no
Format - Varchar2(6)
May be Null? Y | Reference term. Co-requisites are stored as term-effective in the Banner source tables; in the warehouse, the data are stored term-by-term, to facilitate reporting. There will be one row for every possible term in which the co-requisite relationship was in effect. This term can be used to join to other course tables, to get all of the relevant data in effect during the same term. |
