Search Results responsible_org_unit_cd




Overview
Explore in AI Chat

Overview

IGS_EN_UNIT_SET_HIST_V is a reporting and integration view within the Oracle E-Business Suite Student System (IGS) product family. It belongs to the Enrollment (IGS_EN) schema area and specifically addresses the historical change tracking of unit sets — the academic grouping constructs that bundle individual units (courses or modules) into named, versioned structures such as programmes, pathways, or award schemes. The view merges unit set history records with the corresponding current unit set definitions so that every column value can be reconstructed for any point in time, from the earliest recorded history period through to the present day. Each row represents a complete set of column values valid over a defined historical period rather than a single change event.

Within Oracle EBS 12.1.1 and 12.2.2, the IGS product is documented as obsolete, meaning the view is retained for backward compatibility and reference rather than active development. It is exposed under the APPS schema and is queried with the standard _V reporting convention. The view is significant because it solves a common academic reporting problem: institutions must be able to report on the state of a unit set as it existed at a given effective date, not merely its current configuration.

Underlying Base Objects

The view is defined over history and current tables whose physical names are not enumerated in the documented base object list, but the view text reveals the alias USH1 (the unit set history table, IGS_EN_UNIT_SET_HIST or equivalent) as the driving source, and US1 (the current unit set table) as the fallback source. Three supporting objects are referenced directly in the view definition:

  • IGS_AU_GEN_004 — an audit package exposing the function AUDP_GET_USH_COL, which retrieves a named column value from the unit set history for a given unit set code, version number, and history end date.
  • IGS_GE_DATE — the general date utility package, exposing IGSDATE, used to convert stored values into proper date datatypes.
  • USH1 and US1 — the history and current unit set tables joined on the unit set code and version number.

The view applies a layered NVL resolution pattern: the history table column is used when populated, otherwise the audit function result is used, otherwise the current table value is substituted.

Key Columns

The primary searchable column is UNIT_SET_CD, the unique code identifying the unit set. It is paired with VERSION_NUMBER, allowing multiple versions of the same unit set to coexist historically. The date envelope columns HIST_START_DT and HIST_END_DT define the validity window of each row, while HIST_WHO records the user or process that created the history entry.

Descriptive attributes exposed include TITLE, SHORT_TITLE, ABBREVIATION, UNIT_SET_STATUS, and UNIT_SET_CAT, each resolved through the NVL/SUBSTR fallback chain. Date-bearing attributes include START_DT, REVIEW_DT, EXPIRY_DT, and END_DT, passed through IGS_GE_DATE.IGSDATE. Text columns are truncated to their DDL lengths — for example, TITLE to 90 characters, SHORT_TITLE to 40, ABBREVIATION to 20 — which is important when comparing view output against base table values.

Common Use Cases and Queries

The view is typically used to build point-in-time academic reports, to audit unit set changes across academic years, and to feed external student record systems requiring effective-dated programme structures. A representative query filters on the highly selective UNIT_SET_CD column:

  • SELECT unit_set_cd, version_number, hist_start_dt, hist_end_dt, unit_set_status, title FROM igs_en_unit_set_hist_v WHERE unit_set_cd = :p_unit_set_cd ORDER BY version_number, hist_start_dt;
  • SELECT unit_set_cd, version_number, title FROM igs_en_unit_set_hist_v WHERE SYSDATE BETWEEN hist_start_dt AND NVL(hist_end_dt, SYSDATE);

Because the view is documented as obsolete and not implemented in the delivery database, administrators should confirm its availability in their specific instance before relying on it in custom concurrent programs or OAF pages. Where present, it remains the cleanest supported mechanism for effective-dated unit set reporting in EBS 12.1.1 and 12.2.2.