Results for “rg_constant_periods_v”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
RG_CONSTANT_PERIODS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite and delivered as part of the RG (Application Report Generator) product. The view exposes a filtered subset of the report parameter definitions maintained in RG_REPORT_PARAMETERS, restricted to parameters whose DATA_TYPE is equal to 'I'. Within the Oracle EBS reporting architecture, such parameters correspond to constant or period-based values that a report definition resolves at execution time rather than values entered interactively by the user at the point of submission.
The view is significant because it isolates the parameters that carry a period orientation, including the FISCAL_YEAR_OFFSET column, which is the attribute most often sought when users search for fiscal_year_offset. By separating these parameters from the broader population of report parameters, RG_CONSTANT_PERIODS_V provides a stable interface for reports, concurrent programs, and custom extensions that need to enumerate reporting periods relative to a fiscal calendar. In EBS 12.1.1 and 12.2.2, the view is reported as VALID, confirming that its definition and dependent objects are consistent in the dictionary.
Underlying Base Objects
The view is defined over a single base object, RG_REPORT_PARAMETERS, referenced through a public synonym resolving to the APPS-owned table. The defining query selects all columns of interest from that table aliased as PARAM, applying the predicate PARAM.DATA_TYPE = 'I'. In addition to the persistent table columns, the SELECT list includes PARAM.ROWID aliased as ROW_ID, which supplies a unique row identifier for each returned record even though the source table does not expose a natural single-column primary key in the view definition.
Because the view is a straightforward projection with a single filter and no joins, it inherits the indexing and partitioning characteristics of RG_REPORT_PARAMETERS. Query performance therefore depends on how efficiently the DATA_TYPE predicate can be resolved, and on the selectivity of any additional predicates supplied by the caller, such as PARAMETER_SET_ID or PERIOD_NUM.
Key Columns
- ROW_ID — the physical row identifier of the underlying record in RG_REPORT_PARAMETERS; useful for addressing individual parameter rows.
- PARAMETER_SET_ID — identifies the parameter set to which the constant period parameter belongs, linking the row to a specific report definition.
- PARAMETER_NUM — the ordinal position or reference number of the parameter within its set.
- PERIOD_NUM — the period number associated with the parameter, used when the parameter denotes a specific accounting or reporting period.
- FISCAL_YEAR_OFFSET — the offset, expressed in fiscal years, applied when resolving the period relative to the report run date or another reference period. This column is central to period-shifting logic in report definitions.
- DATA_TYPE — the discriminator column; every row returned by this view has the value 'I'.
- CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments available for extending the parameter definition without schema change.
- Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY provide standard EBS who-column auditing.
Common Use Cases and Queries
The most frequent use of this view is audit and troubleshooting of report parameter configurations that depend on fiscal period arithmetic. Analysts query it to confirm how a given report set derives prior-year or future-year periods, and to verify that FISCAL_YEAR_OFFSET values are populated as expected. Custom concurrent programs and report templates also join the view to RG_REPORT_PARAMETERS or to report definition tables to resolve period parameters dynamically.
A representative query listing constant period parameters for a parameter set:
SELECT parameter_set_id, parameter_num, period_num, fiscal_year_offset, last_update_date FROM apps.rg_constant_periods_v WHERE parameter_set_id = :p_set_id ORDER BY parameter_num;
To locate all parameters carrying a non-zero fiscal year offset:
SELECT parameter_set_id, parameter_num, period_num, fiscal_year_offset FROM apps.rg_constant_periods_v WHERE fiscal_year_offset <> 0 ORDER BY parameter_set_id, parameter_num;
Because the view exposes ROW_ID and the standard audit columns, it can also be used in diagnostic queries that compare creation and last-update timestamps to determine when period parameter configuration changed. Queries should always qualify the view with the APPS schema or rely on the synonym, and should filter on PARAMETER_SET_ID wherever possible to minimize the volume of rows scanned from RG_REPORT_PARAMETERS.
-
View: RG_CONSTANT_PERIODS_V 12.2.2
APPS.RG_CONSTANT_PERIODS_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 →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - RG Tables and Views 12.1.1
-
eTRM - RG Tables and Views 12.2.2
-
12.2.2 DBA Data 12.2.2
-
eTRM - RG Tables and Views 12.1.1
-
eTRM - RG Tables and Views 12.2.2
-
12.1.1 DBA Data 12.1.1