Results for “igs_uc_ucas_control”

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

Overview

The IGS.IGS_UC_UCAS_CONTROL table is a control table within the Oracle E-Business Suite Student System (IGS) product family. It holds control information supplied by UCAS (the United Kingdom Universities and Colleges Admissions Service), the centralized admissions body through which undergraduate applications are routed. Unlike the transactional admissions tables in the IGS_UC_* schema, this table functions as a system-level configuration and synchronization anchor: it stores the current state of the UCAS interface as published by UCAS itself, rather than applicant data entered locally.

The defining structural characteristic of this table is that it always contains exactly one record at any given time. It synchronizes with the UCAS view cvControl and is refreshed every time a UCAS import is run. Because of this, it behaves as a singleton state holder rather than a growing transactional table. Its primary key, IGS_UC_UCAS_CONTROL_PK, is defined on the composite of SYSTEM_CODE and UCAS_CYCLE, which allows the design to accommodate control records across multiple UCAS cycles and system codes even though only one row is active per synchronization.

Mined from its foreign key structure, the heuristic Data Vault classification for this table is satellite-leaning. In Data Vault modeling terms, it is best treated as a satellite attached to the IGS_UC_DEFAULTS hub, capturing descriptive control attributes keyed by system code and cycle rather than acting as an independent business key hub. This classification is a modeling suggestion derived from FK relationships, not an Oracle-documented designation.

Key Information Stored

The table contains 36 documented columns. The most significant are summarized below.

• SYSTEM_CODE — Part of the composite primary key; the foreign key column referencing IGS_UC_DEFAULTS.
• UCAS_CYCLE — The remaining component of the composite primary key; identifies the UCAS admissions cycle.
• ENTRY_YEAR — The entry year associated with the current control record.
• APPNO_FIRST, APPNO_MAXIMUM, APPNO_LAST_USED — The applicant number allocation range and the last number issued, governing local applicant number generation.
• APPNO_FIRST_OPF, APPNO_FIRST_RPA_NONEU, APPNO_FIRST_RPA_EU — Cycle-specific applicant number starting points for different applicant categories.
• APPNO_15DEC, APPNO_24MAR, APPNO_16MAY and their corresponding RUN_DATE_* columns — Applicant number thresholds and run dates at key UCAS processing deadlines.
• APPNO_DECISION_PROC and RUN_DATE_DECISION_PROC — Threshold and date for the decision processing run.
• LAST_DAILY_RUN_NO, LAST_DAILY_RUN_DATE — Tracking of the most recent daily synchronization run.
• LAST_PASSPORT_DATE, LAST_LE_DATE — Dates marking the last passport and last LE (late entry) synchronization events.
• UCAS audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns.

The unique index IGS_UC_UCAS_CONTROL_PK on (SYSTEM_CODE, UCAS_CYCLE) is the business-key candidate. No separate surrogate identifier is documented; the composite key serves both as primary key and business key.

Common Use Cases and Queries

Because the table holds a single control row, queries are typically simple single-row lookups used to drive batch processes or validation logic. Typical uses include:

• Confirming the active UCAS cycle and entry year before launching an import.
• Determining the next applicant number to allocate by reading APPNO_LAST_USED and comparing it against APPNO_MAXIMUM.
• Validating deadline thresholds such as APPNO_15DEC or APPNO_24MAR during application processing.
• Monitoring the last synchronization via LAST_DAILY_RUN_DATE and related run columns.

A representative query to read the current control state is:

SELECT system_code, ucas_cycle, entry_year, appno_last_used, appno_maximum, last_daily_run_date FROM igs.igs_uc_ucas_control;

To join control information against the defaults table for reporting, the foreign key relationship supports:

SELECT c.system_code, c.ucas_cycle, c.entry_year, d.* FROM igs.igs_uc_ucas_control c JOIN igs.igs_uc_defaults d ON d.system_code = c.system_code;

Related Objects

The most significant related objects are the following.

• IGS_UC_DEFAULTS — The referenced (parent) table; joined via IGS_UC_UCAS_CONTROL.SYSTEM_CODE = IGS_UC_DEFAULTS.SYSTEM_CODE per the documented foreign key.
• IGS_UC_UCAS_CONTROL_PK — The primary key index supporting the composite unique key on SYSTEM_CODE and UCAS_CYCLE.
• UCAS view cvControl — The external UCAS view with which this table synchronizes on every import.
• The wider IGS_UC_* family of UCAS interface tables, which consume the control settings during applicant import and applicant number allocation.

The table is populated exclusively by the UCAS import process; direct maintenance by users is not appropriate given its synchronization semantics.