Search Results owner_ou_start_dt




Overview
Explore in AI Chat

Overview

IGS_PS_UNIT_VER is an Oracle E-Business Suite view owned by the APPS schema and defined over the Student System (IGS) product family, specifically the Postsecondary/Student Records module. It presents versioned academic unit (course) definitions, exposing one row per combination of unit code, version number, and start date. Each row describes the attributes of an academic unit as of a particular version, including its title, unit level, credit point scheme, enrollment constraints, workflow and financial aid flags, and audit columns.

In reporting and integration terms, the view functions as a denormalized read layer over the underlying unit-version entity. It allows external systems, concurrent programs, and custom reports to query unit version data without navigating the normalized set of base tables. Because many attributes are version-effective-dated (START_DT, REVIEW_DT, EXPIRY_DT, END_DT), the view is commonly used to determine which unit version was in force on a given date, and to reconcile unit definitions against enrollment, offering, and assessment data.

Underlying Base Objects

The ETRM metadata for this object does not document any referenced base objects, so the view is treated as an opaque projection. The column set, however, is consistent with a SELECT over the unit version entity within the IGS schema (for example IGS_PS_UNIT_VER), joined in turn to organization and curriculum context. The presence of ORG_ID indicates multi-organization (business unit / operating unit) filtering, and columns such as OWNER_ORG_UNIT_CD and OWNER_OU_START_DT reflect a foreign key to an owning organizational unit version rather than to a simple lookup.

The ROWID is exposed as ROW_ID, confirming that the view is a one-to-one projection of a row in a base table rather than an aggregation. Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are surfaced directly, which is typical of a view that mirrors its base table with minimal transformation.

Key Columns

Common Use Cases and Queries

Typical uses include determining the current or as-of-date owner of a unit, generating catalog or unit-specification reports, and feeding enrollment or offering processes that require version-effective unit attributes.

Resolving the owning organization unit as of the version start date:

  • SELECT unit_cd, version_number, start_dt, owner_org_unit_cd, owner_ou_start_dt FROM apps.igs_ps_unit_ver WHERE unit_cd = :unit_cd AND :as_of_date BETWEEN start_dt AND NVL(end_dt, :as_of_date);

Listing active units for an organization:

  • SELECT unit_cd, title, unit_status FROM apps.igs_ps_unit_ver WHERE org_id = :org_id AND unit_status = 'ACTIVE' ORDER BY unit_cd;

Enrollment capacity review:

  • SELECT unit_cd, version_number, enrollment_minimum, enrollment_maximum, enrollment_expected FROM apps.igs_ps_unit_ver WHERE TRUNC(SYSDATE) BETWEEN start_dt AND NVL(end_dt, SYSDATE);

Because of the versioned key and the absence of documented base objects, queries should always constrain UNIT_CD and an effective date range to avoid returning multiple historical versions of the same unit.