Results for “parameter_num”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
RG_CURRENCIES_V is an Oracle E-Business Suite view owned by the APPS schema and registered under the RG (Application Report Generator) product. Its ETRM status is VALID, and its description is documented simply as "10SC ONLY" — a reference to the Oracle 10SC (Self-Service/desktop-class reporting) lineage from which the Application Report Generator component descends. The view presents a filtered subset of report parameter definitions, specifically those rows in which the parameter's DATA_TYPE equals 'C', meaning the parameter represents a currency value. Rather than defining a new entity, RG_CURRENCIES_V acts as a convenience projection that allows report definitions, concurrent programs, and integration logic to resolve currency-typed parameters without scanning the full RG_REPORT_PARAMETERS table.
In Oracle EBS 12.1.1 and 12.2.2, the view sits within the report parameter framework used by Application Report Generator. It is not a transactional or master-data view; it is metadata-oriented, describing which currencies a given parameter set may accept and how those currencies are interpreted at report generation time. Because the object is APPS-owned and marked valid, it can be referenced from custom reports, value sets, and APIs that need to enumerate currency parameters attached to a report parameter set.
Underlying Base Objects
The view is defined over a single documented base object: RG_REPORT_PARAMETERS, referenced through a synonym. The defining query selects from RG_REPORT_PARAMETERS (aliased RG_PA) and applies the predicate RG_PA.DATA_TYPE = 'C'. Every row returned therefore corresponds to a currency-type report parameter. The columns exposed are a direct projection of the base table columns — ROW_ID (the ROWID of the base row), PARAMETER_SET_ID, audit columns, PARAMETER_NUM, CURRENCY_TYPE, ENTERED_CURRENCY, LEDGER_CURRENCY, DATA_TYPE, the DFF CONTEXT column, and sixteen ATTRIBUTE columns (ATTRIBUTE1 through ATTRIBUTE15, with the list as documented).
Note that ETRM records ROW_ID as selected via RG_PA.ROWID, meaning the view is non-key-preserving in the strict sense; ROW_ID is stable only for the lifetime of the underlying row. No joins to FND_CURRENCIES or GL currency tables are present in the documented view text, so currency validation is not performed by the view itself.
Key Columns
- PARAMETER_SET_ID — Identifies the report parameter set to which the currency parameter belongs; the primary grouping key for consumers.
- PARAMETER_NUM — The positional number of the parameter within the set, used for ordering and prompt sequencing.
- CURRENCY_TYPE — The column most relevant to users searching for "currency_type"; classifies how the currency value is treated (for example, entered versus ledger-relative currency semantics).
- ENTERED_CURRENCY — The currency in which the user enters the parameter value.
- LEDGER_CURRENCY — The ledger currency associated with the parameter, used when amounts must be interpreted in the functional currency.
- DATA_TYPE — Always 'C' in this view; it is the filter that defines the view's purpose.
- CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns for extensible parameter attributes.
- Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN track who defined or changed the parameter.
Common Use Cases and Queries
Typical uses include building concurrent program prompts that must expose only currency parameters, auditing which reports accept entered versus ledger currencies, and feeding custom report logic that branches on CURRENCY_TYPE. A basic query lists all currency parameters for a parameter set:
SELECT parameter_num, currency_type, entered_currency, ledger_currency FROM apps.rg_currencies_v WHERE parameter_set_id = :p_set ORDER BY parameter_num;
To inspect extensible attributes: SELECT parameter_num, context, attribute1, attribute2 FROM apps.rg_currencies_v WHERE parameter_set_id = :p_set;. Because the view is thin and unfiltered beyond DATA_TYPE, queries should always constrain on PARAMETER_SET_ID for performance, and ROW_ID should not be persisted across transactions.
-
View: RG_CURRENCIES_V 12.1.1
10SC ONLY
APPS.RG_CURRENCIES_V·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
View: RG_BUDGETS_V 12.1.1
10SC ONLY
APPS.RG_BUDGETS_V·↳ GL_BUDGETS·↳ GL_BUDGET_VERSIONS·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
Assignments of budgets, encumbrances, and currencies to reports
-
Row and column definitions
-
View: RG_REPORT_AXES_V 12.2.2
APPS.RG_REPORT_AXES_V·↳ RG_LOOKUPS·↳ RG_REPORT_AXES·↳ RG_REPORT_STANDARD_AXES_TL·Explore RG module →
-
View: RG_CONSTANT_PERIODS_V 12.2.2
APPS.RG_CONSTANT_PERIODS_V·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
View: RG_ENCUMBRANCES_V 12.2.2
10SC ONLY
APPS.RG_ENCUMBRANCES_V·↳ GL_ENCUMBRANCE_TYPES·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
View: RG_CURRENCIES_V 12.2.2
10SC ONLY
APPS.RG_CURRENCIES_V·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
View: RG_CONSTANT_PERIODS_V 12.1.1
APPS.RG_CONSTANT_PERIODS_V·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
Assignments of budgets, encumbrances, and currencies to reports
-
View: RG_BUDGETS_V 12.2.2
10SC ONLY
APPS.RG_BUDGETS_V·↳ GL_BUDGETS·↳ GL_BUDGET_VERSIONS·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
View: RG_ENCUMBRANCES_V 12.1.1
10SC ONLY
APPS.RG_ENCUMBRANCES_V·↳ GL_ENCUMBRANCE_TYPES·↳ RG_REPORT_PARAMETERS·Explore RG module →
-
Row and column definitions
-
View: RG_REPORT_AXES_V 12.1.1
APPS.RG_REPORT_AXES_V·↳ RG_LOOKUPS·↳ RG_REPORT_AXES·↳ RG_REPORT_STANDARD_AXES_TL·Explore RG module →