Results for “degree_attempted”

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

Overview

IGSBV_ACADEMIC_HISTORIES is a read-only view in the Oracle E-Business Suite IGS (Student System) product family. It consolidates a person's academic history into a single denormalized result set, joining external education records held against a party to the self-reported and internally tracked academic history maintained by the institution. The view presents the institution attended, the type of school, declared course major, degree received, degree attempted, attendance dates, and a broad set of grade-point and credit aggregates that support transcript evaluation and admissions processing.

In ETRM 12.2.2 this object is documented as obsolete for the IGS Student System, and the implementation metadata explicitly states that it is not implemented in the reference database. Consequently, the view should be treated as a legacy reporting artifact. Where it does exist in a customer instance, it functions as an integration and reporting surface rather than a transactional entity — no DML is possible, as the definition terminates in a WITH READ ONLY clause. The view is relevant to the "degree_received" search term because that attribute is exposed directly as a projected column.

Underlying Base Objects

The ETRM record lists no formally documented base objects, but the view text identifies the sources unambiguously. Three tables are referenced:

• IGS_AD_HZ_ACAD_HIST (aliased ACH) — the primary academic history table, supplying current institution, degree attempted, comments, planned completion date, and the recalculated and self-reported credit, GPA, and ranking measures.
• HZ_EDUCATION (aliased HZE) — the education record, supplying type of school, course major, degree received, attendance start and last dates, the school party identifier, and the education identifier.
• HZ_PARTIES (aliased HP) — the party registry, supplying the school attended name via PARTY_NAME.

The join condition is ACH.EDUCATION_ID = HZE.EDUCATION_ID, with HZE.SCHOOL_PARTY_ID = HP.PARTY_ID outer-joined, so records without a resolvable school party still return rows with a null school name.

Key Columns

• DEGREE_RECEIVED — the degree conferred by the external institution; the primary attribute for credential verification and the target of the user's search.
• DEGREE_ATTEMPTED and PROGRAM_TYPE_ATTEMPTED — the qualification the applicant pursued, reported through the institution's academic history record.
• SCHOOL_ATTENDED_NAME, TYPE_OF_SCHOOL, COURSE_MAJOR — descriptive attributes of the awarding institution and field of study.
• START_DATE_ATTENDED and LAST_DATE_ATTENDED — the attendance window used for period-based evaluation.
• RECALC_* columns (total credit points attempted and earned, total unit grade points, GPA units attempted, institutional GPA) — institutional recomputation of academic performance.
• SELFREP_* columns — applicant-declared equivalents, including weighted GPA, rank in class, weighted rank, and class size.
• TRANSCRIPT_REQUIRED, CURRENT_INST, PLANNED_COMPLETION_DATE, COMMENTS — workflow and admissions flags.
• HZ_ACAD_HIST_ID, EDUCATION_ID, PERSON_ID, and the standard WHO columns — keys and audit attributes.

Common Use Cases and Queries

Typical usage includes admissions evaluation, prior-learning assessment, and generation of academic history extracts for downstream reporting. A representative query returning the degree received for a given person:

• SELECT school_attended_name, type_of_school, course_major, degree_received, degree_attempted, last_date_attended FROM igsbv_academic_histories WHERE person_id = :p_person_id ORDER BY last_date_attended DESC;
• SELECT degree_received, COUNT(*) FROM igsbv_academic_histories WHERE degree_received IS NOT NULL GROUP BY degree_received ORDER BY 2 DESC;
• SELECT person_id, school_attended_name, recalc_inst_gpa, selfrep_inst_gpa FROM igsbv_academic_histories WHERE current_inst = 'Y';

Because the object is obsolete and not implemented in the reference environment, implementations should validate its existence before use and plan migration to the current Student System academic history entities.