Results for “creator_person_number”

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

Overview

IGS_PE_PERSID_GROUP is a reporting view belonging to the IGS — Student System product family, which Oracle classifies as obsolete in the ETRM documentation. The view presents person identification (persid) group data drawn from the multiorganization group table, joined to a person base view to resolve the identity of the person who created each group. Its principal role is to expose group header information — group code, description, creation date, open/closed status, and descriptive flexfield attributes — together with the creator's full name and person number in a single, query-ready result set. This construction spares reporting and integration developers from having to perform the underlying join themselves and provides a stable projection of the group entity for concurrent programs, Oracle Reports, BI Publisher data templates, and ad hoc SQL.

The parent object, IGS_PE_PERSID_GROUP_ALL, supports the Oracle EBS multiorganization (MOAC) security model by storing rows partitioned by ORG_ID. The view therefore participates in organization-level access control, returning only rows visible in the current operating unit context.

Underlying Base Objects

The documented view text defines IGS_PE_PERSID_GROUP over exactly two objects:

• IGS_PE_PERSID_GROUP_ALL — the multiorganization group table, aliased TAB, supplying all persistent group attributes.
• IGS_PE_PERSON_BASE_V — the person base view, aliased PE, supplying FULL_NAME and PERSON_NUMBER for the creator.

The join is an inner join on PE.PERSON_ID = TAB.CREATOR_PERSON_ID. A constant restriction TAB.FILE_NAME IS NULL excludes rows that carry an uploaded file reference, so only non-file-backed group records are surfaced. ETRM records no other base objects, and the excerpt does not state the view owner.

Key Columns

The view exposes the following notable columns:

• ROW_ID — the underlying table ROWID, useful for direct row identification.
• ORG_ID — the operating unit that owns the group record; drives MOAC filtering.
• GROUP_ID, GROUP_CD — the surrogate key and the human-readable group code.
• CREATOR_PERSON_ID — foreign key to the person who created the group.
• FULL_NAME, CREATOR_PERSON_NUMBER — derived from IGS_PE_PERSON_BASE_V; the creator's name and person number.
• DESCRIPTION, CREATE_DT, CLOSED_IND, COMMENTS — the group's descriptive text, creation timestamp, active/closed indicator, and free-form comments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context for rows created by batch processes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the descriptive flexfield segments.

The WHERE clause compares ORG_ID against a value decoded from the USERENV('CLIENT_INFO') session setting, defaulting to -99 when absent — the standard EBS multiorganization security predicate.

Common Use Cases and Queries

Typical applications include: listing open identification groups visible to the current operating unit; reporting group ownership by person; retrieving flexfield attributes for downstream interfaces; and validating group codes before insert operations against IGS_PE_PERSID_GROUP_ALL.

SELECT group_id,
       group_cd,
       description,
       creator_person_number,
       full_name,
       closed_ind
  FROM igs_pe_persid_group
 WHERE closed_ind = 'N'
 ORDER BY group_cd;

To inspect flexfield data for a specific group code:

SELECT group_cd,
       attribute_category,
       attribute1,
       attribute2
  FROM igs_pe_persid_group
 WHERE group_cd = :p_group_cd;

To count groups by creator within the current organization context:

SELECT creator_person_number,
       full_name,
       COUNT(*) group_count
  FROM igs_pe_persid_group
 GROUP BY creator_person_number, full_name
 ORDER BY group_count DESC;

Because the view enforces the CLIENT_INFO organization predicate internally, applications invoking these queries should call FND_CLIENT_INFO or run within a properly initialized MOAC session to obtain correct organization filtering. As the product is designated obsolete, new development should be directed to supported alternatives where available.