Search Results igs_ad_transcript_v




Overview
Explore in AI Chat

Overview

The IGS_AD_TRANSCRIPT_V view is a denormalized presentation object owned by the APPS schema within the Oracle EBS Student System (IGS) product family. It consolidates transcript header information for admissions and academic records processing, exposing both coded values and their human-readable meanings in a single row shape. Its principal role is to support reporting, extracts, and integrations that require transcript data without repeatedly joining lookup and code-class tables. For users searching on transcript_source_code, the view is directly relevant because it resolves the internal source identifier (TRANSSCRIPT_SOURCE) against the code classes table and surfaces the friendly name as TRANSCRIPT_SOURCE_CODE. This eliminates the need for consumers to know that the underlying value is a CODE_ID referencing IGS_AD_CODE_CLASSES.

Underlying Base Objects

Per the ETRM documentation, the view is defined over the following objects:

  • IGS_AD_TRANSCRIPT — alias T; the driving base table holding the transcript record itself.
  • IGS_LOOKUPS_VIEW — aliases L1, L2, and L3; used to decode lookup codes for TRANSCRIPT_STATUS, TERM_TYPE, and TRANSCRIPT_TYPE respectively.
  • IGS_AD_CODE_CLASSES — aliases CC1, CC2, and CC3; used to resolve code identifiers for the entered and converted grading scales and for the transcript source.

All joins are simple equality predicates. STATUS, TERM_TYPE, and TRANSCRIPT_TYPE are matched against IGS_LOOKUPS_VIEW using their respective LOOKUP_TYPE discriminators ('TRANSCRIPT_STATUS', 'TERM_TYPE', 'TRANSCRIPT_TYPE'). The three IGS_AD_CODE_CLASSES joins resolve CODE_ID values for ENTERED_GS_ID, CONV_GS_ID, and TRANSCRIPT_SOURCE. The ETRM metadata records no referenced base objects explicitly, but the view text above establishes these relationships.

Key Columns

Common Use Cases and Queries

Typical uses include transcript verification reports, applicant screening extracts, and inbound/outbound integration feeds where decoded values are required. A query filtering by source code is straightforward:

  • SELECT transcript_id, education_id, transcript_source_code, transcript_type_meaning FROM igs_ad_transcript_v WHERE transcript_source_code = :source;
  • SELECT transcript_id, transcript_status_meaning, date_of_receipt, entered_gpa FROM igs_ad_transcript_v WHERE education_id = :education_id;
  • Joining back to IGS_AD_TRANSCRIPT on TRANSCRIPT_ID when additional unexposed columns are needed.

Because the view already performs all lookup and code-class resolution, it is the preferred access path for reporting layers and external interfaces over the raw base table.