Results for “exception_id”

4 results




Overview
Explore in AI Chat

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

Overview

RG_REPORT_EXCEPTIONS is a table in the RG (Application Report Generator) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to store exception conditions for report columns. In the Application Report Generator, when a report is defined over a set of axes, individual measure columns frequently require special handling—values that fall outside an expected threshold, violate a conditional rule, or must be substituted with a constant. RG_REPORT_EXCEPTIONS persists those rules as rows, each identified by a surrogate key and linked back to the axis set and axis sequence on which the exception applies.

A Data Vault classification heuristic applied to the foreign key structure labels this table as satellite-leaning. In Data Vault terms, a satellite captures descriptive, time-variant attributes about a parent business key rather than the key itself. Here, the exception rule (condition and constant) behaves as descriptive context hanging off the axis definition in RG_REPORT_AXES, which is consistent with that classification. The classification is a modeling suggestion only; the table is a conventional relational child of RG_REPORT_AXES in the EBS data model.

The table comprises 27 documented columns in the 12.2.2 physical schema. The majority are the standard EBS "who columns" and the fifteen DESCRIPTIVE flexfield attribute columns (ATTRIBUTE1 through ATTRIBUTE15), which means the effective business payload is concentrated in a small number of functional columns.

Key Information Stored

  • EXCEPTION_ID — the surrogate primary key, enforced by RG_REPORT_EXCEPTIONS_PK. Every exception rule is uniquely identified by this system-generated value; it carries no business meaning.
  • AXIS_SET_ID — foreign key to RG_REPORT_AXES, identifying the axis set to which the exception belongs. Together with AXIS_SEQ it forms the business relationship to the parent axis definition.
  • AXIS_SEQ — the axis sequence within the set, pinpointing the specific axis (report dimension or column position) governed by the exception.
  • CONDITION — the logical test that triggers the exception, for example a comparison against a threshold or a null condition. This is the core business rule text or expression.
  • CONSTANT — the replacement value applied when CONDITION evaluates true, allowing a fixed literal to be substituted for the computed column value.
  • APPLICATION_ID — identifies the owning application, supporting multi-application coexistence within a single RG schema.
  • CONTEXT — the descriptive flexfield context segment, enabling application-specific extension of the exception record.
  • ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments available for customer-specific or localization-specific exception attributes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified each rule and when, essential for change tracking and audit reporting.

The natural business key is the combination of AXIS_SET_ID and AXIS_SEQ rather than EXCEPTION_ID; the metadata documents only the surrogate primary key RG_REPORT_EXCEPTIONS_PK.

Common Use Cases and Queries

Typical use is auditing or migrating report definitions. A developer tracing why a report column displays a substituted value joins the exception table to its parent axis set:

  • Retrieve all exceptions for a given axis set: SELECT exception_id, axis_seq, condition, constant FROM rg_report_exceptions WHERE axis_set_id = :axis_set_id ORDER BY axis_seq;
  • Join to the parent axis definition: SELECT e.axis_seq, e.condition, e.constant FROM rg_report_exceptions e, rg_report_axes a WHERE e.axis_set_id = a.axis_set_id AND e.axis_seq = a.axis_seq;
  • Find exceptions carrying flexfield extensions: filter on context and attribute1…attribute15 to locate customer-specific rules.
  • Audit recent rule changes using last_update_date and last_updated_by within a date range.
  • Verify each exception has associated flag rows by joining to RG_REPORT_EXCEPTION_FLAGS on exception_id, a useful integrity check before report generation.

Related Objects

  • RG_REPORT_AXES — parent table; RG_REPORT_EXCEPTIONS.AXIS_SET_ID and AXIS_SEQ reference it. The primary join path for resolving the exception's context.
  • RG_REPORT_EXCEPTION_FLAGS — child table referencing RG_REPORT_EXCEPTIONS.EXCEPTION_ID, storing flag settings associated with each exception rule.
  • RG_REPORT_EXCEPTIONS_PK — the primary key constraint on EXCEPTION_ID.
  • Additional RG report definition and template tables (for example report, axis, and column definition objects) participate in the same generation model and are commonly queried alongside this table when diagnosing report output.
  • Concurrent program and report definition APIs in the RG module read these rows at report execution time.

Because the RG module is a legacy reporting facility, write access should be restricted to the report definition UI or supported APIs rather than direct DML, preserving the referential integrity enforced by the documented foreign keys.