Search Results igs_uc_app_clr_rnd

Overview

The IGS_UC_APP_CLR_RND table is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically designed to manage the UK's Universities and Colleges Admissions Service (UCAS) clearing process. Its primary role is to store detailed records for each clearing round an applicant enters, acting as a critical integration point between the institution's internal EBS system and the external UCAS service. The table is engineered to synchronize directly with the UCAS view named 'ivStartZ2', ensuring data consistency between the university's applicant tracking and the central UCAS clearing system. It is important to note that this table is part of the IGS module, which is marked as obsolete in the provided ETRM documentation for EBS releases 12.1.1 and 12.2.2. This status indicates that while the table may exist in implementations, its associated functionality is likely deprecated or has been superseded by an alternative architecture.

Key Information Stored

The table's structure is centered on tracking the progression of an applicant through specific clearing rounds. While the full column list is not detailed in the excerpt, the foreign key relationships and primary key reveal its core data elements. The primary key, APP_CLEAR_ROUND_ID, uniquely identifies each clearing round record. The table stores a foreign key, CLEARING_APP_ID, which links the round details to a parent clearing application record in the IGS_UC_APP_CLEARING table. Furthermore, it holds identifiers that pinpoint the specific course and institution for which the applicant is being considered in that round, including SYSTEM_CODE, UCAS_PROGRAM_CODE, INSTITUTION, and UCAS_CAMPUS. These columns collectively reference the IGS_UC_CRSE_DETS table, which holds UCAS course details.

Common Use Cases and Queries

The primary use case for this table is reporting and auditing an applicant's journey through the UCAS clearing process. Administrators could query it to generate lists of all applicants currently active in a particular clearing round or to trace the sequence of courses an applicant was considered for during clearing. A typical reporting query would join this table to its parent and reference tables to produce a comprehensible list. For example, to list all clearing round details for a specific applicant, one might use a SQL pattern such as:

SELECT rnd.*, crse.course_title
FROM IGS_UC_APP_CLR_RND rnd,
     IGS_UC_APP_CLEARING app,
     IGS_UC_CRSE_DETS crse
WHERE rnd.clearing_app_id = app.clearing_app_id
AND app.applicant_id = :applicant_number
AND rnd.system_code = crse.system_code
AND rnd.ucas_program_code = crse.ucas_program_code
ORDER BY rnd.app_clear_round_id;

Given the module's obsolete status, direct transactional use or customization is strongly discouraged in favor of any successor functionality provided by Oracle.

Related Objects

The IGS_UC_APP_CLR_RND table exists within a defined schema of related UCAS integration tables, as evidenced by its documented foreign key constraints.

• IGS_UC_APP_CLEARING: This is the parent table for the clearing application. The relationship is defined by the column IGS_UC_APP_CLR_RND.CLEARING_APP_ID, which references a record in IGS_UC_APP_CLEARING.
• IGS_UC_CRSE_DETS: This table holds master details for UCAS courses. The clearing round record links to a specific course via a composite foreign key using the columns IGS_UC_APP_CLR_RND.SYSTEM_CODE, IGS_UC_APP_CLR_RND.UCAS_PROGRAM_CODE, IGS_UC_APP_CLR_RND.INSTITUTION, and IGS_UC_APP_CLR_RND.UCAS_CAMPUS.

These relationships are essential for constructing complete reports that combine applicant clearing activity with application headers and course descriptions.