Search Results sqlsegs_id




Overview
Explore in AI Chat

Overview

The IGSBV_DYN_PERSON_GROUP_SQLS view is a read-only database object owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It belongs to the Person/constituent management area of the Student System and exposes the SQL fragments that make up the definition of a dynamic person group. Dynamic person groups, in the IGS data model, are populations defined by a stored SQL predicate rather than by an explicitly named list of persons; the group membership is resolved at run time by executing the stored SQL. This view is the documented interface for inspecting those stored SQL fragments, their file association, and their ordinal position within the overall statement.

Because it is defined with a WITH READ ONLY clause, the view cannot be used as a DML target. Its purpose is query and reporting access only. It is documented as VALID and is listed in ETRM under the IGS - Student System module, meaning it is treated as part of the supported reference surface of the product rather than as an incidental internal object.

Underlying Base Objects

The view is defined over a single base table, IGS_PE_DYN_SQLSEGS (aliased PDS in the view text). The view text is:

No additional base objects, joins, or lookups are documented in the ETRM 12.2.2 metadata. A stored SQL statement for a dynamic person group is physically longer than the column width available for a single segment, so it is stored in multiple rows of IGS_PE_DYN_SQLSEGS, each row holding one segment. The view simply re-presents those rows with a stable column list, including the standard EBS who-columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Key Columns

  • FILE_NAME — identifies the file or grouping to which the SQL segment belongs, allowing multiple stored SQL definitions to coexist and be distinguished.
  • SEG_SEQUENCE_NUM — the ordinal position of the segment within its parent SQL statement. Segments must be concatenated in ascending sequence order to reconstruct the complete statement. This column is the anchor most frequently searched against when developers investigate how a dynamic group is assembled.
  • SQL_SEGMENT — the actual text fragment of the SQL statement.
  • SQLSEGS_ID — the primary key of the underlying segment row, providing unique identification and a join key back to base-table audits.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Oracle EBS audit columns recording insert and most-recent-update metadata.

Common Use Cases and Queries

Typical use cases include auditing how a dynamic person group is defined, diagnosing why a group returns unexpected members, and reconstructing the effective SQL for documentation or migration. A common pattern orders by SEG_SEQUENCE_NUM per FILE_NAME:

  • SELECT FILE_NAME, SEG_SEQUENCE_NUM, SQL_SEGMENT FROM APPS.IGSBV_DYN_PERSON_GROUP_SQLS ORDER BY FILE_NAME, SEG_SEQUENCE_NUM;
  • SELECT SQLSEGS_ID, SEG_SEQUENCE_NUM, SQL_SEGMENT, LAST_UPDATE_DATE FROM APPS.IGSBV_DYN_PERSON_GROUP_SQLS WHERE FILE_NAME = :p_file_name ORDER BY SEG_SEQUENCE_NUM;

To trace ownership, query the audit columns: SELECT FILE_NAME, MAX(LAST_UPDATE_DATE) FROM APPS.IGSBV_DYN_PERSON_GROUP_SQLS GROUP BY FILE_NAME;. Because the view is read-only and its base table is not documented as exposed here, no inserts or updates should be directed at it; changes to segment text must occur through the supported IGS application flows.