Search Results govt_program_load




Overview
Explore in AI Chat

Overview

IGSBV_HIGH_ED_PROG_VERSIONS is a read-only view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It exposes program version records for higher education institutions, presenting a consolidated, denormalized projection of the underlying program version entity. The view renames a substantial number of columns from their base-table names to more descriptive business aliases—for example, COURSE_CD is surfaced as PROGRAM_CODE and COURSE_STATUS as PROGRAM_STATUS—reflecting the academic terminology used by higher education customers rather than the legacy "course" vocabulary retained in the base tables.

The entity described covers the full lifecycle and configuration of a program version, including intermission rules, financial aid indicators, supplemental examination permissions, and minimum and maximum credit point thresholds. Because it is defined WITH READ ONLY, it functions exclusively as a reporting and integration surface; DML against it is not permitted, and consumers must write to the base tables through supported APIs.

The view is particularly relevant to reporting scenarios involving program approval and accreditation, since it exposes both APPROVAL_DATE and EXTERNAL_APPROVAL_DATE alongside review and expiry dates. Users searching on the term "approval_date" typically intend to identify programs by their institutional or external approval timing.

Underlying Base Objects

The view text references a single documented source object: IGS_PS_VER_ALL. This is the "all" variant of the program version entity, which conventionally in the IGS schema unions or combines the base record and its translation (_TL) records so that descriptive attributes are returned in the session or base language. It also implies that the view inherits the _ALL semantics, meaning rows are filtered or contextualized according to the standard IGS multi-lingual and (where applicable) multi-org access conventions enforced by that object.

No additional base tables, joins, or functions are documented in the available metadata beyond IGS_PS_VER_ALL. The view therefore adds no independent business logic of its own; its principal value is column aliasing and the abstraction of the "course" naming inherited from the underlying schema. Developers tracing data lineage should expect the physical columns to reside in the program version tables beneath IGS_PS_VER_ALL. The metadata records no documented referenced base objects at the physical level, so lineage confirmation should be performed directly against the database definition.

Key Columns

The view exposes roughly sixty columns. The most significant include:

Common Use Cases and Queries

A typical use is retrieving approved program versions by approval date, which matches the "approval_date" search:

  • SELECT program_code, version_number, approval_date, external_approval_date, program_status FROM igsbv_high_ed_prog_versions WHERE approval_date >= :p_from_date ORDER BY approval_date;
  • Identifying programs pending review: filter on review_date against SYSDATE.
  • Auditing financial aid eligibility across active versions using the three financial aid columns.
  • Extracting credit point configuration for accreditation or regulatory reporting.

Because the view is read-only, it is safe for concurrent reporting use, but queries should be constrained by program_code or date ranges to avoid full scans of the underlying program version data.