Search Results igs_uc_sys_calndrs

Overview

The IGS_UC_SYS_CALNDRS table is a data structure within the Oracle E-Business Suite, specifically belonging to the now-obsolete IGS (Student System) product family. Its primary function is to serve as a repository for calendar details associated with UCAS (Universities and Colleges Admissions Service) systems. This table is designed to map specific UCAS application cycles, defined by an entry year and month, to internal academic and administrative calendars used within the institution's EBS instance. The metadata explicitly notes that this table is "Not implemented in this database," indicating it may represent a legacy or planned data model that was not deployed in standard installations of versions 12.1.1 or 12.2.2, but its structure remains defined for reference.

Key Information Stored

The table's design centers on defining a calendar period for a UCAS system. Its composite primary key uniquely identifies a record through a combination of SYSTEM_CODE, ENTRY_YEAR, and ENTRY_MONTH. The SYSTEM_CODE links to the overarching UCAS configuration. The ENTRY_YEAR and ENTRY_MONTH define the specific intake period for the application cycle. Crucially, the table holds foreign key references to the institution's calendar setup (IGS_CA_INST_ALL) via the ACA_CAL_TYPE and ACA_CAL_SEQ_NO columns (for the academic calendar) and the ADM_CAL_TYPE and ADM_CAL_SEQ_NO columns (for the admissions calendar). This establishes the formal link between the external UCAS timeline and the internal institutional processes.

Common Use Cases and Queries

In a scenario where this table was populated, its primary use would be to support processes that synchronize or reference UCAS deadlines and milestones with internal academic scheduling. A typical reporting query would involve joining to calendar tables to translate UCAS entry points into institutional terms or semesters. For example, to retrieve the mapped internal academic calendar for all UCAS systems for a given entry year, one might use a SQL pattern such as: SELECT syscal.SYSTEM_CODE, syscal.ENTRY_YEAR, syscal.ENTRY_MONTH, ca.CALENDAR_NAME FROM IGS_UC_SYS_CALNDRS syscal JOIN IGS_CA_INST_ALL ca ON syscal.ACA_CAL_TYPE = ca.CAL_TYPE AND syscal.ACA_CAL_SEQ_NO = ca.SEQUENCE_NUMBER WHERE syscal.ENTRY_YEAR = '2024'; Data maintenance would focus on ensuring the foreign key relationships to IGS_CA_INST_ALL remain valid when institutional calendars are updated.

Related Objects

The table maintains defined relationships with other key entities in the obsolete Student System module, as documented by its foreign keys:

• IGS_UC_DEFAULTS: The SYSTEM_CODE column in IGS_UC_SYS_CALNDRS references the IGS_UC_DEFAULTS table, linking the calendar details to a specific UCAS system configuration.
• IGS_CA_INST_ALL (Academic Calendar): The columns ACA_CAL_TYPE and ACA_CAL_SEQ_NO together form a foreign key reference to the IGS_CA_INST_ALL table, mapping the UCAS entry period to an institutional academic calendar instance.
• IGS_CA_INST_ALL (Admissions Calendar): Similarly, the columns ADM_CAL_TYPE and ADM_CAL_SEQ_NO form a second foreign key reference to the IGS_CA_INST_ALL table, mapping to a separate calendar instance used for admissions-related activities.

The primary key IGS_UC_SYS_CALNDRS_PK (SYSTEM_CODE, ENTRY_YEAR, ENTRY_MONTH) ensures uniqueness for each UCAS system and entry point combination.