Search Results igsbv_prog_concentrations




Overview
Explore in AI Chat

Overview

The view IGSBV_PROG_CONCENTRATIONS belongs to the Oracle E-Business Suite IGS – Student System product family, a module now classified as obsolete within the ETRM (E-Business Suite Technical Reference Manual) documentation set for releases 12.1.1 and 12.2.2. The view exposes program concentration data, where a concentration represents a logical sub-grouping of a program such as a Major, Minor, Stream, or Strand. Because completion of a concentration is typically governed by rules maintained through the Student System Rules sub-system, this view serves as a reporting and integration layer over the underlying unit-set definitions. It is defined WITH READ ONLY, meaning consumers cannot perform DML through it.

Underlying Base Objects

The documented view text selects exclusively from the base table IGS_EN_UNIT_SET_ALL:

  • IGS_EN_UNIT_SET_ALL — the enrolment unit-set table that stores concentration (unit-set) definitions and their translated descriptive attributes.

The ETRM metadata indicates the view is not implemented in this database, and no referenced base objects are separately documented beyond the source table shown in the view text. Consequently, the view should be treated as a documented data model artifact rather than an assured runtime object in every environment.

Key Columns

The view re-labels several source columns to improve readability. Notable columns include:

Common Use Cases and Queries

Typical uses include extracting the catalogue of concentrations for a program, filtering by category, and validating effective dates. A representative query filtered on category is:

SELECT UNIT_SET_CODE,
       UNIT_SET_CATEGORY,
       TITLE,
       UNIT_SET_STATUS,
       START_DATE,
       END_DATE
FROM   IGSBV_PROG_CONCENTRATIONS
WHERE  UNIT_SET_CATEGORY = :p_unit_set_category
AND    TRUNC(SYSDATE) BETWEEN START_DATE
                          AND NVL(END_DATE, TRUNC(SYSDATE));

Integrations commonly join this view to program and rule entities to reconcile which concentrations apply to a given student's enrolment. Because the object is read-only and, per the metadata, not implemented in the reference database, developers should confirm availability in the target instance before relying on it in production reports.