Search Results sqlsegs_id




Overview
Explore in AI Chat

Overview

IGSBV_DYN_PERSON_GROUP_SQLS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. In the ETRM metadata it is registered under the FND Design Data identifier IGS.IGSBV_DYN_PERSON_GROUP_SQLS and carries a status of VALID. The view belongs to the Oracle iLearning (IGS) product family and, more specifically, to the person-grouping subsystem that supports dynamic person groups. As a BIS view, it is intended primarily for read-only reporting and integration consumption rather than transactional processing.

The entity exposes the SQL text fragments that together define the membership rules of a dynamic person group. Rather than storing a single monolithic SQL statement, the grouping engine decomposes the selection logic into ordered segments, each of which is persisted as a row. This view presents those rows together with a sequence number that fixes their order of assembly and a unique identifier that allows each segment to be addressed individually. The user search term "sqlsegs_id" corresponds directly to the SQLSEGS_ID column, which is the unique identifier for SQL segments and functions as the effective primary key of the row set presented by this view.

Underlying Base Objects

The documented dependency for this view is the base table APPS.IGS_PE_DYN_SQLSEGS. The view is defined over that table and projects its columns without documented joins to additional objects; no other referenced base objects appear in the ETRM dependency section. The metadata further records that APPS.IGSBV_DYN_PERSON_GROUP_SQLS is not referenced by any other database object, confirming its position as a terminal, reporting-facing layer. Consequently, changes to the underlying segment table are surfaced through the view with no intervening transformation layer to consider. Because no join is documented, integration consumers should not assume the view resolves file or group header attributes; those relationships, if required, must be obtained from companion IGS entities and combined at query time.

Key Columns

The view exposes eight columns. Their documented meanings are as follows:

  • SQLSEGS_ID (NUMBER): Unique identifier for SQL segments. This is the principal key for the entity and the value most frequently used in lookup predicates.
  • FILE_NAME (VARCHAR2, 200): File name associated with the SQL segment definition.
  • SEG_SEQUENCE_NUM (NUMBER): Segment sequence number, establishing the order in which segments are concatenated.
  • SQL_SEGMENT (VARCHAR2, 2000): The SQL segment text itself, holding one fragment of the dynamic group's selection logic.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE: Standard WHO audit columns recording insert and update context.

Reconstructing a complete SQL statement requires concatenating SQL_SEGMENT values across rows sharing a common group or file context, ordered by SEG_SEQUENCE_NUM. The 2000-character limit on each segment is the reason the definition is partitioned across multiple rows.

Common Use Cases and Queries

This view is typically used to audit, troubleshoot, or migrate dynamic person-group definitions. Typical scenarios include verifying the assembled SQL logic behind a group, exporting definitions for documentation or code review, and diagnosing membership failures by inspecting individual segments and their order.

Because the view is not indexed for group-level retrieval in its own right, queries should filter on FILE_NAME or SQLSEGS_ID as available, and always order by SEG_SEQUENCE_NUM when reconstructing statements:

  • Retrieve a specific segment by its identifier, matching the sqlsegs_id search term.
  • List all segments for a given file name in sequence to view the complete definition.
  • Audit recently modified segment definitions using LAST_UPDATE_DATE.

Standard extraction follows the documented query pattern:

SELECT FILE_NAME, SEG_SEQUENCE_NUM, SQL_SEGMENT, SQLSEGS_ID, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM APPS.IGSBV_DYN_PERSON_GROUP_SQLS;

Individual lookup: SELECT SQL_SEGMENT FROM APPS.IGSBV_DYN_PERSON_GROUP_SQLS WHERE SQLSEGS_ID = :p_id; Ordered reconstruction: SELECT SEG_SEQUENCE_NUM, SQL_SEGMENT FROM APPS.IGSBV_DYN_PERSON_GROUP_SQLS WHERE FILE_NAME = :p_file ORDER BY SEG_SEQUENCE_NUM;