Search Results prog_grp_type_closed_indicator

Overview

APPS.IGSBV_HIGH_EDU_PRG_GRP_TYPES is a read-only Oracle E-Business Suite view belonging to the Oracle Student System (formerly Oracle Higher Education) product family, exposed under the APPS schema. The view presents the set of valid program group types used to classify and group academic programs of study. In the Oracle Student System data model, a "program group type" is the classification entity that allows institutions to organise programs into logical categories — for example, undergraduate, postgraduate, research, or faculty-specific groupings — so that enrolment, admissions, and reporting processes can be segmented consistently.

The object is a "BV" (Business View) style construct, meaning it is intended primarily for reporting, integration, and lookup consumption rather than transaction processing. Because it is defined WITH READ ONLY, it cannot be used as a DML target; it functions purely as a query surface so that downstream reports, extracts, and interfaces can resolve a program group type code to its human-readable description and status. The view is commonly surfaced through Oracle Forms (the 'S_'-prefixed lookup hint in the definition) and through BI Publisher/OBIEE reporting against the APPS schema.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single base table: IGS_PS_GRP_TYPE, aliased as GR. No other base objects are documented as referenced. The relationship is a straightforward one-to-one projection: each row in IGS_PS_GRP_TYPE yields exactly one row in the view, with several columns renamed to present a more intuitive reporting interface. The alias GR (for "group") is retained in the column prefixes within the lookup hint string, reflecting the original table naming.

Because the view reads directly from the base table with no joins or aggregations, it inherits the full population of program group types defined by the institution, subject only to the column subset and renaming applied. Referential integrity and validation against the IGS_LOOKUP_VALUES lookup set (type COURSE_GROUP_TYPE) are implied by the embedded lookup hint rather than enforced within the view itself.

Key Columns

• PROGRAM_GROUP_TYPE — mapped from IGS_PS_GRP_TYPE.COURSE_GROUP_TYPE. The unique code that identifies the program group type. This is the value most commonly stored on related student records and matched in integration payloads.
• PROGRAM_GROUP_TYPE_DESCRIPTION — mapped from IGS_PS_GRP_TYPE.DESCRIPTION. The user-facing description of the group type; used in reports and LOVs in place of the raw code.
• PROG_GRP_TYPE_CLOSED_INDICATOR — mapped from IGS_PS_GRP_TYPE.CLOSED_IND. Indicates whether the group type is closed (no longer available for new assignments) versus active.
• Lookup hint literal — the constant string '_LA:GR.S_COURSE_GROUP_TYPE:IGS_LOOKUP_VALUES:COURSE_GROUP_TYPE:MEANING'. This is not a data column but a Forms/UI directive that instructs the client to resolve the code's meaning from the IGS_LOOKUP_VALUES lookup of type COURSE_GROUP_TYPE.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE. Standard WHO columns carried through from the base table for audit and change-tracking purposes.

Common Use Cases and Queries

Typical uses include populating report parameters, validating inbound interface values, and producing reference extracts of valid group types. A common query returns only active types with their descriptions:

• Listing available types: SELECT program_group_type, program_group_type_description FROM apps.igsbv_high_edu_prg_grp_types WHERE prog_grp_type_closed_indicator = 'N' ORDER BY program_group_type;
• Resolving a single code for validation or display: SELECT program_group_type_description FROM apps.igsbv_high_edu_prg_grp_types WHERE program_group_type = :p_code;
• Audit/incremental extracts: SELECT program_group_type, last_update_date, last_updated_by FROM apps.igsbv_high_edu_prg_grp_types WHERE last_update_date >= :p_since;

Because the object is read-only and defined over a single table, it is efficient for these lookup and reporting patterns and carries no side effects for integration consumers.