Search Results igs_ad_transcript




Overview

The IGS_AD_TRANSCRIPT table is a core data object within the Oracle E-Business Suite's now-obsolete Student System (IGS) module. Its primary function is to serve as the central repository for storing academic transcript details for applicants or students. A transcript, in this context, represents a formal record of an individual's prior academic performance, typically from a secondary or post-secondary institution, which is evaluated during the admissions process. The table's design facilitates the tracking of this critical information, linking it to specific education records and grading systems. Notably, the provided ETRM metadata explicitly states this table is "Not implemented in this database," indicating it may have been part of a legacy or unimplemented extension of the IGS module in many deployments.

Key Information Stored

While the full column list is not provided in the metadata, the primary and foreign key relationships reveal the essential data elements. The table is uniquely identified by the TRANSCRIPT_ID column, which serves as the primary key. Crucially, it stores foreign keys that establish vital relationships with other entities in the system. The EDUCATION_ID column links each transcript to a specific education record in the HZ_EDUCATION table (part of Oracle's Trading Community Architecture), anchoring the academic data to a person and institution. Furthermore, columns like TRANSCRIPT_SOURCE, ENTERED_GS_ID, and CONV_GS_ID reference the IGS_AD_CODE_CLASSES table, suggesting the table stores metadata about the transcript's origin and the grading scales used for the original entry and any subsequent conversion to a standard scale.

Common Use Cases and Queries

The primary use case for this table is supporting the evaluation of applicant credentials. Admissions officers would query this table to retrieve and assess an applicant's prior academic history. Common reporting and data retrieval patterns would involve joining to related tables for a complete view. For instance, a query to list all transcripts for an applicant, including the institution name from the linked education record, would be fundamental. While specific column names are limited, a typical SQL pattern would be:

  • Retrieving transcript details for a specific education record: SELECT * FROM IGS_AD_TRANSCRIPT WHERE EDUCATION_ID = <value>;
  • Joining with HZ_EDUCATION to get person and institution context: SELECT t.*, e.school, e.degree FROM IGS_AD_TRANSCRIPT t, HZ_EDUCATION e WHERE t.EDUCATION_ID = e.EDUCATION_ID;

Related Objects

The IGS_AD_TRANSCRIPT table sits at the center of a small network of related objects, primarily defined by its foreign key constraints. It is a parent table to IGS_AD_TERM_DETAILS, which likely stores granular, term-by-term academic performance data linked back to a master transcript record via the TRANSCRIPT_ID. As a child table, it depends heavily on HZ_EDUCATION for core education record data and on the code lookup table IGS_AD_CODE_CLASSES for standardized values related to the transcript source and grading scales. This structure ensures referential integrity and allows transcript data to be consistently categorized and linked to the broader applicant and person data model within Oracle EBS.