Results for “rg_row_segment_sequences_v”

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

Overview

RG_ROW_SEGMENT_SEQUENCES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the RG (Application Report Generator) product, the metadata-driven reporting engine that powers Oracle Reports integration and the broader Applications Report Generator framework. The view exposes the segment sequences that make up a report row order — the ordered layout of key flexfield segments that appear on a generated report. It presents the transactional configuration stored in RG_ROW_SEGMENT_SEQUENCES alongside the row order context and the corresponding key flexfield segment definitions from FND_ID_FLEX_SEGMENTS.

Because the view joins to FND_ID_FLEX_SEGMENTS and filters on ENABLED_FLAG = 'Y', consumers see only enabled flexfield segments. This makes the view suitable for runtime report generation, ad hoc SQL queries against report definitions, and integration routines that need to resolve the display and ordering semantics of report columns.

Underlying Base Objects

The view is defined over three base objects, all referenced through synonyms in the APPS schema:

• RG_ROW_SEGMENT_SEQUENCES — the primary table, providing the sequence, order type, display type, segment width, and descriptive flexfield context columns.
• RG_ROW_ORDERS — joined on ROW_ORDER_ID, supplying the row order context and the ID_FLEX_CODE/STRUCTURE_ID key flexfield coordinates.
• FND_ID_FLEX_SEGMENTS — outer-joined on ID_FLEX_CODE, STRUCTURE_ID, and APPLICATION_COLUMN_NAME, with the ENABLED_FLAG = 'Y' predicate applied to yield the enabled flexfield segment name in the SEG_NAME column.

The ROW_ID column is the ROWID from RG_ROW_SEGMENT_SEQUENCES, retained for direct row addressing. The outer join notation (+) on the FND_ID_FLEX_SEGMENTS conditions indicates Oracle-style outer join semantics, allowing row segment sequence rows to survive where no matching enabled flexfield segment exists.

Key Columns

• ROW_ID — the physical ROWID of the underlying RG_ROW_SEGMENT_SEQUENCES row; useful for direct updates or deletes.
• ROW_SEGMENT_SEQUENCE_ID — the surrogate primary key of the row segment sequence record.
• ROW_ORDER_ID — foreign key to RG_ROW_ORDERS; identifies the parent row order.
• SEGMENT_SEQUENCE — the positional order of the segment within the report row.
• SEG_ORDER_TYPE — controls how the segment is ordered within the report layout.
• SEG_DISPLAY_TYPE — the display type applied to the segment. The user's search for "seg_display_type" maps directly to this column and its corresponding field in the ETRM/Application Developer forms, where the display type governs how the flexfield value is rendered in the report output.
• SEGMENT_NAME and SEG_NAME — the segment name from the row segment sequence and the friendly name resolved from FND_ID_FLEX_SEGMENTS, respectively.
• STRUCTURE_ID and APPLICATION_ID — key flexfield structure context for the segment.
• APPLICATION_COLUMN_NAME — the column name used by the flexfield segment definition; the join key to FND_ID_FLEX_SEGMENTS.
• SEGMENT_WIDTH — the column width allocated to the segment on the report.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield context and attribute values carried on the underlying table.

Common Use Cases and Queries

Typical scenarios include inspecting the segment layout of a report definition, validating SEG_DISPLAY_TYPE settings, and joining report definitions to flexfield metadata for integration or documentation purposes.

To list the segments of a specific row order:

• SELECT segment_sequence, segment_name, seg_name, seg_display_type, seg_order_type, segment_width
• FROM applsys.rg_row_segment_sequences_v
• WHERE row_order_id = :p_row_order_id
• ORDER BY segment_sequence;

To audit display type usage across all row orders:

• SELECT row_order_id, segment_sequence, seg_display_type, segment_name
• FROM applsys.rg_row_segment_sequences_v
• WHERE seg_display_type IS NOT NULL
• ORDER BY row_order_id, segment_sequence;

Because the view filters on ENABLED_FLAG = 'Y', disabled flexfield segments are omitted; queries that require the full population should target RG_ROW_SEGMENT_SEQUENCES directly. All queries should be executed against the APPS schema with appropriate grants, and read consistency should be considered when joining to live flexfield metadata.