Search Results pa_fcst_periods_tmp




Overview
Explore in AI Chat

Overview

APPS.PA_FCST_PERIODIC_HDR_V is a reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that supplies the header (period-by-currency) matrix for periodic project forecasting. It is the view counterpart to the periodic forecast summary views and is invoked when a user requests the periodic forecast form from Oracle Projects. The user's search term, pa_fcst_periods_tmp, corresponds to a synonym on the base period driver within this view: the view's second UNION ALL branch selects period names directly from PA_FCST_PERIODS_TMP when no forecast value exists for the current global project forecast date range.

The view answers a narrow but important question: which project currency codes and which accounting periods should appear as columns and rows in the periodic forecast display, and whether forecast data exists at each intersection. It uses a UNION ALL to guarantee that every in-scope period is returned at least once, even when the summary view has no matching row, and it embeds DENSE_RANK analytic functions to produce the ordered X and Y axis sequence numbers consumed by the form's layout engine.

Underlying Base Objects

The documented referenced objects are FND_GLOBAL (package), PA_FCST_GLOBAL (package), PA_FCST_PERIODIC_SUM_V (view), PA_FCST_PERIODS_TMP (synonym), PA_PROJECTS_MAINT_UTILS (package), PA_UTILS (package), and DUAL (synonym).

  • PA_FCST_PERIODIC_SUM_V — the value source. It supplies PERIOD_NAME and project currency VALUE. It is joined to PA_FCST_PERIODS_TMP with an outer join on PERIOD_NAME, and self-joined on NVL(SUM.PERIOD_NAME, SUM1.PERIOD_NAME) so a currency axis is still emitted when the summary row is null.
  • PA_FCST_PERIODS_TMP — the period driver. It provides PERIOD_NAME, START_DATE, and END_DATE. The view filters it against the global project forecast start and end dates.
  • PA_FCST_GLOBAL — supplies GetProjFcstStartDate and GetProjFcstEndDate, the function calls that populate the inline FilterBy subquery. These bound the reporting window to the currently selected project forecast range.
  • FND_GLOBAL, PA_PROJECTS_MAINT_UTILS, PA_UTILS — supporting packages providing session context (ORG_ID, USER_ID) and Projects utility logic used throughout the forecasting forms.
  • DUAL — the source of the inline FilterBy row.

Key Columns

  • forecast_exists_flag — 'Y' when a periodic forecast value row exists, 'N' when the period is returned only from PA_FCST_PERIODS_TMP.
  • Y1 — the project currency code (PROJECT_CURRENCY_CODE), or NULL in the 'N' branch.
  • y1_seq — DENSE_RANK over Y1, ordering currencies on the vertical axis; the 'N' branch is hard-coded to 100000 so it sorts last.
  • X1 — the period name (PERIOD_NAME).
  • x1_seq — DENSE_RANK over PER.START_DATE, ordering periods on the horizontal axis.
  • value — the periodic forecast amount from PA_FCST_PERIODIC_SUM_V, or 0 in the 'N' branch.

Common Use Cases and Queries

The view is primarily consumed by Projects periodic forecast forms and by conversion or reconciliation reports that must confirm whether a forecast exists for a given period set. A typical diagnostic query lists all periods and flags gaps:

  • SELECT x1_seq, x1, y1_seq, y1, forecast_exists_flag, value FROM apps.pa_fcst_periodic_hdr_v ORDER BY x1_seq, y1_seq;
  • SELECT x1, y1, value FROM apps.pa_fcst_periodic_hdr_v WHERE forecast_exists_flag = 'Y';
  • SELECT COUNT(*) FROM apps.pa_fcst_periodic_hdr_v WHERE forecast_exists_flag = 'N';

Because the result set is driven by PA_FCST_GLOBAL.GetProjFcstStartDate and GetProjFcstEndDate, queries outside an active Projects session should set the same global context (via FND_GLOBAL / PA_FCST_GLOBAL initialization) or results will be filtered to the default range. When troubleshooting a missing period, inspect PA_FCST_PERIODS_TMP first; if the period is absent there, the header view cannot return it regardless of the summary view contents.