Search Results rg_report_standard_axes




Overview
Explore in AI Chat

Overview

The RG_REPORT_STANDARD_AXES table is a core data dictionary object within the Application Report Generator (RG) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a repository for predefined "amount types" that define the fundamental axes of a financial report, specifically the data categories used to structure rows and columns. This table functions as a master catalog of standard, reusable financial dimensions—such as Actual, Budget, or Encumbrance amounts—which report designers can select when building report templates. Its role is to ensure consistency and standardization in financial reporting across the enterprise by providing a controlled set of data points for report axes.

Key Information Stored

While the provided ETRM excerpt does not list all column definitions, the primary and unique keys, along with the description, indicate the critical data elements. The table's structure centers on the identification and naming of standard axes. The STANDARD_AXIS_ID column is the primary key, a unique numeric identifier for each axis record. The STANDARD_AXIS_NAME column is a unique key, storing the descriptive name of the amount type (e.g., "Current Period Actual"). The presence of foreign key columns STANDARD_AXIS1_ID and STANDARD_AXIS2_ID that reference the table's own primary key suggests a hierarchical or relational structure may exist within the standard axes definitions, allowing for complex axis groupings or dependencies.

Common Use Cases and Queries

The primary use case is the administrative setup and maintenance of the Report Generator's foundational components. System administrators or implementation consultants may query this table to audit available standard axes or to troubleshoot reporting issues. A common query would involve joining this table with the RG_REPORT_AXES table to see which standard axes are deployed in active report definitions. For instance, a query to list all standard axes and any report axes that use them would follow this pattern:

  • SELECT s.STANDARD_AXIS_NAME, a.REPORT_AXIS_NAME
  • FROM RG_REPORT_STANDARD_AXES s, RG_REPORT_AXES a
  • WHERE s.STANDARD_AXIS_ID = a.STANDARD_AXIS_ID(+);

Another critical scenario involves understanding axis hierarchies, which can be explored via a self-join on the STANDARD_AXIS1_ID and STANDARD_AXIS2_ID columns to parent records.

Related Objects

The RG_REPORT_STANDARD_AXES table has documented relationships with several key objects in the Report Generator schema, as defined by its foreign key constraints.

  • RG_REPORT_AXES: This is the primary consumer. The RG_REPORT_AXES.STANDARD_AXIS_ID column is a foreign key referencing RG_REPORT_STANDARD_AXES.STANDARD_AXIS_ID. This links a specific, configured report axis to its standard definition.
  • Self-Referencing Relationships: The table contains two internal foreign keys, creating a recursive structure.
    • RG_REPORT_STANDARD_AXES.STANDARD_AXIS1_ID references RG_REPORT_STANDARD_AXES.STANDARD_AXIS_ID
    • RG_REPORT_STANDARD_AXES.STANDARD_AXIS2_ID references RG_REPORT_STANDARD_AXES.STANDARD_AXIS_ID
    These relationships allow a standard axis to be logically related to two other standard axes, potentially for building composite or comparative axes.