Results for “entry_year”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_UC_SYS_CALNDRS is a configuration table in the Oracle E-Business Suite Student System (IGS) product family, historically associated with the UCAS (Universities and Colleges Admissions Service) integration that supported admissions processing for UK institutions. The table holds calendar details for UCAS Systems, binding an external admissions system identifier to the institutional calendar instances used during a given entry cycle. The product is documented as obsolete, and the source metadata records that the object is not implemented in the reference database, meaning it should be treated as a legacy or archived schema element rather than an active dependency in current deployments.

From a heuristic Data Vault modeling perspective, the FK structure supports classification as a link. The primary key combines SYSTEM_CODE, ENTRY_YEAR, and ENTRY_MONTH, forming a composite identifier that connects the UCAS system definition in IGS_UC_DEFAULTS to two distinct calendar instance references in IGS_CA_INST_ALL — one for academic calendars (ACA_CAL_TYPE / ACA_CAL_SEQ_NO) and one for admissions calendars (ADM_CAL_TYPE / ADM_CAL_SEQ_NO). This places the table as a relationship carrier between a system hub and calendar hubs rather than a pure descriptive satellite.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

  • SYSTEM_CODE — Identifier of the UCAS system configuration; part of the primary key and the FK to IGS_UC_DEFAULTS.
  • ENTRY_YEAR — The admissions entry year the calendar mapping applies to; part of the primary key.
  • ENTRY_MONTH — The entry month within that year; part of the primary key.
  • ACA_CAL_TYPE and ACA_CAL_SEQ_NO — Academic calendar type and sequence number, joined to IGS_CA_INST_ALL.
  • ADM_CAL_TYPE and ADM_CAL_SEQ_NO — Admissions calendar type and sequence number, also joined to IGS_CA_INST_ALL.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns maintained by the diagnostic and concurrency frameworks.

The primary key IGS_UC_SYS_CALNDRS_PK is defined as the composite of SYSTEM_CODE, ENTRY_YEAR, and ENTRY_MONTH. This is a genuine business-key candidate rather than a surrogate identifier; the table has no single-column surrogate key. The business key's uniqueness is enforced through the unique index backing the PK constraint, so any query identifying a single row must supply all three components.

Common Use Cases and Queries

The table was primarily consumed during UCAS admissions processing, when the integration needed to resolve which academic and admissions calendar instances corresponded to a specific system, entry year, and entry month. Typical reporting scenarios include reconciling calendar assignments across entry cycles and validating that no overlapping or missing calendar mappings exist for a system.

A representative query joining the parent system definition:

  • SELECT c.SYSTEM_CODE, c.ENTRY_YEAR, c.ENTRY_MONTH, c.ACA_CAL_TYPE, c.ADM_CAL_TYPE FROM IGS_UC_SYS_CALNDRS c, IGS_UC_DEFAULTS d WHERE c.SYSTEM_CODE = d.SYSTEM_CODE AND c.ENTRY_YEAR = :year;

To validate that both calendar references resolve to valid instances, the table can be joined twice to IGS_CA_INST_ALL, once on (ACA_CAL_TYPE, ACA_CAL_SEQ_NO) and once on (ADM_CAL_TYPE, ADM_CAL_SEQ_NO). Because the object is obsolete and not implemented, such queries are relevant mainly for legacy data migration, historical auditing, or impact analysis during upgrades from 12.1.1 to 12.2.2.

Related Objects

The documented FK relationships define the principal related objects:

  • IGS_UC_DEFAULTS — Referenced via SYSTEM_CODE; the parent definition of the UCAS system.
  • IGS_CA_INST_ALL — Referenced twice, via (ACA_CAL_TYPE, ACA_CAL_SEQ_NO) for academic calendars and (ADM_CAL_TYPE, ADM_CAL_SEQ_NO) for admissions calendars.

Additionally, the primary key and audit columns indicate dependency on standard EBS audit infrastructure, and any UCAS admissions packages or concurrent programs that read the system calendar configuration would have referenced this table directly. Given its obsolete status, no active API is documented against it in the ETRM metadata.