Results for “igs_uc_ref_keywords”
25 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_UC_REF_KEYWORDS is a reference table within the IGS (Student System) product family, which is marked obsolete in Oracle EBS 12.1.1 and 12.2.2. The table holds the authoritative list of keywords used in the Universities and Colleges Admissions Service (UCAS) integration. Its content is synchronized with the external UCAS view cvRefKeyword, meaning the table acts as a local materialization of a controlled vocabulary maintained by UCAS and consumed by the EBS student system during admissions data exchange.
From a Data Vault modeling perspective, the table is classified heuristically as hub-leaning. This classification reflects the fact that the object functions as a stable repository of business keys — keywords — that are referenced by transactional or associative tables elsewhere in the schema. In practice, IGS_UC_REF_KEYWORDS should be treated as a reference or lookup hub, with dependent tables supplying the descriptive and historical context.
Key Information Stored
The documented physical schema contains seven columns. The most significant are:
- KEYWORD — The business identifier for each keyword entry. It is both the primary key column (via IGS_UC_REF_KEYWORDS_PK) and the sole column of the unique index IGS_UC_REF_KEYWORDS_U1, making it the unambiguous business-key candidate. Note that the primary key is defined on the natural business key rather than a system-generated surrogate, so KEYWORD serves simultaneously as PK and business key.
- IMPORTED — A flag indicating whether the record originated from a UCAS import process, supporting synchronization auditing against the external cvRefKeyword view.
- CREATED_BY, CREATION_DATE — Standard EBS audit columns recording the user and timestamp of row creation.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification context, used for change tracking and integration reconciliation.
Because the metadata provides only seven columns and the descriptive attributes are limited, the table's expressive content is concentrated almost entirely in the KEYWORD value itself; the remaining columns are audit and provenance attributes.
Common Use Cases and Queries
Typical use cases involve validation of keyword values incoming from UCAS feeds and reporting on the keyword vocabulary associated with courses.
- Listing all available keywords:
SELECT keyword, imported, last_update_date FROM igs_uc_ref_keywords ORDER BY keyword;
- Identifying imported versus locally maintained keywords:
SELECT keyword FROM igs_uc_ref_keywords WHERE imported = 'Y';
- Joining to course keyword associations:
SELECT k.keyword, ck.course_code FROM igs_uc_ref_keywords k, igs_uc_crse_keywrds ck WHERE k.keyword = ck.keyword; - Detecting stale reference data by audit timestamp:
SELECT keyword, last_updated_by, last_update_date FROM igs_uc_ref_keywords WHERE last_update_date < SYSDATE - 365;
These patterns support data quality checks, integration troubleshooting, and reconciliation against the UCAS source view.
Related Objects
The most significant dependent object is IGS_UC_CRSE_KEYWRDS, which references IGS_UC_REF_KEYWORDS through the foreign key column KEYWORD. This establishes a parent-child relationship in which each course keyword association must resolve to a valid reference keyword. The external UCAS view cvRefKeyword is the synchronization source and should be considered as part of the integration landscape even though it resides outside the EBS schema. The table is not implemented in the current database, so any related application programming interfaces or concurrent programs that previously consumed it are likewise dormant. The unique index IGS_UC_REF_KEYWORDS_U1 and the primary key constraint IGS_UC_REF_KEYWORDS_PK both enforce uniqueness on KEYWORD and are the principal structural artifacts of the object. Because the product is obsolete in 12.1.1 and 12.2.2, these relationships are relevant primarily for historical data migration and legacy reporting rather than for active configuration.
-
Holds the list of keywords. It synchronizes with UCAS view 'cvRefKeyword'
-
Table: IGS_UC_REF_KEYWORDS 12.2.2
Holds the list of keywords. It synchronizes with UCAS view 'cvRefKeyword'
Not implemented in this database·Explore IGS module →
-
Table: IGS_UC_CRSE_KEYWRDS 12.2.2
Holds the keywords linked to a course during the UCAS admission cycle . It synchronizes with UCAS view 'uvCourseKeyword'
Not implemented in this database·Explore IGS module →
-
Holds the keywords linked to a course during the UCAS admission cycle . It synchronizes with UCAS view 'uvCourseKeyword'
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.