Search Results oss_person_name




Overview
Explore in AI Chat

Overview

The view APPS.IGSFV_UC_APPLICANT_REFEREES is a read-only database object within the IGS — Student System product family of Oracle E-Business Suite, available in R12.1.1 and 12.2.2. It presents full applicant referee detail sourced from the UCAS (Universities and Colleges Admissions Service) applicant integration tables. In the recruitment and admissions lifecycle, referee data captures the academic or professional references supplied by an applicant at the point of application, including the referee's name, position, establishment, contact details, and supporting statement.

The view is classified as a "Full View," meaning it exposes the complete column set of the underlying referee entity rather than a restricted or summary projection. It is primarily consumed for reporting, inquiry, and integration purposes: admissions staff, MI (management information) reporting, and downstream extracts use it to associate referee records with the corresponding OSS person identifier (OSS_PERSON_ID) and party information. The user search term oss_person_id corresponds directly to the OSS_PERSON_IDENTIFIER and OSS_PERSON_NUMBER columns exposed here, which bridge the applicant referee record to the Oracle Trading Community Architecture (TCA) party model via HZ_PARTIES.

Underlying Base Objects

The view is defined over three base objects joined within the APPS schema. The driving table is IGS_UC_APP_REFEREES (aliased AP), which stores the individual referee records keyed by application number. It is joined to IGS_UC_APPLICANTS (aliased FT1) on AP.APP_NO = FT1.APP_NO, which supplies the applicant context and the OSS person identifier. The applicant record is in turn outer-joined to HZ_PARTIES (aliased FT2) on FT1.OSS_PERSON_ID = FT2.PARTY_ID (+), resolving party number and party name from the TCA registry. The outer join ensures referee rows are retained even where no matching party record exists. The view is defined WITH READ ONLY, so no DML is permitted against it. Note that ETRM 12.2.2 documentation records no explicit base-object listing, but the view text embedded in the metadata identifies these three sources unambiguously.

Key Columns

  • UCAS_APPLICANT_NUMBER — The UCAS application number, the principal join key across applicant and referee records.
  • REFEREE_NAME, REFEREE_POST — The referee's name and professional position.
  • ESTABLISHMENT_NAME, ADDRESS1–ADDRESS4, TELEPHONE, FAX, EMAIL — Contact and establishment details for the referee.
  • STATEMENT — The referee's supporting statement or comment on the applicant.
  • OSS_PERSON_IDENTIFIER — The OSS person identifier sourced from IGS_UC_APPLICANTS; this is the column surfaced when users search on oss_person_id.
  • OSS_PERSON_NUMBER, OSS_PERSON_NAME — Party number and party name resolved from HZ_PARTIES.
  • PREDICTED_GRADES — Predicted academic grades recorded against the referee entry.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns.

Common Use Cases and Queries

The view is typically queried to list referees for a given applicant or to correlate referee records with TCA party identifiers for integration and reconciliation. A representative query follows:

  • SELECT uc_ucas_applicant_number, referee_name, referee_post, oss_person_identifier, oss_person_number, oss_person_name FROM igsfv_uc_applicant_referees WHERE oss_person_identifier = :p_person_id;
  • SELECT referee_name, establishment_name, email FROM igsfv_uc_applicant_referees WHERE ucas_applicant_number = :p_app_no;
  • Reconciliation extracts comparing OSS_PERSON_IDENTIFIER against OSS_PERSON_NUMBER to detect applicants whose party record has not yet been created (nulls arising from the outer join to HZ_PARTIES).

Because the view is read-only and appears valid in both 12.1.1 and 12.2.2, it is a stable foundation for custom admissions reports and interface programs that require referee detail linked to the OSS person model.