Search Results igs_ps_unit_x_grpmem_u2

Overview

IGS.IGS_PS_UNIT_X_GRPMEM is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the IGS schema (the Student Systems / Higher Education product family). It stores information about Units (academic units or courses) that belong to a Unit Cross-Listed Group. In Oracle Student Systems, cross-listing allows one academic unit to be offered under multiple subject codes or shared across disciplines; this table captures the membership relationships that tie a specific unit code and version to a cross-listed group.

Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is a link. It resolves the many-to-many association between cross-listed groups (IGS_PS_UNIT_X_GRP) and unit versions (IGS_PS_UNIT_VER_ALL), and it may carry descriptive attributes such as the PARENT indicator. It is not a pure hub or satellite, though the WHO audit columns behave satellite-like.

Key Information Stored

The table contains 10 documented columns. The primary key is the surrogate UNIT_X_LISTED_GROUP_MEM_ID (NUMBER(10)), which uniquely identifies each membership row and is enforced by unique index IGS_PS_UNIT_X_GRPMEM_U1. A second unique index, IGS_PS_UNIT_X_GRPMEM_U2, is defined on the business-key candidate pair UNIT_CD and VERSION_NUMBER, ensuring a given unit version appears only once.

• UNIT_X_LISTED_GROUP_MEM_ID – surrogate primary key for the membership record.
• UNIT_X_LISTED_GROUP_ID – foreign key to IGS_PS_UNIT_X_GRP; identifies the cross-listed group to which the unit belongs.
• UNIT_CD – the unit code (VARCHAR2(10)); foreign key to IGS_PS_UNIT_VER_ALL.
• VERSION_NUMBER – the unit version, completing the business key together with UNIT_CD.
• PARENT – a Y/N flag indicating whether the unit is the parent member of the cross-listed group.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

Typical reporting scenarios include determining which academic units are cross-listed within a given group, identifying parent versus child members, and validating that a unit version is uniquely represented. A representative query joining the group header and unit version details follows:

• List all members of a cross-listed group:
  SELECT m.UNIT_CD, m.VERSION_NUMBER, m.PARENT FROM IGS.IGS_PS_UNIT_X_GRPMEM m WHERE m.UNIT_X_LISTED_GROUP_ID = :group_id;
• Reverse lookup — find the group for a unit version:
  SELECT UNIT_X_LISTED_GROUP_ID FROM IGS.IGS_PS_UNIT_X_GRPMEM WHERE UNIT_CD = :unit_cd AND VERSION_NUMBER = :ver;
• Identify parent members only:
  SELECT * FROM IGS.IGS_PS_UNIT_X_GRPMEM WHERE PARENT = 'Y';

The base extraction pattern documented in ETRM selects all ten columns from IGS.IGS_PS_UNIT_X_GRPMEM, which is suitable for reconciliation extracts or data migration.

Related Objects

• IGS.IGS_PS_UNIT_X_GRP – parent cross-listed group header; joined via UNIT_X_LISTED_GROUP_ID.
• IGS.IGS_PS_UNIT_VER_ALL – unit version master; joined via UNIT_CD (and VERSION_NUMBER).
• APPS.IGS_PS_UNIT_X_GRPMEM – the APPS synonym that references this table, the form in which most reports and concurrent programs consume the data.

These FK relationships make the table the central link in the cross-listing data model, connecting group definitions to the units they contain.