Results for “igs_ps_grp_mbr”

50+ results




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

Overview

IGS_PS_GRP_MBR is a table within the IGS (Student System) product family of Oracle E-Business Suite. The metadata classifies IGS as an obsolete module, and the physical implementation confirms this status: the table is not implemented in the documented database, meaning no runtime data resides in it in a standard 12.1.1 or 12.2.2 installation. Its purpose, as described, is to record the programs that are members of a program grouping. Each row associates a specific program version with a grouping, forming the membership relationship between individual academic programs and the groups to which they belong.

From a modeling perspective, the heuristic Data Vault classification supplied in the metadata identifies this object as a link. This is consistent with its structure: the table exists purely to connect two stronger entities — the program definition and the program group — and carries no independent descriptive attributes beyond standard audit columns. Analysts modeling a modern equivalent would treat IGS_PS_GRP_MBR as a link table resolving a many-to-many relationship between programs and groups, with the audit columns representing the link's descriptive payload.

Key Information Stored

The table exposes eight documented columns. Three form the composite primary key and simultaneously constitute the single unique index, IGS_PS_GRP_MBR_U1, making them the business-key candidates. Because the composite key has no separate surrogate identifier column, identity is expressed entirely through business attributes.

  • COURSE_CD — the code identifying the program (internally named as a course) that is a member of the grouping; first component of the primary key and of the unique index.
  • VERSION_NUMBER — the version of that program, distinguishing iterations of the same program code; second component of the primary key and unique index.
  • COURSE_GROUP_CD — the code of the program grouping to which the program belongs; third component of the primary key and unique index.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns capturing who created and last modified each membership row and when.

The primary key constraint IGS_PS_GRP_MBR_PK is defined over COURSE_CD, VERSION_NUMBER, and COURSE_GROUP_CD. No non-key descriptive attributes are documented, reinforcing the table's role as a pure association entity.

Common Use Cases and Queries

Although the table is not populated in the reference database, the patterns below illustrate how it would be queried where an equivalent structure is deployed. A typical requirement is to list all programs belonging to a given group:

  • Membership lookup by group: SELECT COURSE_CD, VERSION_NUMBER FROM IGS_PS_GRP_MBR WHERE COURSE_GROUP_CD = :group_cd;
  • Reverse lookup, finding the groups to which a program version belongs: SELECT COURSE_GROUP_CD FROM IGS_PS_GRP_MBR WHERE COURSE_CD = :course_cd AND VERSION_NUMBER = :version;
  • Reporting joins to resolve group and program names by joining to IGS_PS_GRP_ALL and IGS_PS_VER_ALL on their respective codes.
  • Audit and reconciliation queries filtering on CREATION_DATE or LAST_UPDATE_DATE to determine when a membership was established or changed.

Because the unique index enforces one row per program-version-group combination, duplicate detection and data quality checks can rely on IGS_PS_GRP_MBR_U1.

Related Objects

The foreign key metadata establishes the immediate dependency chain:

  • IGS_PS_GRP_ALL — the program grouping master, joined via COURSE_GROUP_CD.
  • IGS_PS_VER_ALL — the program version entity, joined via COURSE_CD and VERSION_NUMBER.
  • IGS_PS_GRP_MBR_PK — the primary key constraint defining row uniqueness.
  • IGS_PS_GRP_MBR_U1 — the unique index over the same three business columns.

Any downstream reporting or API layer addressing program groupings would traverse these relationships, combining membership rows with the parent group and program version records to produce complete, human-readable output.