Search Results igs_en_unit_set_hist




Overview
Explore in AI Chat

Overview

The IGS_EN_UNIT_SET_HIST view is a documented Oracle E-Business Suite database object owned by the APPS schema and classified under the IGS (Student System) product family. Its stated purpose is to describe the history of changes to a given unit set. In the Oracle Student System data model, a "unit set" (identified by UNIT_SET_CD) represents a defined grouping or collection of academic units, and this view exposes the temporal, versioned history of the attributes and lifecycle status of such unit sets over time.

In the context of EBS 12.1.1 and 12.2.2, the object is a reporting companion to the operational unit set definition tables. It provides a read-only, versioned perspective on how a unit set's title, category, status, and associated dates have evolved, allowing institutions to reconstruct the state of a unit set as of any point in its lifecycle. Because the view is registered as VALID in the ETRM metadata, it is treated as a supported, documented interface for querying historical unit set data rather than an internal implementation artifact.

Like many IGS views, it enforces multi-organization (operating unit) security through an ORG_ID predicate, meaning its output is filtered by the operating unit context established in the session.

Underlying Base Objects

The view text documented in the ETRM metadata defines IGS_EN_UNIT_SET_HIST as a projection over a single underlying object: IGS_EN_UNIT_SET_HIST_ALL. No other referenced base objects are documented in the available metadata. The "_ALL" suffix indicates that the base table stores history rows for all operating units, and the view applies a security filter to restrict the visible rows to the current session's operating unit.

The WHERE clause compares a derived organization value against ORG_ID, using NVL(ORG_ID, ... ) and a value decoded from USERENV('CLIENT_INFO'). This is the standard IGS multi-org row-level security pattern, where CLIENT_INFO carries the operating unit identifier and rows with a null ORG_ID are treated against a default sentinel value of -99. Practically, this means the view returns only the history records belonging to the caller's operating unit context.

The view also synthesizes a ROW_ID column from the underlying ROWID, providing a unique row identifier for each history record even though the base object already keys history entries on unit set code, version, and history dates.

Key Columns

Common Use Cases and Queries

Typical uses include auditing unit set lifecycle changes, point-in-time reporting, and reconciliation of unit set status over an academic period.

  • Full current-version history for a unit set: 
    SELECT unit_set_cd, version_number, hist_start_dt, hist_end_dt,
       hist_who, unit_set_status, title
FROM   igs_en_unit_set_hist
WHERE  unit_set_cd = :unit_set_cd
ORDER  BY version_number, hist_start_dt;
  • Point-in-time state of a unit set as of a given date: 
    SELECT unit_set_cd, unit_set_status, title, short_title
FROM   igs_en_unit_set_hist
WHERE  unit_set_cd = :unit_set_cd
AND    :as_of_date BETWEEN hist_start_dt AND NVL(hist_end_dt, :as_of_date);
  • Audit of who changed unit sets within a period: 
    SELECT unit_set_cd, version_number, hist_who, hist_start_dt
FROM   igs_en_unit_set_hist
WHERE  hist_start_dt >= :from_date
ORDER  BY hist_start_dt;

All queries return only records for the session's operating unit, as enforced by the view's ORG_ID security predicate.