Search Results class_meet_group_name

Overview

IGS.IGS_PS_USO_CM_GRP is a transactional table within the Oracle Student System (a module of Oracle E-Business Suite) that stores the definition of every Class Meet Group created in the institution's scheduling and enrollment infrastructure. A Class Meet Group represents a named grouping of class meetings — used primarily to control enrollment and override capacity for a set of related class meetings tied to a specific calendar instance. The table resides in the APPS_TS_TX_DATA tablespace, is owned by the IGS schema, and is registered as FND Design Data object IGS.IGS_PS_USO_CM_GRP with status VALID.

From a dimensional modeling perspective, the mined Data Vault classification is satellite-leaning — that is, the table behaves as an attributed satellite attached to a calendar-instance hub (via CAL_TYPE and CI_SEQUENCE_NUMBER) rather than as an independent hub or a pure link. Modelers should treat CLASS_MEET_GROUP_ID as a surrogate key issued to a business grouping, not as an enterprise-wide hub key.

Key Information Stored

The table holds eleven documented columns. The most significant are:

• CLASS_MEET_GROUP_ID (NUMBER, 10) — Sequence-generated surrogate primary key (IGS_PS_USO_CM_GRP_PK) that uniquely identifies a Class Meet group.
• CLASS_MEET_GROUP_NAME (VARCHAR2, 80) — The user-facing name of the group; the attribute the user searched for. It forms part of the composite business key IGS_PS_USO_CM_GRP_U2.
• CAL_TYPE (VARCHAR2, 10) — Calendar Type. This column carries a foreign key to IGS_CA_INST_ALL and, together with CI_SEQUENCE_NUMBER, scopes the group to a calendar instance.
• CI_SEQUENCE_NUMBER (NUMBER) — Calendar Instance Sequence Number, the second half of the calendar-instance context.
• MAX_ENR_GROUP (NUMBER) — Maximum enrollment permitted for a meet associated with this class group.
• MAX_OVR_GROUP (NUMBER) — Maximum override capacity permitted for the same grouping.
• Standard WHO audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Two unique indexes qualify as business-key candidates: U1 on CLASS_MEET_GROUP_ID (surrogate uniqueness) and U2 on the composite (CLASS_MEET_GROUP_NAME, CAL_TYPE, CI_SEQUENCE_NUMBER), which enforces that a name is unique only within a given calendar instance — the true natural key.

Common Use Cases and Queries

Typical reporting and validation scenarios include: locating a group by name within a calendar instance, auditing enrollment/override ceilings, and resolving the class meetings that belong to a group. A standard lookup pattern is:

• SELECT CLASS_MEET_GROUP_ID, CLASS_MEET_GROUP_NAME, CAL_TYPE, CI_SEQUENCE_NUMBER, MAX_ENR_GROUP, MAX_OVR_GROUP FROM IGS.IGS_PS_USO_CM_GRP WHERE CLASS_MEET_GROUP_NAME = :p_name;
• Calendar-scoped lookup: add AND CAL_TYPE = :cal AND CI_SEQUENCE_NUMBER = :ci to satisfy the U2 key — this returns at most one row and is the recommended retrieval pattern.
• Capacity audit: compare MAX_ENR_GROUP / MAX_OVR_GROUP against actual enrollment counts at the meet level.
• Integration/interface extracts: the documented Query Text selection of all eleven columns is the canonical pull for downstream data feeds.

Related Objects

The table participates in a small, well-defined dependency mesh:

• IGS.IGS_PS_USO_CLAS_MEET — the primary referencing table; its CLASS_MEET_GROUP_ID column joins to this table, so each class meet is assigned to at most one group.
• IGS.IGS_CA_INST_ALL — parent calendar-instance table referenced via CAL_TYPE, providing calendar context for grouping.
• APPS.IGS_PS_USO_CM_GRP — the APPS synonym through which application code and reports access the table.
• Other class-meet, scheduling, and enrollment objects (for example, class-meeting and enrollment-capacity views) that consume MAX_ENR_GROUP and MAX_OVR_GROUP indirectly through IGS_PS_USO_CLAS_MEET.

No additional outbound foreign keys beyond CAL_TYPE are documented, confirming its position as a low-fan-out satellite whose principal dependency flows to the class-meet table.