Search Results pa_forecasting_period_type




Overview
Explore in AI Chat

Overview

APPS.PA_FCST_PERIODS_TMP_V is a reporting view in Oracle EBS Projects (PA) that exposes the complete set of forecasting periods available for use in project forecasting and planning. Its defining characteristic is that it is conditional: the rows returned depend on the value of the profile option PA_FORECASTING_PERIOD_TYPE, which is the exact term the user searched for. When this profile option is set to 'GL', the view returns periods sourced from the General Ledger calendar. When it is set to 'PA', the view returns periods sourced from the Oracle Projects period calendar.

Because the profile option governs the period source, the view acts as a single normalized access point for forecasting periods regardless of whether an implementation runs Projects periods aligned to GL periods or maintains its own PA-defined periods. This makes it central to forecasting UIs, period-selection LOVs, and any process that must enumerate valid forecast periods in a consistent shape.

Underlying Base Objects

The view is a UNION ALL of two branches, each governed by the profile option check.

Note that several referenced objects are synonyms or views over the base GL and PA tables, reflecting standard EBS layering.

Key Columns

  • Source indicator: the literal 'GL' or 'PA' identifying which branch produced the row.
  • PERIOD_YEAR: the fiscal/calendar year of the period.
  • PERIOD_NAME: the period identifier (for example, a GL period name such as JAN-25).
  • START_DATE / END_DATE: the GL start and end dates of the period in the GL branch; the PA branch returns PA_START_DATE and PA_END_DATE aliased to the same positions, giving a uniform date range across both sources.

The consistent column shape across both branches is what allows downstream forecast logic to iterate periods without branching on the profile option itself.

Common Use Cases and Queries

Typical scenarios include populating a forecast period LOV, validating a user-entered forecast period, and driving period-based forecast rollups. A simple query lists all valid forecast periods:

  • SELECT period_name, period_year, start_date, end_date FROM apps.pa_fcst_periods_tmp_v ORDER BY start_date;
  • Restricting to the current year: add WHERE period_year = TO_CHAR(SYSDATE,'YYYY').
  • Filtering by source: WHERE source = 'PA' (or 'GL') to isolate the active calendar branch.

Because the profile option is resolved at query time, the same SQL behaves correctly under either configuration, which is the primary reason this view exists.