Results for “period_type”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_REP_PERIOD_YEARS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) application. Its purpose, as documented in the ETRM metadata, is to display the list of period years that correspond to a given period type. The view provides a consolidated lookup of available years across the different calendar and period-type sources used by Oracle Projects reporting, allowing the year selection to be driven by the period type requested by the user or the reporting engine.

In both Release 12.1.1 and 12.2.2 the view carries a VALID status and is defined entirely over other reporting views rather than over base tables. It functions as a lightweight unification layer that normalizes year values originating from the General Ledger calendar, the Projects calendar and other period-type specific sources into a single result set keyed by a two-character period type. Because it is a simple UNION of existing views, it introduces negligible overhead and requires no materialization.

Underlying Base Objects

PA_REP_PERIOD_YEARS_V is defined as a UNION of SELECT statements over three documented views, each supplying the PERIOD_YEAR for a particular period type:

Each contributing view is queried with a literal period-type tag hard-coded in the SELECT list, so the UNION ALL effectively produces a combined list of period-type/period-year pairs. The dependency chain therefore runs from PA_REP_PERIOD_YEARS_V down to these three views, which in turn resolve against the underlying GL and PA calendar tables. Because the period type is assigned as a constant rather than joined from a table, the supported period types are fixed at design time: GL, PA, QR, YR and GE.

Key Columns

The view exposes two columns:

  • PERIOD_TYPE — a character literal identifying the reporting period type. Documented values include GL (General Ledger period type), PA (Projects period type), QR (quarterly), YR (yearly) and GE (a calendar-based period type resolved through PA_REP_YEAR_CAL_V).
  • PERIOD_YEAR — the period year value associated with that period type, returned from the corresponding source view.

No other columns are documented. Consumers should treat PERIOD_TYPE as the filtering/driving key and PERIOD_YEAR as the displayed or selectable value.

Common Use Cases and Queries

The primary use case is populating period-year list-of-values selections in Oracle Projects reporting, where the list of selectable years depends on the period type chosen earlier in the reporting flow. A typical query filters by period type:

  • SELECT period_year FROM pa_rep_period_years_v WHERE period_type = 'PA' ORDER BY period_year;
  • SELECT period_type, period_year FROM pa_rep_period_years_v ORDER BY period_type, period_year;

A second scenario is validating which period types are available for a given reporting request, for example to confirm that a quarterly or yearly selection is valid before launching a report. Because the view is read-only and defined over other views, it is safe to query directly from custom reports, concurrent program parameters and BI Publisher data models in both 12.1.1 and 12.2.2. Where performance is a concern, note that each period type is sourced from a distinct view, so filtering on PERIOD_TYPE allows the optimizer to restrict the contributing branches and avoid scanning unnecessary year ranges.