Results for “rg_report_parameters”

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

Overview

RG_REPORT_PARAMETERS is a table in the RG (Application Report Generator) schema within Oracle EBS 12.1.1 and 12.2.2. Its documented description is "Assignments of budgets, encumbrances, and currencies to reports." It stores the parameter definitions that drive the Financial Statement Generator-style reporting functionality historically associated with the RG product, binding a report's parameter set to specific budget versions, encumbrance types, and currency definitions.

The table carries 32 documented columns and is classified under a heuristic Data Vault model as a link. This classification reflects its structure: it holds foreign key references to multiple parent entities (GL_BUDGET_VERSIONS, GL_ENCUMBRANCE_TYPES, and three references into FND_CURRENCIES), making it an associative entity that resolves relationships between report parameter sets and those reference objects rather than acting as an independent hub.

Key Information Stored

The primary key is RG_REPORT_PARAMETERS_PK, composed of PARAMETER_SET_ID, DATA_TYPE, and PARAMETER_NUM. A unique index, RG_REPORT_PARAMETERS_U1, is defined on the same three columns, making this combination the documented business-key candidate as well as the physical identifier for each row.

• PARAMETER_SET_ID — Groups individual parameters into a set and links the assignment to a report.
• DATA_TYPE — Identifies the kind of parameter (for example, budget, encumbrance, or currency), pairing with PARAMETER_NUM to form the key.
• PARAMETER_NUM — Sequence number positioning the parameter within its set.
• PARAMETER_ID — The referenced identifier for budget versions or encumbrance types, depending on DATA_TYPE.
• UNIT_OF_MEASURE_ID_11I — Currency reference column joined to FND_CURRENCIES.
• ENTERED_CURRENCY — The transaction/entered currency for the report parameter.
• LEDGER_CURRENCY — The ledger (functional) currency associated with the parameter.
• CURRENCY_TYPE and CURRENCY_TYPE_11I — Currency classification indicators.
• PERIOD_NUM — Period reference used in the report assignment.
• FISCAL_YEAR_OFFSET — Offset applied to the fiscal year for period selection.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for audit tracking.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments for extensibility.

Common Use Cases and Queries

A typical use case is determining which currencies and budgets have been assigned to a given report parameter set. Because the search term FND_CURRENCIES was associated with this object, currency-resolution queries are common. The following pattern joins the three currency references to FND_CURRENCIES:

• Resolving entered currency: SELECT rp.PARAMETER_SET_ID, fc.NAME FROM RG_REPORT_PARAMETERS rp, FND_CURRENCIES fc WHERE rp.ENTERED_CURRENCY = fc.CURRENCY_CODE;
• Resolving ledger currency: substitute rp.LEDGER_CURRENCY for the join.
• Resolving the unit-of-measure currency via rp.UNIT_OF_MEASURE_ID_11I.
• Listing budgets assigned to a report by joining PARAMETER_ID to GL_BUDGET_VERSIONS.
• Listing encumbrance assignments by joining PARAMETER_ID to GL_ENCUMBRANCE_TYPES.
• Filtering by DATA_TYPE to separate budget, encumbrance, and currency rows within a parameter set.

These queries support reporting diagnostics, migration validation, and audit of report configuration.

Related Objects

The documented foreign keys tie RG_REPORT_PARAMETERS to the following reference tables, which are its most significant related objects:

• GL_BUDGET_VERSIONS — joined via PARAMETER_ID; supplies budget version definitions.
• GL_ENCUMBRANCE_TYPES — joined via PARAMETER_ID; supplies encumbrance type definitions.
• FND_CURRENCIES — referenced three times, via UNIT_OF_MEASURE_ID_11I, ENTERED_CURRENCY, and LEDGER_CURRENCY, providing the currency master data central to the searched term.

Given the heuristic link classification, the parent tables above act as the hubs this table connects, and the RG_REPORT_PARAMETERS_PK composite key governs all downstream joins.