Search Results round_no

Overview

The IGS_UC_APP_CLR_RND table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Higher Education (Student Management) product family. Owned by the IGS schema, it serves as the primary repository for applicant clearing round details. Its fundamental role is to synchronize clearing application data with the external UCAS (Universities and Colleges Admissions Service) system, specifically with the UCAS view 'ivStartZ2'. The table tracks the progression of an applicant through multiple clearing rounds, which are processes for matching applicants with available course places after the main application cycle. It is a transactional table stored in the APPS_TS_TX_DATA tablespace.

Key Information Stored

The table's structure captures identifiers, program details, and clearing outcomes. The primary key, APP_CLEAR_ROUND_ID, is a unique system-generated identifier for each round record. Critical foreign keys include CLEARING_APP_ID, linking to the main IGS_UC_APP_CLEARING table, and SYSTEM_CODE, referencing IGS_UC_CRSE_DETS. Key business columns include APP_NO (the UCAS application number), ENQUIRY_NO (the clearing enquiry number), and ROUND_NO (the sequential clearing round number). The table maps UCAS codes (UCAS_PROGRAM_CODE, UCAS_CAMPUS) to internal Oracle Student System (OSS) codes (OSS_PROGRAM_CODE, OSS_PROGRAM_VERSION, OSS_LOCATION). The ROUND_TYPE column, now holding 'F' for forms-based clearing, and the RESULT column, which stores the coded outcome of the clearing round, are essential for process tracking. Standard WHO columns (CREATED_BY, CREATION_DATE, etc.) provide audit history.

Common Use Cases and Queries

This table is central to reporting and operational processes related to the UCAS clearing cycle. Common use cases include generating lists of applicants in a specific clearing round, tracking the history of clearing rounds for a single applicant, and reconciling data sent to or received from UCAS. A typical query would join to the parent clearing application table to get full applicant context. For example, to find all clearing round details for a specific application number:

• SELECT clr_rnd.* FROM igs.igs_uc_app_clr_rnd clr_rnd JOIN igs.igs_uc_app_clearing clr ON clr_rnd.clearing_app_id = clr.clearing_app_id WHERE clr_rnd.app_no = <application_number> ORDER BY clr_rnd.round_no;

Another common pattern is to query active clearing rounds by result code or institution to manage workflow. The DATETIMESTAMP column, though noted as obsolete, may be used in legacy synchronization checks.

Related Objects

The IGS_UC_APP_CLR_RND table is a child entity within a defined hierarchy and has specific documented foreign key relationships. The primary related objects are:

• IGS_UC_APP_CLEARING: This is the direct parent table. The relationship is defined by the foreign key where IGS_UC_APP_CLR_RND.CLEARING_APP_ID references IGS_UC_APP_CLEARING. This links each clearing round record to a master clearing applicant record.
• IGS_UC_CRSE_DETS: The table references course details via the SYSTEM_CODE column, where IGS_UC_APP_CLR_RND.SYSTEM_CODE is a foreign key to IGS_UC_CRSE_DETS. This connects the clearing round to institutional course information.

These relationships are critical for maintaining referential integrity and for constructing accurate joins in reports and interfaces that require a complete view of the applicant's clearing journey and associated course data.