Search Results igsbv_uc_qual_details




Overview
Explore in AI Chat

Overview

IGSBV_UC_QUAL_DETAILS is a base view owned by the APPS schema in the Oracle E-Business Suite environment, delivered as part of the IGS (Student System) product family. It exposes the qualifications awarded to an applicant, drawing from the UCAS qualification details captured during the admissions process. According to the ETRM 12.2.2 metadata, its status is VALID, and it is documented as the "Base View for the qualifications awarded to an applicant." The view is defined with the WITH READ ONLY clause, meaning it is intended strictly for query and reporting purposes and cannot be used as a DML target. Because it consolidates applicant qualification records with descriptive lookups from parties, awards, fields of study, and grading schemas, the view serves as a convenient reporting and integration surface for admissions and student-records functionality rather than as a transactional object. The presence of generated column aliases such as OSS_PERSON_IDENTIFIER and mapped "_LA:" flexible-address columns indicates that the view is also used to feed downstream Oracle Student System (OSS) processing and integration layers that expect renamed attributes.

Underlying Base Objects

The ETRM metadata records no explicitly documented referenced base objects, but the view text reveals the actual underlying tables. The driving table is IGS_UC_QUAL_DETS (aliased QU), which stores the applicant's qualification detail records, including exam level, subject, year, sitting, awarding body, grading schema, and predicted, approved, and claimed results. Four outer-joined lookup tables enrich these records: HZ_PARTIES (FT1) on PARTY_ID supplies party number and party name; IGS_PS_AWD (FT2) on AWARD_CD supplies the award title corresponding to the exam level; IGS_PS_FLD_OF_STUDY_ALL (FT3) on FIELD_OF_STUDY supplies the subject description; and IGS_AS_GRD_SCH_GRADE (FT4) on the combination of GRADING_SCHEMA_CD, VERSION_NUMBER, and GRADE supplies the full grade name and rank. All joins are outer joins marked with (+), ensuring qualification rows are retained even when lookup values are absent. The view therefore behaves as a denormalized reporting projection over one primary admissions table plus four descriptive lookups.

Key Columns

The user search term "exam_level_code" maps directly to the view column EXAM_LEVEL_CODE, which is sourced from QU.EXAM_LEVEL and corresponds to the award code joined to IGS_PS_AWD. Its descriptive counterpart EXAM_LEVEL_TITLE is derived from FT2.AWARD_TITLE. Other identifier columns include QUAL_DETAILS_IDENTIFIER (the qualification detail primary key), OSS_PERSON_IDENTIFIER (person identifier), and OSS_PERSON_NUMBER and OSS_PERSON_NAME from HZ_PARTIES. Qualification attributes include SUBJECT_CODE and its description SUBJECT_CODE_DESC, YEAR, SITTING, and the flexfield-generated _LA:SITTING_DESC. Result-related columns include PREDICTED_RESULT, APPROVED_RESULT, CLAIMED_RESULT, APPROVED_RESULT_DESCRIPTION, APPROVED_RESULT_SCORE (from FT4.RANK), and UCAS_TARIFF. Additional fields cover AWARDING_BODY_CODE, GRADING_SCHEMA_CODE, VERSION_NUMBER, IMPORTED_FLAG, IMPORTED_DATE, and the standard audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include admissions evaluation reports, UCAS import verification, tariff-point calculations, and extracts feeding external student systems. A frequent query filters by exam level and person, for example:

  • SELECT EXAM_LEVEL_CODE, EXAM_LEVEL_TITLE, SUBJECT_CODE_DESC, YEAR, APPROVED_RESULT, APPROVED_RESULT_SCORE FROM IGSBV_UC_QUAL_DETAILS WHERE EXAM_LEVEL_CODE = :exam_level AND OSS_PERSON_IDENTIFIER = :person_id;
  • Reporting awarded qualifications by awarding body: SELECT AWARDING_BODY_CODE, COUNT(*) FROM IGSBV_UC_QUAL_DETAILS GROUP BY AWARDING_BODY_CODE;
  • Reviewing imported records: SELECT QUAL_DETAILS_IDENTIFIER, IMPORTED_DATE FROM IGSBV_UC_QUAL_DETAILS WHERE IMPORTED_FLAG = 'Y';
  • Auditing grade mapping: SELECT EXAM_LEVEL_CODE, APPROVED_RESULT, APPROVED_RESULT_DESCRIPTION FROM IGSBV_UC_QUAL_DETAILS WHERE GRADING_SCHEMA_CODE IS NOT NULL;

Because the view is read-only and the lookups are outer-joined, queries remain safe for reporting and will not fail when descriptive data is missing. Note that the view should not be used for inserts or updates.