Search Results igs_pe_persid_group_v




Overview
Explore in AI Chat

Overview

IGS_PE_PERSID_GROUP_V is a reporting view owned by the APPS schema within the IGS (Student System) product family of Oracle E-Business Suite. It presents person identification groups — logical groupings of person identifiers maintained in the student system — together with descriptive information about the person who created each group. The view is defined in both EBS 12.1.1 and 12.2.2 and is documented with a status of VALID in the ETRM repository.

The view is intended primarily for inquiry, reporting, and integration rather than for transactional maintenance. Identification groups are used by the student system to categorize and process person identifier records in bulk, for example when a set of identifiers must be loaded, validated, or processed together. By exposing the group header, its attributes, its audit columns, and the creator's name and person number in a single row, the view removes the need for consumers to join the group table to the person tables themselves. This makes it a convenient source for concurrent programs, BI Publisher reports, Oracle Reports, and outbound interfaces that must present group information in human-readable form.

Underlying Base Objects

The view is defined over two documented objects: the base table IGS_PE_PERSID_GROUP_ALL and the view IGS_PE_PERSON_BASE_V. The join condition is PE.PERSON_ID = PG.CREATOR_PERSON_ID, an inner join that returns group rows only when the creator person is resolvable in the person base view.

From IGS_PE_PERSID_GROUP_ALL the view selects the group identifier, code, description, status flags, file name, all twenty descriptive flexfield attribute columns, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). The view also derives a ROW_ID using the ROWID of the group table. From IGS_PE_PERSON_BASE_V it obtains FULL_NAME and PERSON_NUMBER, aliased to CREATOR_PERSON_NUMBER. The base table is an _ALL table in name, but the view definition does not filter by organization or business unit, so it selects across all rows visible under the APPS schema. The DDL is owned by APPS, and the view is not identified as a multi-org (MO) view in the documented metadata.

Key Columns

  • ROW_ID — the ROWID of the underlying group row, useful for row-level addressing and debugging.
  • GROUP_ID — internal surrogate key identifying the identification group.
  • GROUP_CD — the user-facing group code, typically the value referenced by users and interfaces.
  • GROUP_TYPE — derived using DECODE on FILE_NAME: returns 'STATIC' when FILE_NAME is null and 'DYNAMIC' otherwise, indicating whether the group is maintained manually or driven by a file.
  • CREATOR_PERSON_ID — person identifier of the creator; the join key to the person base view.
  • FULL_NAME and CREATOR_PERSON_NUMBER — the creator's display name and person number, denormalized for reporting convenience.
  • DESCRIPTION, COMMENTS, CLOSED_IND — descriptive text and the closed status indicator for the group.
  • FILE_NAME — the source file associated with a dynamic group; null for static groups.
  • CREATE_DT — the business date the group was created, distinct from the CREATION_DATE audit column.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield context and segment values.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include listing all identification groups with their creators, identifying dynamic groups that depend on a file, and confirming whether a group has been closed. The GROUP_TYPE derivation is particularly useful for quick filtering without inspecting FILE_NAME directly.

SELECT group_id, group_cd, group_type, description,
       full_name, creator_person_number, closed_ind, create_dt
FROM   apps.igs_pe_persid_group_v
WHERE  closed_ind = 'N'
ORDER  BY group_cd;

To isolate dynamic groups that are still active, filter on GROUP_TYPE. To audit recently maintained groups, constrain on LAST_UPDATE_DATE. Because the view is an inner join, groups whose creator cannot be resolved in IGS_PE_PERSON_BASE_V are excluded; where completeness is required, query the base table directly. The view is read-only in practice, and appropriate grants to reporting schemas are required before use outside APPS.