Results for “enrollment_maximum”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view IGS_PS_UNIT_X_GRPMEM_V belongs to the Oracle E-Business Suite IGS — Student System product family, which is documented in ETRM as an obsolete module in release 12.1.1 and 12.2.2. The object is a reporting and integration view that flattens the relationship between program units, their versioned definitions, and the membership records of unit "cross-listed" groups. Its purpose is to present enrollment-capacity attributes alongside the identifying keys of a group membership record, so that downstream reports, concurrent programs, or integration interfaces can retrieve both structural keys and enrollment thresholds in a single query.

The view is relevant to the term override_maximum because it surfaces the column OVERRIDE_MAXIMUM, which expresses the override enrollment maximum applicable to a cross-listed group member. In other words, where a group inherits or explicitly sets a maximum enrollment override, this view makes that value available together with the parent unit and group identifiers. ETRM records that the object is "Not implemented in this database," indicating that in the documented environment the underlying tables are absent, which is consistent with the module's obsolete status.

Underlying Base Objects

The view text reveals that it is defined over three base objects, joined in a single SELECT statement:

• IGS_PS_UNIT_X_GRPMEM UXGM — the unit cross-listed group member table, supplying the membership identifier, parent, unit code, version, and audit columns.
• IGS_PS_UNIT_VER UV — the unit version table, which contributes TITLE, VERSION_NUMBER, ENROLLMENT_MAXIMUM, and OVERRIDE_ENROLLMENT_MAX.
• IGS_PS_UNIT_X_GRP UXG — the unit cross-listed group table, which supplies the flags MAX_ENR_GROUP and MAX_OVR_GROUP that govern whether the version-level maximums are exposed.

The join is established on UNIT_CD and VERSION_NUMBER between the member and version tables, and on UNIT_X_LISTED_GROUP_ID between the member and group tables. ETRM lists no explicitly documented referential constraints beyond these join predicates, and no referenced base objects are recorded as formal foreign keys.

Key Columns

• ROW_ID — the row identifier of the group member record, used for addressability and DML-style lookups.
• UNIT — a concatenation of UNIT_CD, VERSION_NUMBER, and TITLE, providing a human-readable descriptor.
• UNIT_X_LISTED_GROUP_MEM_ID and UNIT_X_LISTED_GROUP_ID — primary and parent group keys.
• UNIT_CD, VERSION_NUMBER — the unit and version being cross-listed.
• PARENT — the parent membership reference for hierarchical group structures.
• ENROLLMENT_MAXIMUM — derived via DECODE(UXG.MAX_ENR_GROUP, NULL, NVL(UV.ENROLLMENT_MAXIMUM,0), NULL); only populated when the group flag MAX_ENR_GROUP is null.
• OVERRIDE_MAXIMUM — derived via DECODE(UXG.MAX_OVR_GROUP, NULL, NVL(UV.OVERRIDE_ENROLLMENT_MAX,0), NULL); only exposed when MAX_OVR_GROUP is null. This is the column users searching for override_maximum are seeking.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include identifying override enrollment limits for cross-listed unit groups, validating capacity configuration, and feeding enrollment or scheduling reports. Because the view applies DECODE logic, values may be null depending on group-level flags, so queries should tolerate nulls.

• Retrieve override maximums for a specific unit and version.
• List all group memberships with non-null override values for capacity auditing.
• Join to related unit tables for broader reporting.

SELECT unit_cd, version_number, unit,
       unit_x_listed_group_id,
       override_maximum
FROM   igs_ps_unit_x_grpmem_v
WHERE  unit_cd = :p_unit_cd
AND    version_number = :p_version;

SELECT unit, override_maximum
FROM   igs_ps_unit_x_grpmem_v
WHERE  override_maximum IS NOT NULL
ORDER BY unit;

Given that ETRM marks the object as not implemented, these queries are illustrative; verification against a live 12.1.1/12.2.2 instance is recommended before deployment.