Search Results term_type_meaning

Overview

IGS_AV_ACAD_HISTORY_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the IGS (Student System) product family and presents the consolidated academic history of a student. The view joins education records held against a party (person) with their transcript, term, and term unit detail records, and resolves the term type lookup code into a user-facing meaning. In practice, the view exposes one row per term unit detail record — that is, per graded unit attempt within a student's academic history — along with the parent transcript and term context.

Because it spans HZ, IGS_AD, and lookup tables in a single pre-joined projection, the view is intended for reporting, inquiry forms, extracts, and integration interfaces where consumers need a flattened academic history picture without writing the join logic themselves. The TERM_TYPE_MEANING column in particular is the decoded value most frequently referenced by report authors who search for "term_type_meaning", since it avoids a separate lookup join.

Underlying Base Objects

The view text references the following base objects:

• HZ_EDUCATION (HE) — the driving table, holding the education record identified by EDUCATION_ID, with SCHOOL_PARTY_ID, STATUS, and standard WHO columns.
• HZ_PARTIES (P) — joined on PARTY_ID = HE.SCHOOL_PARTY_ID; supplies the institution party.
• IGS_AD_TRANSCRIPT (T) — joined on HE.EDUCATION_ID = T.EDUCATION_ID; supplies TRANSCRIPT_ID, TERM_TYPE, and DATE_OF_ISSUE.
• IGS_AD_TERM_DETAILS (D) — joined on T.TRANSCRIPT_ID = D.TRANSCRIPT_ID; supplies TERM_DETAILS_ID and TERM.
• IGS_LOOKUPS_VIEW (LK) — joined on T.TERM_TYPE = LK.LOOKUP_CODE with LOOKUP_TYPE = 'TERM_TYPE'; supplies MEANING, aliased as TERM_TYPE_MEANING.
• IGS_AD_TERM_UNITDTLS (E) — joined on D.TERM_DETAILS_ID = E.TERM_DETAILS_ID; supplies UNIT_DETAILS_ID, UNIT, UNIT_NAME, GRADE, and CP_EARNED.
• IGS_PE_HZ_PARTIES (PHP) — referenced by a scalar subquery to derive INSTITUTION_CODE from OSS_ORG_UNIT_CD when SCHOOL_PARTY_ID is not null.

ETRM does not document additional base objects beyond those visible in the view text. All joins are inner equi-joins except the institution code subquery, which is a correlated scalar lookup.

Key Columns

• ROW_ID — the ROWID of the HZ_EDUCATION row; a surrogate identifier, not a stable key.
• PERSON_ID — alias of HE.PARTY_ID, the student party identifier.
• EDUCATION_ID, TRANSCRIPT_ID, TERM_DETAILS_ID, UNIT_DETAILS_ID — the hierarchical identifiers linking institution, transcript, term, and unit records.
• INSTITUTION_CODE — decoded from IGS_PE_HZ_PARTIES.OSS_ORG_UNIT_CD for the school party.
• TERM_TYPE_MEANING — the decoded description of T.TERM_TYPE from IGS_LOOKUPS_VIEW; this is the human-readable term type label.
• TERM — the term code from IGS_AD_TERM_DETAILS.
• UNIT, UNIT_NAME — the unit code and its descriptive name.
• GRADE, CP_EARNED — the grade achieved and credit points earned for the unit attempt.
• DATE_OF_ISSUE — transcript issue date.
• STATUS — status of the underlying education record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from HZ_EDUCATION.

Common Use Cases and Queries

Typical uses include producing student transcripts, verifying credit point totals per term, and feeding external student record systems. Because the view presents one row per unit detail, aggregation is normally required for term or transcript level reporting.

• Retrieving a student's full academic history: SELECT person_id, term, term_type_meaning, unit, unit_name, grade, cp_earned FROM apps.igs_av_acad_history_v WHERE person_id = :p_person_id ORDER BY term, unit;
• Listing distinct term types present for a student: SELECT DISTINCT term_type_meaning FROM apps.igs_av_acad_history_v WHERE person_id = :p_person_id;
• Totalling credit points by term: SELECT term, SUM(cp_earned) FROM apps.igs_av_acad_history_v WHERE person_id = :p_person_id GROUP BY term;
• Institutional extracts filtered by institution: SELECT * FROM apps.igs_av_acad_history_v WHERE institution_code = :p_inst;

Queries should always constrain by PERSON_ID or another indexed parent identifier, since no indexes are defined on a view and the join path traverses several large IGS_AD and HZ tables.