Search Results igs_ps_unit_x_grpmem_pk

Overview

IGS_PS_UNIT_X_GRPMEM is a transactional table within the Oracle E-Business Suite Student System (IGS) product family. It stores the membership records that associate individual academic units with a Unit Cross-Listed Group, effectively defining which unit versions participate in a cross-listing arrangement. In the EBS 12.1.1 and 12.2.2 data models, the object is documented under the IGS schema and is classified as obsolete, meaning Oracle no longer actively implements it in current database instances. The ETRM documentation explicitly records the status as "Not implemented in this database," which is significant for any upgrade or migration assessment.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This classification reflects the table's role as an associative entity that connects a unit version to a cross-listed group, rather than describing either entity's attributes independently. Analysts designing a Data Vault or dimensional model should treat IGS_PS_UNIT_X_GRPMEM as a relationship or bridge construct.

Key Information Stored

The documented physical schema contains 10 columns. The most important include:

• UNIT_X_LISTED_GROUP_MEM_ID — the surrogate primary key, defined by the IGS_PS_UNIT_X_GRPMEM_PK constraint and also carried by the unique index IGS_PS_UNIT_X_GRPMEM_U1.
• UNIT_X_LISTED_GROUP_ID — foreign key identifying the parent cross-listed group in IGS_PS_UNIT_X_GRP.
• UNIT_CD and VERSION_NUMBER — the composite business key pointing to a specific unit version in IGS_PS_UNIT_VER_ALL. Together they form the unique index IGS_PS_UNIT_X_GRPMEM_U2 (referenced in the documentation as UK1), which enforces that a given unit version appears only once per cross-listed group.
• PARENT — a column indicating hierarchical or parental relationship context within the group membership structure.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit and concurrency tracking.

The distinction between the surrogate primary key and the business-key unique index is essential: integrations should resolve membership by (UNIT_CD, VERSION_NUMBER) plus group identifier rather than relying on the generated ID.

Common Use Cases and Queries

Typical usage centers on reporting which units belong to a cross-listed group and validating the integrity of unit version assignments. A representative query joining the membership table to its parent group and unit version source follows:

• SELECT m.unit_cd, m.version_number, g.unit_x_listed_group_id FROM igs_ps_unit_x_grpmem m, igs_ps_unit_x_grp g WHERE m.unit_x_listed_group_id = g.unit_x_listed_group_id;
• Auditing orphaned memberships by outer-joining to IGS_PS_UNIT_VER_ALL on UNIT_CD and VERSION_NUMBER.
• Detecting duplicate unit assignments per group using GROUP BY on UNIT_X_LISTED_GROUP_ID and UNIT_CD.
• Data migration reconciliation, where legacy cross-list definitions must be mapped to new structures.

Related Objects

The most significant related objects, grounded in the documented foreign keys, include:

• IGS_PS_UNIT_X_GRP — parent cross-listed group table; joined via UNIT_X_LISTED_GROUP_ID.
• IGS_PS_UNIT_VER_ALL — unit version table; joined via UNIT_CD and VERSION_NUMBER.
• IGS_PS_UNIT_X_GRPMEM_PK / _U1 / _U2 — primary key and unique indexes enforcing identity and business-key uniqueness.
• IGS_PS_UNIT_VER_ALL-dependent views and the IGS unit offerings APIs — downstream consumers that inherit cross-list membership through these joins.