Results for “entry_point”

25 results




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

Overview

IGS_UC_APP_CLEARING is a table within the Oracle E-Business Suite IGS (Student System) product family. Per the ETRM metadata, the IGS product line is flagged as obsolete in Oracle EBS 12.1.1 and 12.2.2, and this specific table is documented as "Not implemented in this database." Its purpose, as described, is to hold applicant clearing details and to synchronize with the UCAS view 'ivStarZ1'. UCAS (the Universities and Colleges Admissions Service) is the central admissions body in the United Kingdom, and the clearing process represents the late-stage matching of applicants to available university places. This table therefore occupies the integration boundary between EBS Student System data and external UCAS clearing feeds.

From a dimensional modeling perspective, the ETRM Data Vault heuristic classifies this object as satellite-leaning. This suggests it is best modeled as a satellite structure attached to a parent hub (the applicant), capturing descriptive clearing attributes keyed by the clearing application identifier rather than acting as an independent hub or a many-to-many link.

Key Information Stored

The table contains 23 documented columns. The surrogate primary key is CLEARING_APP_ID, enforced by the IGS_UC_APP_CLEARING_PK constraint and also backed by the unique index IGS_UC_APP_CLEARING_U1 (CLEARING_APP_ID), making it both the technical and business-key identifier for a clearing record.

The foreign key APP_ID references IGS_UC_APPLICANTS, tying each clearing record to the originating applicant. Other significant columns include:

  • ENQUIRY_NO and APP_NO — the UCAS enquiry and application reference numbers used to correlate with external UCAS correspondence.
  • INSTITUTION, COURSE, CAMPUS — the destination institution, course, and campus associated with the clearing place.
  • ENTRY_MONTH, ENTRY_YEAR, ENTRY_POINT — the intended intake period and entry qualification point.
  • RESULT — the outcome of the clearing application.
  • CENTRAL_CLEARING — indicates whether the record originates from central clearing processing.
  • CEF_NO, DATE_CEF_SENT, CEF_RECEIVED — the Clearing Entry Form number and its despatch/receipt dates, which are central to clearing workflow tracking.
  • CLEARING_APP_SOURCE and IMPORTED — flags identifying the data source and whether the record was imported from UCAS.
  • DATETIMESTAMP — a timestamp associated with the clearing record.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical use cases center on monitoring the clearing pipeline and reconciling inbound UCAS data. A common pattern joins clearing records to applicants:

  • Reporting applicants with an active clearing application: SELECT a.*, c.* FROM IGS_UC_APPLICANTS a JOIN IGS_UC_APP_CLEARING c ON a.APP_ID = c.APP_ID;
  • Tracking Clearing Entry Form turnaround by comparing DATE_CEF_SENT against CEF_RECEIVED to identify outstanding forms.
  • Filtering by IMPORTED or CLEARING_APP_SOURCE to audit which clearing records arrived via the UCAS synchronization path.
  • Reporting by ENTRY_YEAR / ENTRY_MONTH to summarize clearing volumes per intake and institution.

Because the table is documented as not implemented in the reference database, these queries are illustrative of intended usage rather than verified against a live instance.

Related Objects

The principal related objects derive directly from the documented foreign keys:

  • IGS_UC_APPLICANTS — parent entity referenced via IGS_UC_APP_CLEARING.APP_ID, supplying core applicant identity.
  • IGS_UC_APP_CLR_RND — dependent table referencing IGS_UC_APP_CLEARING.CLEARING_APP_ID, holding clearing round details linked to each clearing application.
  • The UCAS view 'ivStarZ1' — the external synchronization target associated with this table, per the documented description.

No documented APIs or additional views are recorded in the ETRM metadata, so the applicant, the clearing round table, and the UCAS view represent the primary relationship surface for this object.