Results for “external_ref”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_UC_COM_EBL_SUBJ is a legacy Oracle E-Business Suite table in the IGS (Student System) product family, classified in the ETRM metadata as Obsolete. It stores the list of subjects offered by an examining board and is designed to synchronize with the UCAS (Universities and Colleges Admissions Service) external view cvEBLSubject. In the Oracle EBS 12.1.1 schema it is owned by the IGS schema and contains 15 documented columns. Under the 12.2.2 footprint the object is documented in ETRM but is marked "Not implemented in this database," meaning it no longer exists as a physical object in the running instance and survives only as a historical/reference artifact.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table hangs off a parent reference entity (the awarding body) and carries descriptive attributes (title, examination level, subject code) that describe a business key rather than purely resolving many-to-many relationships. This is a heuristic suggestion, not a documented fact.

Key Information Stored

The table's surrogate primary key is SUBJECT_ID, enforced by constraint IGS_UC_COM_EBL_SUBJ_PK. A unique index, IGS_UC_COM_EBL_SUBJ_U1, is also defined on SUBJECT_ID, making it the documented business-key candidate as well as the surrogate. The most significant columns are:

• SUBJECT_ID — surrogate primary key and unique business identifier for each examining-board subject.
• AWARDING_BODY — foreign key to IGS_UC_REF_AWRDBDY, identifying the awarding body that owns the subject.
• YEAR and SITTING — the academic year and examination sitting to which the subject applies; YEAR also participates in the awarding-body reference relationship.
• EXAM_LEVEL — the qualification or examination level of the subject.
• TITLE — the descriptive name of the subject.
• SUBJECT_CODE — the code used to identify the subject, typically aligned with the UCAS coding scheme.
• EXTERNAL_REF — the external reference linking the row to its UCAS source record.
• IMPORTED — flag indicating whether the record was imported from UCAS.
• DATETIMESTAMP — timestamp used for synchronization with the UCAS view.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Historically, this table supported UCAS admissions processing, providing the validation list of examining-board subjects against which applicant qualifications were checked. A representative query joining the subject to its awarding body would look like:

SELECT s.SUBJECT_ID, s.SUBJECT_CODE, s.TITLE, s.EXAM_LEVEL, a.AWARDING_BODY_NAME FROM IGS_UC_COM_EBL_SUBJ s, IGS_UC_REF_AWRDBDY a WHERE s.AWARDING_BODY = a.AWARDING_BODY AND s.YEAR = :year;

Reporting scenarios included listing subjects by awarding body and sitting, reconciliation of imported UCAS records (IMPORTED = 'Y'), and extraction of applicant results keyed on SUBJECT_ID. Because the table is obsolete and not implemented, any modernization effort should treat these queries as migration references only.

Related Objects

The metadata documents IGS_UC_COM_EBL_SUBJ.AWARDING_BODY as a foreign key to IGS_UC_REF_AWRDBDY, and numerous tables reference its SUBJECT_ID. The most significant related objects are:

• IGS_UC_REF_AWRDBDY — awarding-body reference; joined on AWARDING_BODY (and YEAR).
• IGS_UC_APP_RESULTS — applicant examination results; joined on SUBJECT_ID.
• IGS_AD_PAST_HISTORY_ALL — prior academic history; joined on SUBJECT_ID.
• ENG_SUBJECTS_B and ENG_SUBJECTS_TL — engineering subject definitions; joined on SUBJECT_ID.
• BISM_SUBJECTS and BISM_PERMISSIONS — business intelligence subject mapping and permissions; joined on SUBJECT_ID.
• HZ_RELATIONSHIPS — TCA relationship records; referenced on SUBJECT_ID.

The UCAS view cvEBLSubject is the external counterpart with which this table synchronizes, and while documented, these references should be validated against the target 12.2.2 instance because the table is flagged as not implemented.