Search Results rg_row_orders_uk1

Overview

The RG_ROW_ORDERS table is a core repository for row order definitions within the Application Report Generator (RG) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. The Application Report Generator is a legacy tool used to create custom reports based on the structure of key flexfields. This table serves as the master definition table for the specific sequencing and ordering rules applied to rows of data in these generated reports. It is a foundational metadata object that dictates how segment values from a flexfield structure are organized in the final report output, ensuring data is presented in a consistent and meaningful hierarchical or sorted order.

Key Information Stored

The table stores metadata that defines a named row ordering rule. Its primary columns include ROW_ORDER_ID, the unique internal primary key identifier. The NAME column stores the user-defined name for the row order definition, which is unique within a specific APPLICATION_ID. The APPLICATION_ID links the definition to an Oracle EBS application, such as General Ledger or Inventory. Critical columns for flexfield context are ID_FLEX_CODE_11I (the flexfield code, e.g., 'GL#') and STRUCTURE_ID, which together identify the specific key flexfield structure to which this row order applies. This structure is enforced via a foreign key relationship to the FND_ID_FLEX_STRUCTURES table. The table's unique key constraint (RG_ROW_ORDERS_UK1) on NAME and APPLICATION_ID prevents duplicate definition names within the same application.

Common Use Cases and Queries

The primary use case is the creation and management of custom reporting formats where data must be sorted or parent-child relationships must be visualized according to flexfield segment hierarchies. For instance, a report on Accounting Flexfield combinations may need rows ordered by Company, then Department, then Account. A row order definition in RG_ROW_ORDERS would establish this sequence. Common queries involve listing all row order definitions for a specific application or flexfield, or troubleshooting report generation issues. A sample query to retrieve basic definition data is:

• SELECT name, application_id, id_flex_code_11i, structure_id FROM rg.rg_row_orders WHERE application_id = 101 ORDER BY name;

Another critical pattern is joining to RG_ROW_SEGMENT_SEQUENCES to see the detailed ordering of individual segments within a specific row order definition.

Related Objects

RG_ROW_ORDERS is centrally linked to several key objects in the Report Generator schema. It is directly referenced by RG_REPORTS and RG_REPORT_REQUESTS, which store report definitions and runtime instances, respectively, linking them to a specific row order. The detailed sequencing rules for each segment within a row order are stored in the child table RG_ROW_SEGMENT_SEQUENCES, using ROW_ORDER_ID as the foreign key. As noted in the metadata, its definition is also tied to the flexfield metadata via a foreign key to FND_ID_FLEX_STRUCTURES on the combination of APPLICATION_ID, ID_FLEX_CODE_11I, and STRUCTURE_ID, ensuring referential integrity with the EBS flexfield architecture.