Search Results igsbv_high_edu_unit_categories




Overview

The IGSBV_HIGH_EDU_UNIT_CATEGORIES view is a base database object owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS – Student System (Oracle Student System / Higher Education) product family. It presents a denormalized, read-only projection of the categories that are assigned to academic units within the institution's curriculum structure. In this context a "unit" is a discrete subject or module of study, and each unit may carry multiple categories (for example, disciplinary groupings, funding classifications, or reporting taxonomies), so the view returns one row per unit-to-category association.

Because the view is exposed as a read-only WITH READ ONLY construct, it is intended purely for querying, reporting, and integration extract purposes rather than for DML. It shields consumers from the join complexity of the underlying normalized tables, allowing concurrent programs, OBIEE/BI Publisher reports, and inbound/outbound interfaces to retrieve unit category information through a single, stable relational surface. The status of the object is recorded as VALID in the ETRM metadata, confirming it compiles successfully against the referenced base objects.

Underlying Base Objects

The view text is defined over three base tables. The metadata does not list these as formally documented "referenced base objects," but the view definition itself is authoritative:

  • IGS_PS_UNIT_CATEGORY_ALL (UNA) – The driving table holding the assignment of a category to a unit and version. The _ALL suffix indicates it is the multi-organization (or partitioned) form of the unit-category entity.
  • IGS_PS_UNIT_CAT (UNC) – The category definition (lookup) table supplying the descriptive text for each category.
  • IGS_PS_UNIT_VER_ALL (UNV) – The unit version table supplying the version-specific unit title.

The joins are equijoins on UNIT_CAT (UNA to UNC) and on the composite key UNIT_CD plus VERSION_NUMBER (UNA to UNV). This means a unit category row can be returned only where a matching unit-version record exists, and only where a matching category definition exists.

Key Columns

Common Use Cases and Queries

Typical uses include producing category-driven unit listings, feeding student records extracts, and validating that units in a given version carry the required classifications. Because users frequently search on unit_title, filtering or sorting by that column is common.

  • Listing all categories for a specific unit version.
  • Listing all units belonging to a particular category.
  • Finding units by title across versions.
SELECT unit_code,
       unit_version_number,
       unit_category,
       unit_title,
       unit_category_description
FROM   apps.igsbv_high_edu_unit_categories
WHERE  unit_title LIKE '%ACCOUNTING%';

SELECT unit_code, unit_title, unit_category, unit_category_description
FROM   apps.igsbv_high_edu_unit_categories
WHERE  unit_cat = :p_category
ORDER  BY unit_title;