Search Results resp_org_unit_code




Overview

The IGSFV_HIGH_EDU_PRG_GROUPS view is a read-only reporting object owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It exposes groupings of academic programs — referred to in the underlying data model as course groups — that are used for a variety of functional purposes across the student information system. Program groups are commonly leveraged to organize related programs for admissions processing, curriculum planning, enrollment rules, fee assessment, and self-service catalog presentation.

The view is defined as a full view (WITH READ ONLY), meaning it is intended strictly for query and reporting access. No DML operations may be performed directly against it. Its primary role is to provide a denormalized, human-readable representation of program group data, joining internal code values to their descriptive counterparts so that reports, concurrent programs, and integration extracts can present meaningful labels rather than raw identifier codes. This makes it a convenient single-source object for reporting tools such as Oracle Reports, BI Publisher, and OBIEE, as well as for inbound SQL queries from external systems.

Underlying Base Objects

The view is defined over three base objects joined by the following relationships:

  • IGS_PS_GRP_ALL (aliased GRA) — the primary driving table containing the program group records, including group code, description, responsible organizational unit, group type, and the closed indicator.
  • IGS_PS_GRP_TYPE (aliased GRT) — joined on COURSE_GROUP_TYPE to supply the descriptive text for each program group type.
  • HZ_PARTIES (aliased PA) — outer-joined on RESPONSIBLE_ORG_UNIT_CD = PARTY_NUMBER, constrained to active parties (STATUS = 'A'), to resolve the responsible organizational unit into a party name.

The join to HZ_PARTIES is an outer join, meaning program group rows will still be returned even when no matching active party exists for the responsible organizational unit. The join predicates are applied within the WHERE clause using Oracle's traditional outer-join syntax, consistent with 11i-era coding conventions carried forward into EBS 12.1.1 and 12.2.2.

Key Columns

Common Use Cases and Queries

Typical use cases include listing available program groups for reporting, validating group membership prior to admissions or enrollment processing, and driving self-service catalog displays.

Retrieve all active (non-closed) program groups:

  • SELECT program_group_code, program_group_description, program_group_type_description FROM igsfv_high_edu_prg_groups WHERE program_closed_indicator = 'N' ORDER BY program_group_description;

Locate a group by its description:

  • SELECT program_group_code, program_group_description FROM igsfv_high_edu_prg_groups WHERE UPPER(program_group_description) LIKE '%UNDERGRAD%';

Because the view is read-only and drives off IGS_PS_GRP_ALL, it should be treated as a reporting convenience object rather than a transactional source.