Results for “igs_pe_persid_group_all”

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

Overview

IGS_PE_PERSID_GROUP_ALL is a table within the Oracle E-Business Suite Student System (IGS) product family. The ETRM documentation classifies the IGS product line as obsolete, and this table is explicitly noted as "Not implemented in this database" in the reference environment. Despite that implementation status, the entity remains a documented part of the EBS 12.1.1 and 12.2.2 schema catalog and continues to appear in metadata repositories, data lineage analyses, and migration inventories for institutions that historically deployed Oracle Student System.

The table describes the available groups to which persons can be assigned for reporting purposes. It functions as a classification or grouping registry, allowing person records (parties) to be organized into named cohorts that downstream reporting, award processing, enrollment setup, and security routines can reference. Because it defines the group definitions themselves rather than the individual group memberships, the heuristic Data Vault classification derived from the foreign key structure is hub. In Data Vault modeling terms, this suggests treating IGS_PE_PERSID_GROUP_ALL as a business-key-bearing hub entity, with group memberships (IGS_PE_PRSID_GRP_MEM_ALL) and group security assignments (IGS_PE_PRSID_GRP_SEC) behaving as satellites or link tables that depend upon it.

Key Information Stored

The documented physical schema contains 39 columns. The surrogate primary key is GROUP_ID, enforced by the unique index IGS_PE_PERSID_GROUP_PK. A second unique index, IGS_PE_PERSID_GROUP_U1, is defined on GROUP_CD, making the group code the principal business-key candidate. These two identifiers should be distinguished in any integration or ETL logic: GROUP_ID is the internal referential anchor used by child tables, while GROUP_CD is the human-readable, externally meaningful identifier.

The most significant descriptive and operational columns include:

• GROUP_ID — surrogate primary key; the value referenced by all dependent foreign keys.
• GROUP_CD — unique business code identifying the group.
• DESCRIPTION — textual description of the group's purpose.
• CREATOR_PERSON_ID — foreign key to HZ_PARTIES, identifying the person who created the group.
• CREATE_DT — date the group was established.
• CLOSED_IND — indicator of whether the group is closed to further use.
• COMMENTS — free-form annotation.
• ORG_ID — operating unit or organization context for multi-org installations.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns recording the process that last touched the row.
• FILE_NAME — associated file reference, typically for bulk-upload or import scenarios.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard Oracle DFF (descriptive flexfield) extensibility block.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on resolving group identifiers into readable codes, identifying active versus closed groups, and joining group definitions to membership or security records. A common reporting pattern retrieves open groups with their creator information:

• List active groups: SELECT GROUP_ID, GROUP_CD, DESCRIPTION FROM IGS_PE_PERSID_GROUP_ALL WHERE CLOSED_IND = 'N';
• Resolve a group code to its surrogate key for downstream inserts: SELECT GROUP_ID FROM IGS_PE_PERSID_GROUP_ALL WHERE GROUP_CD = :p_group_cd;
• Enrich membership reporting: join IGS_PE_PRSID_GRP_MEM_ALL m to IGS_PE_PERSID_GROUP_ALL g ON m.GROUP_ID = g.GROUP_ID to produce group names alongside person assignments.
• Audit trail review: filter on LAST_UPDATE_DATE and PROGRAM_ID to trace concurrent processes that modified group definitions.

Because the entity is closely tied to person-grouping, deployment, and award workflows, it also serves as a reference source during data migration and reconciliation when institutions move away from Oracle Student System.

Related Objects

The ETRM relationship data documents one outbound foreign key and seven inbound references. The most significant dependent objects are:

• HZ_PARTIES — referenced by IGS_PE_PERSID_GROUP_ALL.CREATOR_PERSON_ID; identifies the group creator as a party record.
• IGS_PE_PRSID_GRP_MEM_ALL — membership table joined on GROUP_ID; records which persons belong to each group.
• IGS_PE_PRSID_GRP_SEC — group security assignments joined on GROUP_ID; controls access to group data.
• IGS_EN_PIG_S_SETUP and IGS_EN_PIG_CP_SETUP — enrollment person-group setup tables joined on GROUP_ID; drive enrollment-related grouping configuration.
• IGF_AW_AWD_FRML_DET_ALL — award formula detail table joined on PE_GROUP_ID; links group definitions to financial aid award processing.
• IGS_AS_GPC_PE_ID_GRP — admissions/adviser grouping configuration joined on GROUP_ID.
• IGS_DA_RQST — data request table referencing this entity via PERSON_ID_GROUP_ID; used when requesting person-group data extracts.

Together these objects confirm the table's role as a central grouping hub within the obsolete IGS Student System schema, even where it is not physically deployed.