Search Results cef_no




Overview
Explore in AI Chat

Overview

IGSBV_UC_ENQUIRY_DETAILS is a read-only Oracle E-Business Suite database view owned by the APPS schema. It exposes enquiry and applicant data used by the UCAS (Universities and Colleges Admissions Service) integration within the Oracle Student System (IGS) product family. The view consolidates enquiry-level detail records with their associated applicant records so that reporting, admissions processing, and downstream integration components can retrieve a completed applicant/enquiry profile from a single object rather than joining the base tables manually.

The name prefix IGSBV indicates a seed/standard Oracle-supplied view (the "BV" convention commonly denotes a base view delivered by the product). Because the view text ends with WITH READ ONLY, it is intended strictly for query and reporting access — no DML is permitted against it. The view is equally valid in Oracle EBS 12.1.1 and 12.2.2, where the IGS schema objects and the APPS synonyms and grants follow the same naming pattern.

Underlying Base Objects

Although the ETRM metadata records no formally documented base objects, the view text unambiguously defines the underlying tables:

  • IGS_UC_ENQ_DETAILS (aliased EN) — the primary driving table, holding enquiry-level records including applicant number, personal details, and address.
  • IGS_UC_APPLICANTS (aliased FT1) — the applicant-level table, supplying system code, passport information, request flags, the CEF number, and the OSS person identifier.

The join is defined as EN.APP_NO = FT1.APP_NO (+), an outer join keyed on applicant number. The (+) operator on the FT1 side means enquiry records are retained even when no matching applicant row exists; applicant-derived columns then return NULL. Both tables belong to the IGS (Student System) schema, and the APPS view is exposed through standard APPS synonym/grant administration.

Key Columns

The view projects 24 columns, several of which are directly relevant to the user's search term cef_no:

Common Use Cases and Queries

The view is typically used for admissions reporting, enquiry tracking, and troubleshooting UCAS data feeds — for example, verifying that a CEF number has been captured correctly against an applicant.

To locate an applicant by CEF number:

  • SELECT ucas_applicant_number, surname, given_names, clearing_entry_form_number, ucas_system_code FROM apps.igsbv_uc_enquiry_details WHERE clearing_entry_form_number = :cef_no;

To review all enquiries with applicant request flags:

  • SELECT ucas_applicant_number, surname, given_names, request_appl_details_ind, request_copy_appl_form_ind FROM apps.igsbv_uc_enquiry_details WHERE request_copy_appl_form_ind = 'Y';

To list enquiries lacking a matching applicant record (outer-join NULLs):

  • SELECT ucas_applicant_number, surname, clearing_entry_form_number FROM apps.igsbv_uc_enquiry_details WHERE clearing_entry_form_number IS NULL;

Because the view is read-only and joins only two IGS tables, it performs efficiently for ad-hoc queries and can be consumed by BI Publisher reports or interface programs requiring a flattened UCAS enquiry/applicant result set.