Search Results igs_pe_prsid_grp_mem




Overview
Explore in AI Chat

Overview

The view IGS_PE_PRSID_GRP_MEM belongs to the IGS – Student System product family within Oracle E-Business Suite. The IGS module (Intelligent Grants System / Student System components) was historically used for person and student identifiers, and it is now marked Obsolete in the ETRM reference set for releases 12.1.1 and 12.2.2. The view presents membership records that associate a person with an identifier group — in other words, it exposes the rows that define which persons are members of a given person-identifier grouping.

Its role in reporting and integration is that of an operational, multi-org aware reporting layer over the underlying association table. Rather than querying the base table directly, downstream reports, concurrent programs, and interfaces reference this view so that the standard multi-org security predicate (driven by ORG_ID) is applied automatically. Because the view is flagged as Not implemented in this database and the parent product is obsolete, the object is documented primarily for archival and migration-reference purposes; it will generally appear populated only in environments where the legacy IGS Student System objects were previously deployed.

Underlying Base Objects

The ETRM metadata documents the defining query and identifies a single underlying base object: IGS_PE_PRSID_GRP_MEM_ALL. The view does not introduce any joins; it is a flat projection of the base table, selecting all business columns plus the standard WHO columns and the ROWID pseudo-column aliased as ROW_ID. The naming convention of the base table — the _ALL suffix — confirms that it is a multi-org (partitioned by operating unit) table, and the view applies an ORG_ID filter derived from USERENV('CLIENT_INFO'). This is the classic Oracle EBS multi-org secured view pattern, where the client-info string carries the current operating unit identifier. No other referenced base objects were documented in the ETRM metadata, and no join to person, group, or lookup tables is present in the view text itself.

Key Columns

Common Use Cases and Queries

Typical usage centers on identifying current members of a person-identifier group for a given operating unit, or reconciling effective-dated membership history. A common query selects current members as of a reference date:

  • List current members: SELECT group_id, person_id, start_date, end_date FROM igs_pe_prsid_grp_mem WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
  • Members of a specific group: SELECT person_id, start_date, end_date FROM igs_pe_prsid_grp_mem WHERE group_id = :group_id;
  • Operating-unit-scoped extract: SELECT * FROM igs_pe_prsid_grp_mem WHERE org_id = :org_id;

Because the view enforces multi-org security, callers should initialize CLIENT_INFO appropriately when querying outside a Forms session. Given the obsolete status, any implementation should treat these queries as migration or audit aids rather than ongoing production interfaces.