Search Results rg_dss_system_seg_order_u2

Overview

RG.RG_DSS_SYSTEM_SEG_ORDER is a maintenance and configuration table in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, owned by the RG schema. It defines the ordering and mapping of key flexfield segments that participate in the data subset definition of a system. Each row associates a system (the financial data set) with a specific application column, assigns it a positional sequence, and links that column to the underlying key flexfield code and structure number. The table therefore acts as a bridge between the abstract data model of a system definition and the concrete column names used by Oracle Applications flexfield structures.

From a Data Vault modeling perspective, the metadata classifies this table as satellite-leaning. The parent reference, SYSTEM_ID, points to RG_DSS_SYSTEMS, indicating that the natural business hub or parent entity is the system definition, while RG_DSS_SYSTEM_SEG_ORDER carries descriptive, system-specific attributes about segment ordering. The classification is a heuristic suggestion rather than a mandated design.

The object is flagged in Oracle documentation as internal use only; Oracle Corporation does not support direct application data access except through standard Oracle Applications programs. Developers and support personnel should treat it as a configuration detail rather than as a supported integration point.

Key Information Stored

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

• SYSTEM_ID — NUMBER(15), mandatory. The financial data set defining column and the primary foreign key to RG_DSS_SYSTEMS.
• SEQUENCE — NUMBER(15). Position of the column in the sort order, establishing how segments are ordered within the system.
• APPLICATION_COLUMN_NAME — VARCHAR2(30). The name of the column that contains the segment, tying the definition to a physical or logical application column.
• ID_FLEX_CODE — Key flexfield code identifying the flexfield to which the ordered segment belongs.
• ID_FLEX_NUM — NUMBER(15). Key flexfield structure number, qualifying the flexfield code to a specific structure.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing audit trail information.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive Flexfield context and segment columns available for extensibility.

The surrogate-style primary key is RG_DSS_SYSTEM_SEG_ORDER_PK, composed of SYSTEM_ID and SEQUENCE. Two unique indexes document the business-key candidates: RG_DSS_SYSTEM_SEG_ORDER_U1 on (SYSTEM_ID, SEQUENCE), and RG_DSS_SYSTEM_SEG_ORDER_U2 on (SYSTEM_ID, APPLICATION_COLUMN_NAME). A user searching for "rg_dss_system_seg_order_u2" is therefore looking at the unique constraint that enforces the one-column-per-system rule, preventing duplicate column mappings within a single system while still allowing the same column name under different systems.

Common Use Cases and Queries

The table is principally queried to reconstruct segment order for a given system, to audit duplicate column mappings, and to validate flexfield configuration. A typical lookup joins the order table to the system definition:

• Retrieve segments in order for one system: SELECT sequence, application_column_name, id_flex_code, id_flex_num FROM rg.rg_dss_system_seg_order WHERE system_id = :p_system_id ORDER BY sequence;
• Detect duplicate column mappings: query RG_DSS_SYSTEM_SEG_ORDER_U2 columns grouped by SYSTEM_ID and APPLICATION_COLUMN_NAME with a HAVING count greater than one.
• Cross-reference flexfield structure usage: join to key flexfield definitions using ID_FLEX_CODE and ID_FLEX_NUM.
• Audit changes over time using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the object is classified as Oracle Internal Use Only, queries should normally be executed through standard Oracle Applications programs or, where necessary, in a read-only reporting context.

Related Objects

The dominant documented relationship is the foreign key from RG_DSS_SYSTEM_SEG_ORDER.SYSTEM_ID to RG_DSS_SYSTEMS, which is the parent system definition table. Additional dependencies derive from the flexfield reference columns ID_FLEX_CODE and ID_FLEX_NUM, which correspond to Oracle Application Object Library key flexfield definition tables such as FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_SEGMENTS. The descriptive flexfield context and attribute columns follow standard FND descriptive flexfield conventions. Reporting and integration objects that consume subset system definitions, including the RG_DSS family of tables, may also rely on this table indirectly through SYSTEM_ID.