Results for “dom_text”

6 results




Overview
Explore in AI Chat

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

Overview

IGS_UC_REF_APR is a reference (lookup) table within the Oracle E-Business Suite student system module, historically catalogued under the IGS – Student System product line. In Oracle EBS 12.1.1 and 12.2.2 this module is classified as obsolete; the ETRM metadata records that the object is not implemented in the current database. It exists in the schema as a legacy artifact tied to the UCAS (Universities and Colleges Admissions Service) integration layer.

Functionally, IGS_UC_REF_APR holds the list of valid domicile codes recognized by the admissions interface. It synchronizes with the external UCAS view cvRefAPR, meaning its rows are populated or refreshed from the UCAS reference data set rather than entered by institutional users. Domicile classification drives fee assessment and residency-related admissions processing, so the table acts as a controlled vocabulary consumed elsewhere in the schema.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as hub-leaning. The single inbound reference from IGS_UC_COM_SCH.COUNTRY, combined with a stable business key and a compact descriptive payload, is characteristic of a hub with a thin attached satellite rather than a transactional link.

Key Information Stored

The documented physical schema for ETRM 12.1.1 shows owner IGS with nine columns. The most significant are:

  • DOM — the domicile code, the business identifier for the record and the anchor of the primary key.
  • DOM_TEXT — the descriptive text rendered for the domicile code, typically used in list-of-values and report output.
  • LEA_FLAG — a flag distinguishing local education authority related domicile classifications, used in residency and fee rules.
  • IMPORTED — indicates whether the row originated from the UCAS synchronization process rather than local maintenance.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording the most recent modification and the login context.

The surrogate/business key is IGS_UC_REF_APR_PK, defined on DOM. A second unique index, IGS_UC_REF_APR_U1, also carries the DOM column, confirming it as the sole documented business-key candidate. No other unique constraints are recorded.

Common Use Cases and Queries

Because the table is obsolete and unimplemented in 12.1.1/12.2.2, current use cases are primarily archival, migration, or comparison exercises. Typical patterns include validating that legacy domicile codes still resolve, and auditing which rows were system-imported.

A simple lookup by code:

  • SELECT dom, dom_text, lea_flag FROM igs_uc_ref_apr WHERE dom = :p_dom;

Identifying synchronized versus locally maintained rows:

  • SELECT dom, dom_text FROM igs_uc_ref_apr WHERE imported = 'Y' ORDER BY dom;

Resolving the domicile description for related scheduled records:

  • SELECT s.*, r.dom_text FROM igs_uc_com_sch s, igs_uc_ref_apr r WHERE s.country = r.dom;

Reporting use is limited to reconciliation extracts that compare the EBS copy of domicile codes against the UCAS cvRefAPR view, and to migration scripts that map legacy DOM values into replacement reference data in later releases.

Related Objects

The documented relationship metadata identifies the following significant dependencies:

  • IGS_UC_COM_SCH — the principal dependent table. Its COUNTRY column carries a foreign key to IGS_UC_REF_APR.DOM, so every scheduled communication row resolves its domicile through this reference table.
  • IGS_UC_REF_APR_PK — the primary key constraint on DOM, enforcing uniqueness of domicile codes and supporting the join above.
  • IGS_UC_REF_APR_U1 — the unique index on DOM, reinforcing the business key and available to the optimizer for index-driven lookups.
  • UCAS cvRefAPR — the external UCAS view with which this table synchronizes; it is the authoritative source for the domicile code list rather than an in-database object.

Beyond these documented links, the table is referenced indirectly wherever admissions residency and fee logic consume domicile codes; however, no additional foreign keys or API entry points are recorded in the ETRM metadata. Administrators should treat any residual dependency as legacy and verify it against the target release before relying on the object.