Results for “applicant_identifier”

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

Overview

IGSFV_UC_APPLICANT_RESULTS is a full (non-incremental) view within the Oracle E-Business Suite IGS — Student System product family, specifically the UCAS (Universities and Colleges Admissions Service) integration area. Its documented description is "Full View for Applicant Examination Results," and its stated purpose is to present applicant examination and qualification results captured through the UCAS admissions interface alongside associated applicant, person, subject, and awarding-body reference data.

The view is exposed for reporting and integration. In practice, institutions use it as a stable presentation layer over the underlying transactional tables so that ad-hoc queries, BI Publisher reports, and outbound interfaces do not need to resolve the join logic between applicant results, person records, subject codes, and awarding bodies themselves. Because it is a read-only view (WITH READ ONLY), it can be queried freely without risk of modifying admissions data.

Under the broader IGS/UCAS roadmap, this object is documented as belonging to the IGS — Student System (Obsolete) component, and the ETRM entry explicitly records that it is not implemented in the current database. This is an important operational caveat: installations on 12.1.1 or 12.2.2 should verify object existence before relying on it.

Underlying Base Objects

The view text defines joins over four base objects, none of which are separately documented in the ETRM metadata for this view:

• IGS_UC_APP_RESULTS (aliased AP) — the driving table containing applicant examination results. Joined via APP_NO = FT1.APP_NO.
• IGS_UC_APPLICANTS (aliased FT1) — inner join supplying the UCAS applicant record and the OSS_PERSON_ID linkage; joined on APP_NO.
• HZ_PARTIES (aliased FT2) — outer join ((+)) providing person/party number and name.
• IGS_UC_COM_EBL_SUBJ (aliased FT3) — inner join on SUBJECT_ID supplying subject code and title.
• IGS_UC_REF_AWRDBDY (aliased FT4) — outer join on awarding body, year, and sitting supplying the awarding body name.

Because the applicant, subject, and result joins are inner, only applicant results with a matching applicant and subject row are returned; person and awarding-body data may be null due to the outer joins.

Key Columns

• APPLICANT_RESULT_IDENTIFIER — primary identifier derived from IGS_UC_APP_RESULTS.APP_RESULT_ID.
• UCAS_APPLICANT_NUMBER / ENQUIRY_NUMBER — UCAS applicant and enquiry references.
• SUBJECT_CODE / SUBJECT_TITLE — output of the search term subject_code, sourced from IGS_UC_COM_EBL_SUBJ.SUBJECT_CODE and its title.
• EXAM_LEVEL, EXAM_YEAR, SITTING, _LA:SITTING_DESC — examination classification; the sitting description is resolved through the lookup IGS_LOOKUP_VALUES:IGS_UC_SITTING.
• PREDICTED_RESULT, CLAIMED_RESULT, RESULT_IN_OFFER, EBL_RESULT, EBL_AMENDED_RESULT — the several scoring/outcome fields tracked per applicant result.
• AWARDING_BODY / AWARDING_BODY_NAME — code and resolved name of the awarding body.
• OSS_PERSON_IDENTIFIER, OSS_PERSON_NUMBER, OSS_PERSON_NAME — identity details from HZ_PARTIES.
• APPLICANT_IDENTIFIER, SUBJECT_IDENTIFIER, IMPORTED_FLAG, plus audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include reporting predicted versus claimed versus actual (EBL) results, auditing awarding-body coverage, and reconciling imported UCAS results to person records. A representative query filtering on the searched attribute:

SELECT applicant_result_identifier,
       ucas_applicant_number,
       subject_code,
       subject_title,
       exam_level,
       exam_year,
       sitting,
       predicted_result,
       claimed_result,
       ebl_result,
       awarding_body_name
  FROM igsfv_uc_applicant_results
 WHERE subject_code = :p_subject_code
   AND exam_year   = :p_year
 ORDER BY ucas_applicant_number, subject_code;

To identify recording gaps in awarding-body or person data (areas protected by outer joins):

SELECT ucas_applicant_number, subject_code, awarding_body, awarding_body_name, oss_person_name
  FROM igsfv_uc_applicant_results
 WHERE awarding_body_name IS NULL
    OR oss_person_name  IS NULL;

Before deployment, confirm availability with SELECT * FROM ALL_VIEWS WHERE VIEW_NAME = 'IGSFV_UC_APPLICANT_RESULTS'; — given the ETRM note that it is not implemented in the documented database, a NULL result indicates the object must be created or replaced by its supported successor.