Search Results rg_report_exception_flags_pk

Overview

The RG_REPORT_EXCEPTION_FLAGS table is a core data object within the Application Report Generator (RG) module of Oracle E-Business Suite (EBS). Its primary function is to store the specific symbols or flags used to visually highlight exceptions within generated financial and managerial reports. This table operates as a child entity, linking the definition of an exception condition to the specific axes (or dimensions) of a report where that condition is evaluated. By storing these flags, the Report Generator enables users to quickly identify data points that fall outside predefined thresholds or rules, such as budget variances or performance outliers, directly within the report output.

Key Information Stored

The table's structure is designed to map exception indicators to their corresponding report axes. The critical columns, as indicated by its primary and foreign key constraints, are EXCEPTION_ID, AXIS_SET_ID, and AXIS_SEQ. The EXCEPTION_ID is the primary key and serves as the foreign key linking to the RG_REPORT_EXCEPTIONS table, which holds the master definition of the exception rule (e.g., "Revenue Variance > 10%"). The AXIS_SET_ID and AXIS_SEQ columns together form a composite foreign key relationship to the RG_REPORT_AXES table. This relationship specifies the exact dimensional context (such as a specific company, department, product line, or time period) within the report where the exception flag is applicable. The table likely contains additional columns to store the actual flag symbol (e.g., "***", "!", or a color code) and display attributes.

Common Use Cases and Queries

The primary use case is the runtime evaluation and display of exceptions during report execution. When the Report Generator processes data, it cross-references results against defined exceptions and uses the flags stored in this table to annotate the output. Administrators or developers may query this table to audit or maintain exception reporting setups. A common diagnostic query would join to parent tables to list all configured flags:

SELECT exc.exception_name, flag.* FROM rg_report_exception_flags flag, rg_report_exceptions exc WHERE flag.exception_id = exc.exception_id;

Another typical pattern retrieves the flags for a specific report axis set to understand dimensional coverage: SELECT * FROM rg_report_exception_flags WHERE axis_set_id = <value> ORDER BY axis_seq; Direct data manipulation in this table is rare; configuration is typically performed through the application's front-end interfaces.

Related Objects

The RG_REPORT_EXCEPTION_FLAGS table has defined dependencies on two key parent tables within the Report Generator schema, as per the provided metadata:

• RG_REPORT_EXCEPTIONS: This is the master table for exception rules. The relationship is established via the foreign key column RG_REPORT_EXCEPTION_FLAGS.EXCEPTION_ID referencing RG_REPORT_EXCEPTIONS. This join retrieves the rule's name, condition, and threshold.
• RG_REPORT_AXES: This table defines the report structures and dimensions. The relationship uses a composite foreign key from RG_REPORT_EXCEPTION_FLAGS (AXIS_SET_ID, AXIS_SEQ) to RG_REPORT_AXES. This join determines the specific row, column, or page axis where the exception flag is displayed.

The table itself is referenced by the RG_REPORT_EXCEPTION_FLAGS_PK primary key constraint on EXCEPTION_ID.