Search Results fee_payer_code




Overview
Explore in AI Chat

Overview

IGSFV_UC_APPLICANTS is a full view owned by the APPS schema within the IGS (Student System) product of Oracle E-Business Suite. In ETRM 12.2.2 it is documented with a status of VALID and is described as the "Full View for UCAS Applicant Details." Its purpose is to expose, in a single denormalized result set, the attributes captured by the Oracle Student System for applicants received through UCAS (the UK Universities and Colleges Admissions Service) and similar admissions routes. Rather than forcing report authors and integrators to join several normalized applicant tables, the view maps internal column names to recognizable UCAS-oriented aliases, making it suitable for operational reporting, extracts, and inbound/outbound integration with admissions systems.

The view behaves identically in Oracle EBS 12.1.1 and 12.2.2 in terms of its column list and semantics; differences between the releases lie in the underlying table definitions and patching level rather than in the view contract itself. Note that the view name carries the "FV" (full view) prefix convention common in the IGS data model, indicating an uncompressed, all-columns projection.

Underlying Base Objects

The ETRM metadata for this object records no documented referenced base objects. Based on the view text and standard IGS schema conventions, the projection is drawn from the UCAS applicant base entity in the IGS data model — the IGS_UC_APPLICANTS table (and its associated address, qualification, and reply detail tables in the fuller implementation). The column aliasing pattern (for example, AP.APP_ID APPLICANT_ID, AP.ROUTE_B ROUTE_B_FLAG) confirms a single driving base table aliased as AP, with each physical column renamed to a business-friendly label.

Because the metadata records no other documented base objects, treat the view as a thin wrapper over the applicant table. Where the deployed view joins additional tables (personal details, domicile, qualifications), those joins are implicit and should be verified against the APPS.IGSFV_UC_APPLICANTS view text in the target instance before relying on them.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting on applicants by admission route, reconciling UCAS submissions, driving clearing and confirmation processes, and extracting applicant data for downstream systems. Because Route B is a distinct admissions pathway, queries filtering on the route flag are common.

  • Applicants on the Route B path: 
    SELECT applicant_id, ucas_applicant_number, applicant_status
FROM   apps.igsfv_uc_applicants
WHERE  route_b_flag = 'Y';
  • Electronic applicants with their status and fee code: 
    SELECT ucas_applicant_number, applicant_status, fee_payer_code
FROM   apps.igsfv_uc_applicants
WHERE  electronic_appl_system_flag = 'Y';
  • Withdrawn or clearing applicants: 
    SELECT applicant_id, withdrawn_date, release_to_clearing_reason
FROM   apps.igsfv_uc_applicants
WHERE  withdrawn = 'Y';

Always apply the standard EBS security context and confirm the deployed view text, since the documented ETRM metadata for this object does not enumerate all base objects.