Results for “rg_row_orders”

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

Overview

RG_ROW_ORDERS is a table in the RG (Application Report Generator) schema of Oracle E-Business Suite, holding row order definitions used by the Oracle Report Generator component. RG_ROW_ORDERS serves as a repository for named row order configurations — business rules that determine how rows are ranked, sorted, and sequenced within a generated report output. It is a candidate hub-leaning object in a Data Vault model: the surrogate key ROW_ORDER_ID and the business key (NAME, APPLICATION_ID) form the natural reference frame, with descriptive attributes such as ROW_RANK_TYPE, STRUCTURE_ID, and the DFF columns best modeled as satellite attributes.

Key Information Stored

RG_ROW_ORDERS contains 32 documented columns at ETRM 12.2.2. The core identifying columns are:

• ROW_ORDER_ID — the numeric surrogate primary key (RG_ROW_ORDERS_PK), also carried on unique index RG_ROW_ORDERS_U1.
• NAME — the user-defined row order name, the first column of the business-key unique index RG_ROW_ORDERS_U2.
• APPLICATION_ID — the owning application, second column of RG_ROW_ORDERS_U2, scoping the NAME and creating foreign-key lineage to key flexfield definitions.
• ROW_RANK_TYPE — the ranking method applied to rows (e.g., ascending/descending rank semantics).
• ID_FLEX_CODE_11I, ID_FLEX_CODE, STRUCTURE_ID — key flexfield code and structure identifiers, used to bind the row order to a particular segment structure.
• DESCRIPTION — free-text description of the row order.
• COLUMN_NUMBER, COLUMN_NAME, CONTEXT — positional and descriptive field attributes that define which column the ordering applies to.
• ATTRIBUTE1–ATTRIBUTE15 — the standard 15 descriptive flexfield (DFF) columns for customer-defined extensions.
• SECURITY_FLAG — controls whether report access is restricted for this row order.
• Standard who-columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide audit history.

Common Use Cases and Queries

The table is typically queried to resolve which row order applies to a report or request, or to validate that a named order exists in a given application. A representative lookup:

• Resolve a row order by key: SELECT ROW_ORDER_ID, NAME, ROW_RANK_TYPE, STRUCTURE_ID FROM RG.RG_ROW_ORDERS WHERE NAME = :p_name AND APPLICATION_ID = :p_app;
• Find orders bound to a key flexfield structure: join on ID_FLEX_STRUCTURES via ID_FLEX_CODE_11I and STRUCTURE_ID to confirm the segment source.
• Audit usage across reports and requests by joining ROW_ORDER_ID to RG_REPORTS and RG_REPORT_REQUESTS.
• Map downstream ordering: join RG_ROW_SEGMENT_SEQUENCES on ROW_ORDER_ID to list the ordered segment set. Directly querying the UK1 index (RG_ROW_ORDERS_UK1/U2) via NAME + APPLICATION_ID is the fastest access path for single-record lookups.

Related Objects

• RG_REPORTS — references ROW_ORDER_ID; a report's default row-order definition.
• RG_REPORT_REQUESTS — references ROW_ORDER_ID; runtime requests inherit the row order.
• RG_ROW_SEGMENT_SEQUENCES — references ROW_ORDER_ID; the ordered child sequence lines.
• FND_ID_FLEX_STRUCTURES — referenced by APPLICATION_ID + ID_FLEX_CODE_11I + STRUCTURE_ID; supplies the key flexfield structure definition.
• FND_APPLICATION — implicit lookup for the owning APPLICATION_ID.