Results for “coo_id”

50+ results




Overview
Explore in AI Chat

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

Overview

IGSFV_STUDENT_PROGRAM_TERMS is a read-only view within the Oracle E-Business Suite (EBS) IGS — Student System product family. In EBS 12.1.1 and 12.2.2, IGS is delivered as an obsolete, legacy module retained for backward compatibility; its schema objects persist even though most functionality has been superseded by Oracle Student Financial Planning and related higher-education products. The view presents a consolidated, denormalized picture of a student's program and term enrollment record, joining the core student program/term allocation table to descriptive reference tables so that codes are surfaced alongside their human-readable descriptions. Because IGS is obsolete, the view is documented in the ETRM but flagged as "Not implemented in this database," meaning the object may not exist in every EBS instance depending on whether the IGS schema was ever installed or later dropped.

Underlying Base Objects

Although the documented metadata lists no referenced base objects in ETRM 12.2.2, the view text explicitly identifies its driving and joined tables. The primary table is IGS_EN_SPA_TERMS (aliased SPAT), which stores student program term records keyed by TERM_RECORD_ID. It is outer- or inner-joined to a set of reference and descriptive tables:

The view is defined WITH READ ONLY, so it cannot be used for DML.

Key Columns

The view exposes over twenty columns. The most significant are:

Common Use Cases and Queries

Typical usage is reporting on a student's program and term history, student term extract feeds, and cross-referencing key program flags. A representative query:

SELECT PERSON_NUMBER, PERSON_NAME, PROGRAM_CODE, PROGRAM_TITLE, TERM_CALENDAR_TYPE_DESC, TEM_CALENDAR_START_DATE, TERM_CALENDAR_END_DATE, KEY_PROGRAM_FLAG_DESC FROM IGSFV_STUDENT_PROGRAM_TERMS WHERE PERSON_IDENTIFIER = :person_id ORDER BY TEM_CALENDAR_START_DATE;

Consultants should verify the object's existence in the target instance before relying on it, given its obsolete status and "not implemented" flag in the ETRM metadata.