Results for “segment_sequence”

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

Overview

The IGS_PE_DYNAMIC_SQL table belongs to the IGS (Student System) product family within Oracle E-Business Suite. In the ETRM documentation for both 12.1.1 and 12.2.2, this object is flagged as Obsolete and is listed as not implemented in this database. It therefore exists only as a legacy or residual schema artifact and does not participate in the active runtime data model of a standard EBS installation. Its historical purpose appears to have been to store dynamically constructed SQL fragments, segmented by group and sequence, likely used by the Student System for dynamically generated queries or flexible processing logic.

From a modeling perspective, the ETRM metadata classifies this table heuristically as satellite-leaning. In Data Vault terms, a satellite captures descriptive, time-variant attributes attached to a hub or link. This suggests that IGS_PE_DYNAMIC_SQL would most naturally be modeled as a satellite keyed to a parent group (the hub/link), with SEGMENT_SEQUENCE providing ordering within each group.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• GROUP_ID — Part of the composite primary key (IGS_PE_DYNAMIC_SQL_PK) and the foreign key column referencing IGS_PE_DYNAMIC_PERSID. It identifies the group to which a set of SQL segments belongs.
• SEGMENT_SEQUENCE — The second component of the composite primary key, ordering individual SQL segments within a group. This is the column most directly associated with the search term "segment_sequence."
• SQL_SEGMENT — The descriptive payload column, holding the actual dynamically constructed SQL text fragment for the given group and sequence.
• CREATED_BY, CREATION_DATE — Standard EBS audit columns recording who created the segment and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing the most recent modification and the login context.

The surrogate-style composite primary key (GROUP_ID, SEGMENT_SEQUENCE) is also the sole documented unique index, making it the business-key candidate. There is no separate single-column surrogate key; the two key columns together uniquely identify each row.

Common Use Cases and Queries

Because the table is obsolete and not implemented, practical use cases are limited to historical reference, migration analysis, and legacy data extraction. Typical patterns include:

• Listing all SQL segments for a given group in sequence order:

SELECT segment_sequence, sql_segment
FROM   igs_pe_dynamic_sql
WHERE  group_id = :group_id
ORDER BY segment_sequence;

• Counting segments per group to assess legacy dynamic-SQL usage:

SELECT group_id, COUNT(*) AS segment_count
FROM   igs_pe_dynamic_sql
GROUP BY group_id;

• Tracing audit history of a specific segment by joining on the parent persistence record.

These queries are useful primarily for data lineage and archival reporting when assessing whether legacy Student System functionality must be re-implemented.

Related Objects

The most significant documented relationship is the foreign key from IGS_PE_DYNAMIC_SQL.GROUP_ID to IGS_PE_DYNAMIC_PERSID. This parent table anchors the group definition, making it the natural join partner:

SELECT p.*, s.segment_sequence, s.sql_segment
FROM   igs_pe_dynamic_persid p
JOIN   igs_pe_dynamic_sql    s ON s.group_id = p.group_id;

Because the table is obsolete and largely undocumented beyond this FK, no other dependent views or APIs are enumerated in the ETRM metadata. Any additional related objects should be confirmed directly against the data dictionary of the specific environment under review.