Search Results igs_uc_cyc_defaults




Overview

The table IGS_UC_CYC_DEFAULTS is a data object within the Oracle E-Business Suite (EBS) Student System (IGS), specifically marked as obsolete. Its primary role was to store default configuration values associated with specific UCAS (Universities and Colleges Admissions Service) admission cycles. In the context of EBS 12.1.1 and 12.2.2, this table would have supported the integration and processing of UK university admissions data by providing a centralized repository for cycle-specific parameters, ensuring consistent application of rules and defaults across the student lifecycle management modules. The provided ETRM metadata explicitly notes that this table was "Not implemented in this database," indicating it may have been a planned or legacy component not deployed in standard installations.

Key Information Stored

The table's structure, as defined by its primary key, is designed to uniquely identify a set of defaults by a combination of a system code and a UCAS cycle identifier. The documented columns are:

  • SYSTEM_CODE: A key column linking to the parent IGS_UC_DEFAULTS table, likely identifying a specific system or institution context for the defaults.
  • UCAS_CYCLE: A column identifying the specific admissions cycle (e.g., an academic year) to which the stored default values apply.
While the specific default value columns are not detailed in the excerpt, the table's purpose implies it would have held fields for various configurable parameters relevant to a UCAS cycle, such as application deadlines, fee codes, or status settings.

Common Use Cases and Queries

In an active implementation, this table would be queried to retrieve the operative defaults for processing applications for a given admissions cycle. A typical use case would be during the application intake or batch processing phases, where the system needs to apply the correct cycle-specific rules. A fundamental query would involve joining to the parent defaults table to retrieve a full set of parameters.

Sample SQL Pattern:
SELECT ccd.*, ud.default_name, ud.default_value
FROM igs_uc_cyc_defaults ccd,
igs_uc_defaults ud
WHERE ccd.system_code = ud.system_code
AND ccd.system_code = :p_sys_code
AND ccd.ucas_cycle = :p_cycle;

Reporting would focus on auditing the default values configured for different cycles, often for compliance or setup verification purposes.

Related Objects

Based on the provided foreign key metadata, this table has a direct and documented relationship with one other object:

  • IGS_UC_DEFAULTS: This is the parent table referenced by the foreign key. The relationship is defined on the SYSTEM_CODE column. IGS_UC_CYC_DEFAULTS.SYSTEM_CODE is a foreign key to IGS_UC_DEFAULTS.SYSTEM_CODE. This suggests that IGS_UC_DEFAULTS holds a master list of default types or system-level defaults, which are then specialized per UCAS cycle in the IGS_UC_CYC_DEFAULTS table.
The primary key constraint IGS_UC_CYC_DEFAULTS_PK enforces uniqueness on the combination of SYSTEM_CODE and UCAS_CYCLE.