Results for “segment_width”

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

Overview

The RG_ROW_SEGMENT_SEQUENCES table resides in the RG schema, which belongs to the Application Report Generator (RG) product within Oracle E-Business Suite. It stores the assignment of individual report segments to row orders, effectively defining how columns and segment names are laid out, sequenced, and displayed for a given report structure. This makes it a configuration-level table that governs report output formatting rather than transactional or financial data.

Because the table is anchored by a single primary key column (ROW_SEGMENT_SEQUENCE_ID) and also carries one foreign key referencing RG_ROW_ORDERS.ROW_ORDER_ID, the heuristic Data Vault classification is satellite-leaning. From a modeling perspective, it behaves as a satellite attached to the RG_ROW_ORDERS hub/link structure, holding descriptive, versioned attributes about segment placement. It is not a hub itself, since it owns no independent business key beyond its parent row order context.

Key Information Stored

Among the 31 documented columns, the most significant are the identifying and layout-related attributes:

• ROW_SEGMENT_SEQUENCE_ID — the surrogate primary key (RG_ROW_SEGMENT_SEQUENCES_PK / U1), uniquely identifying each assignment row.
• ROW_ORDER_ID — foreign key to RG_ROW_ORDERS; the parent row order to which this segment belongs.
• STRUCTURE_ID — identifies the report structure context, forming part of the business unique keys U2 and U3.
• SEGMENT_SEQUENCE — the ordinal position of the segment; part of the business unique key U2.
• SEGMENT_NAME — the internal name of the segment being placed.
• APPLICATION_COLUMN_NAME — the source application column; part of business unique key U3, tying the segment to actual report data columns.
• APPLICATION_ID — the application owning the segment or column.
• SEG_ORDER_TYPE and SEG_DISPLAY_TYPE — control ordering behavior and how the segment is displayed in output.
• SEGMENT_WIDTH — defines the display width allocated to the segment.
• CONTEXT — descriptive context for the segment definition.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE15.

The three unique indexes clarify the business keys: U1 on the surrogate ID, U2 on (ROW_ORDER_ID, STRUCTURE_ID, SEGMENT_SEQUENCE), and U3 on (ROW_ORDER_ID, STRUCTURE_ID, APPLICATION_COLUMN_NAME).

Common Use Cases and Queries

Typical use cases include auditing how report columns are sequenced, diagnosing report layout issues, and migrating RG definitions between environments. A common query retrieves all segments for a row order in sequence:

• SELECT segment_sequence, segment_name, application_column_name, seg_display_type FROM rg_row_segment_sequences WHERE row_order_id = :p_row_order_id ORDER BY segment_sequence;
• Joining to RG_ROW_ORDERS to reconcile row orders against their segment assignments.
• Detecting duplicate sequence or duplicate column assignments via U2 and U3 constraints.
• Reporting on segment widths and display types for layout validation before report regeneration.

Related Objects

The most significant dependencies are:

• RG_ROW_ORDERS — parent table joined via ROW_SEGMENT_SEQUENCES.ROW_ORDER_ID = RG_ROW_ORDERS.ROW_ORDER_ID; the principal FK relationship.
• The RG structure and column definition tables referenced by STRUCTURE_ID and APPLICATION_COLUMN_NAME, which populate segment and column metadata.
• RG report generation views and concurrent programs in the Application Report Generator module that consume these sequence definitions to render output.
• RG schema indexes RG_ROW_SEGMENT_SEQUENCES_PK, _U1, _U2, and _U3, which enforce identity and business uniqueness.