Search Results igs_ad_trmdt_int

Overview

The view IGS_AD_TRMDT_INT is a critical data object within the Oracle E-Business Suite (EBS) Student System (IGS), specifically designed for the Admissions module. It serves as an interface view, providing a structured representation of term-level academic details imported from external systems or entered for data migration and integration purposes. Its primary role is to facilitate the processing of transcript data, acting as a staging area where term details (such as grades and credits) are held before being validated and posted to core transactional tables. The view is built directly on the underlying interface table IGS_AD_TRMDT_INT_ALL, indicating it is a multi-organization access control (MOAC) enabled object, filtered by the operating unit's ORG_ID. The metadata note "Not implemented in this database" suggests this view may be part of a standard delivery that requires specific implementation steps to be activated for a given installation.

Key Information Stored

The view encapsulates detailed academic performance for a specific term. Key columns include identifiers like TERM_DETAILS_ID and the associated INTERFACE_TRANSCRIPT_ID, which links to a parent transcript record. Academic metrics are stored in TOTAL_CP_ATTEMPTED (total credit points attempted), TOTAL_CP_EARNED (credit points successfully earned), TOTAL_UNIT_GP (total grade points), TOTAL_GPA_UNITS (units used in GPA calculation), and the calculated GPA. The temporal scope of the term is defined by START_DATE and END_DATE. Critical for interface processing are the STATUS and ERROR_CODE columns, which track the success or failure of data validation and integration. The MATCH_IND and DUP_TERM_DTLS_ID columns are likely used for deduplication and matching against existing student records. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, etc.) and program columns (REQUEST_ID, PROGRAM_ID) are also present.

Common Use Cases and Queries

The primary use case is the batch processing of external academic transcripts, often via a concurrent request. A typical operational query would check for pending interface records that require processing or have errored out. For example:

• To identify term details awaiting processing: SELECT * FROM IGS_AD_TRMDT_INT WHERE STATUS = 'PENDING' AND ORG_ID = :org_id;
• To analyze errors in a failed transcript load: SELECT INTERFACE_TRANSCRIPT_ID, TERM, ERROR_CODE FROM IGS_AD_TRMDT_INT WHERE STATUS = 'ERROR';
• For reporting on imported GPA data before final posting: SELECT TERM, GPA, TOTAL_CP_EARNED FROM IGS_AD_TRMDT_INT WHERE INTERFACE_TRANSCRIPT_ID = :transcript_id ORDER BY TERM;

These records are typically consumed by a dedicated student system interface program that validates data against institutional rules (like valid terms and grade scales) and then creates records in the core student academic history tables.

Related Objects

Based on the column structure and naming conventions, this view has direct and fundamental relationships with other IGS interface and base tables.

• IGS_AD_TRMDT_INT_ALL: This is the base table upon which the view is built. The view selects all columns from this table, and the relationship is inherent.
• IGS_AD_TRANSCRIPT_INT: A closely related interface table for the parent transcript header. The INTERFACE_TRANSCRIPT_ID column in IGS_AD_TRMDT_INT is a foreign key to this object, linking term details to their corresponding transcript.
• IGS_AD_STD_TERM_DTLS: This is the likely target transactional table where successfully processed term detail records are ultimately stored. The DUP_TERM_DTLS_ID column may store the ID of a matched existing record in this table, while TERM_DETAILS_ID may be populated with a new ID from this table upon successful interface processing.