Search Results predicted_gpa




Overview
Explore in AI Chat

Overview

IGS_AD_KEY_ACAD_IND_V is a supplementary view owned by the APPS schema within the Oracle E-Business Suite Recruiting (IGS) product family. Its FND Design Data identifier is IGS.IGS_AD_KEY_ACAD_IND_V, and its documented status is VALID. The view presents admissions-related academic indicators, consolidating applicant identification, admission application context, admitted program information, and academic performance metrics into a single row per person and admission application combination.

The Oracle ETRM documentation explicitly labels this object as a "supplementary view used to simplify forms coding" and includes the vendor warning that Oracle does not recommend querying or altering data through this view, because its definition may change dramatically in subsequent minor or major releases. Consequently, it should be treated as a forms-support construct rather than a stable integration contract. It is nonetheless valid and queryable in both 12.1.1 and 12.2.2. The object is especially relevant to users searching for predicted_gpa, since PREDICTED_GPA is exposed as one of the view's primary academic indicator columns.

Underlying Base Objects

The documented ETRM metadata for this view does not enumerate referenced base objects; the dependency list is empty in the supplied excerpt. In practice, the view is defined over IGS admissions application structures, principally the admission application and applicant records (such as IGS_AD_APPLICATIONS and its associated person and academic indicator entities) that carry the predicted grade point average, academic index, and prior institution attainment data. Because the documented dependency information is absent, implementers should confirm the current definition at their patch level by inspecting DBA_VIEWS or ALL_DEPENDENCIES before relying on any column lineage. The warning to avoid direct queries reinforces treating the view as a presentation layer over forms base entities rather than as a dependable reporting interface.

Key Columns

Common Use Cases and Queries

Typical scenarios include admissions review of predicted versus recorded academic performance, institutional grade point average comparisons, and ranking analysis for a nominated program. Because the view is forms-oriented, the most defensible use is ad hoc, read-only inquiry.

  • Retrieve predicted and institutional GPAs for an applicant pool.
  • Compare first-choice unit set against the admitted unit set and program.
  • Report application and outcome status by institution.
SELECT PERSON_ID
     , ADMISSION_APPL_NUMBER
     , PROGRAM_ADMITTED
     , PREDICTED_GPA
     , INST_GRADE_POINT_AVERAGE
     , GRADE_POINT_AVERAGE
     , CORE_CURRICULUM_VALUE
  FROM APPS.IGS_AD_KEY_ACAD_IND_V
 WHERE ADM_APPL_STATUS = :p_status;

Given the documented instability warning, production integrations should replicate this logic against the underlying IGS admissions tables rather than depending on the view definition.