Results for “igs_ad_term_details”

50+ results




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

Overview

IGS_AD_TERM_DETAILS is a table in the IGS (Student System) product family of Oracle E-Business Suite, owned by the IGS schema. Per the ETRM documentation, its stated purpose is simply to "hold term details," and it functions as the academic term-level record within a student's transcript. Each row represents one term of enrollment tied to a parent transcript, capturing the term code, its start and end dates, and aggregated academic performance metrics such as attempted credits, earned credits, grade points, GPA units, and grade point average.

Under the heuristic Data Vault classification supplied in the metadata, this object is described as satellite-leaning. As a modeling suggestion, this reflects that it hangs off a parent entity (IGS_AD_TRANSCRIPT) via the TRANSCRIPT_ID foreign key and carries descriptive, term-specific attributes rather than serving as a pure enterprise hub or a link resolving many-to-many relationships. In an EBS Student System implementation, it is a transactional/detail table underpinning transcript generation, GPA computation, and academic progress reporting.

Key Information Stored

The documented physical schema for 12.1.1 lists nineteen columns. The most significant are summarized below.

The presence of two unique indexes on TERM_DETAILS_ID and on (TERM, END_DATE, START_DATE) confirms the surrogate-versus-business-key split: the ID is the technical identifier, while the term/date triad enforces uniqueness on the natural business key.

Common Use Cases and Queries

Typical uses include retrieving a student's term-by-term academic record, recomputing or validating term GPA, and feeding transcript and academic-standing reports. Stored procedures and concurrent programs populate the aggregate columns, which are then read for reporting rather than recalculated on the fly.

A transcript-driven query joins to the parent table:

  • SELECT t.TERM, t.START_DATE, t.END_DATE, t.TOTAL_CP_EARNED, t.GPA FROM IGS.IGS_AD_TERM_DETAILS t WHERE t.TRANSCRIPT_ID = :p_transcript_id ORDER BY t.START_DATE;

A term lookup by business key uses the U2 index:

  • SELECT * FROM IGS.IGS_AD_TERM_DETAILS WHERE TERM = :p_term AND START_DATE = :p_start AND END_DATE = :p_end;

Interface and staging tables (for example IGS_AD_TRMDT_INT) are commonly used to bulk-load or update these rows during transcript import.

Related Objects

  • IGS_AD_TRANSCRIPT — parent entity; joined via IGS_AD_TERM_DETAILS.TRANSCRIPT_ID = IGS_AD_TRANSCRIPT.TRANSCRIPT_ID.
  • IGS_AD_TERM_UNITDTLS — child holding term unit details; joined via IGS_AD_TERM_UNITDTLS.TERM_DETAILS_ID = IGS_AD_TERM_DETAILS.TERM_DETAILS_ID.
  • IGS_AD_TUNDT_INT — interface table referencing TERM_DETAILS_ID for unit-detail imports.
  • IGS_AD_TRMDT_INT — interface table referencing TERM_DETAILS_ID for term-detail loads.
  • IGS_AD_TERM_DETAILS_PK / _U1 / _U2 — primary and unique key constraints enforcing identity and the (TERM, START_DATE, END_DATE) business key.