Results for “igs_uc_com_inst”

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

Overview

The IGS_UC_COM_INST table is a legacy data object belonging to the IGS (Student System) product family within Oracle E-Business Suite. It holds the list of all institutions known to the UCAS (Universities and Colleges Admissions Service) integration layer, and its rows are synchronized with the external UCAS view cvInstitution. Because the IGS product line is obsolete, the table exists primarily as a historical reference for institutions that once ran the UCAS admissions interface on EBS 12.1.1 or 12.2.2.

The ETRM metadata classifies this object as standalone under the heuristic Data Vault model — it has no outgoing or incoming foreign key dependencies on other documented tables. In Data Vault terms, this suggests IGS_UC_COM_INST functions as a hub candidate: a stable business entity (the institution) keyed by a business identifier rather than by transactional relationships. Because there are no dependent links or satellites mined from the schema, the table carries its descriptive attributes directly in-line, which is characteristic of pre-Data-Vault legacy designs.

Key Information Stored

The table comprises 14 documented columns. Its surrogate primary key is INST, enforced through IGS_UC_COM_INST_PK. A unique index, IGS_UC_COM_INST_U1, also exists on INST, marking it as the primary business-key candidate. Notably, no separate natural-key column is uniquely indexed, so INST serves both roles in the documented schema.

The most significant columns are:

• INST — Surrogate/business-key identifier for the institution record.
• INST_CODE — The institution code used by UCAS, the practical business reference.
• INST_NAME — Full name of the institution.
• DATETIMESTAMP — Timestamp associated with the record, typically reflecting the last synchronization from cvInstitution.
• UCAS, GTTR, SWAS, NMAS — Flags indicating the institution's participation in each respective admissions scheme.
• IMPORTED — Status flag indicating whether the record has been imported into the local EBS instance.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit fields tracking record provenance.

The metadata explicitly notes: "Not implemented in this database," meaning the table may be absent or unpopulated in a given environment even when the IGS schema exists.

Common Use Cases and Queries

Typical usage centers on reference lookups and reconciliation of institution data against the UCAS feed. A common pattern is to resolve an institution code to a name for admissions reporting:

SELECT INST_CODE, INST_NAME FROM IGS_UC_COM_INST WHERE INST_CODE = :p_code;

Analysts often validate synchronization freshness by inspecting the DATETIMESTAMP column, particularly for records where IMPORTED is flagged. A reconciliation query might compare the count of locally imported institutions against the expected UCAS population. Scheme-participation reporting can filter on UCAS, GTTR, SWAS, or NMAS flags to identify which institutions belong to which admissions route. Audit queries leveraging LAST_UPDATE_DATE and LAST_UPDATED_BY help trace when institution data was last refreshed and by which user or process.

Related Objects

The mined relationship data classifies IGS_UC_COM_INST as standalone, with no FK links to other documented objects. Consequently, related-object guidance is inferential. The most significant association is the external UCAS source:

• UCAS view cvInstitution — the external integration source with which IGS_UC_COM_INST synchronizes.
• IGS_UC_COM_INST_PK / IGS_UC_COM_INST_U1 — the primary-key constraint and unique index defining record identity.

Other IGS_UC_* interface tables (for applicants, courses, and applications) would logically join to this table on INST to resolve institution details, but such joins should be verified against the specific environment's schema, since the documented relationship model shows no enforced foreign keys.