Search Results sql_segment

Overview

IGS_PE_ALL_PERSID_GROUP_V is a database view belonging to the IGS – Student System product family within Oracle E-Business Suite. Its documented purpose is to provide a unified presentation of person identification group data by combining two conceptual sources: the existing static Person ID table and a proposed dynamic Person ID table. The view is therefore best understood as an integration and consolidation layer rather than a transactional entity in its own right.

The object is classified as obsolete in the IGS – Student System module, and the ETRM metadata states that it is not implemented in this database. This status indicates that the view was designed as part of an enhancement or migration effort and was superseded or never deployed in the delivered Oracle EBS 12.1.1 and 12.2.2 environments. Consultants encountering it should treat it as a reference definition rather than an active reporting source.

Underlying Base Objects

According to the documented view text, IGS_PE_ALL_PERSID_GROUP_V is defined exclusively over IGS_PE_PERSID_GROUP_V, aliased as PPG. The column list selects ROW_ID, GROUP_ID, GROUP_TYPE, a literal zero, a literal NULL, GROUP_CD, CREATOR_PERSON_ID, DESCRIPTION, CLOSED_IND, COMMENTS, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

No referenced base objects are documented in the ETRM 12.2.2 metadata, and no owner is recorded. The design intent described in the documentation is a union of a static Person ID table and a newly proposed dynamic Person ID table. In the implemented definition, however, the query reads from a single view, with the dynamic-side columns represented by the literal 0 and NULL. This suggests the union predicate and the dynamic source were either staged for a future release or omitted from the delivered form.

Key Columns

• ROW_ID – Surrogate row identifier for the group record.
• GROUP_ID – Identifier of the person ID group.
• GROUP_TYPE – Discriminator that distinguishes the category of identification group.
• SEGMENT_SEQUENCE – Positional sequence for the identification segment; populated with the literal 0 in the delivered definition.
• SQL_SEGMENT – Column intended to carry a dynamically generated SQL fragment used to resolve person IDs; populated with the literal NULL in the delivered definition. This is the column most commonly associated with the search term "sql_segment".
• GROUP_CD – Short code assigned to the person ID group.
• CREATOR_PERSON_ID – Person who created the group definition.
• DESCRIPTION and COMMENTS – Free-text descriptive attributes.
• CLOSED_IND – Indicates whether the group is closed to further use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle WHO audit columns.

Common Use Cases and Queries

Because the view is not implemented in the database, direct querying is generally not possible and transactional reporting should target IGS_PE_PERSID_GROUP_V instead. The primary practical use is structural reference: understanding how static and dynamic person ID group definitions were intended to be unified, and identifying the SEGMENT_SEQUENCE and SQL_SEGMENT attributes that support dynamic segment resolution.

A representative query, where the object exists, follows the shape below:

SELECT group_id,
       group_type,
       group_cd,
       segment_sequence,
       sql_segment,
       closed_ind
FROM   igs_pe_all_persid_group_v
WHERE  closed_ind = 'N'
ORDER  BY group_id, segment_sequence;

Analysts investigating dynamic person identification logic may also inspect SQL_SEGMENT to determine whether a group relies on runtime-generated SQL. In delivered environments this column returns NULL, confirming that the dynamic path was not activated. Migration or upgrade assessments should verify the object's presence in the target instance before writing any custom report or interface against it.