Results for “pa_fcst_periods_tmp_v”

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

Overview

The PA_FCST_PERIODS_TMP_V view is a Projects (PA) module database object registered in the APPS schema. It presents period-type reference information — specifically the period name together with its start and end dates — for use in the Oracle Projects forecasting flow. The view is a UNION-based construct that surfaces two distinct period sources depending on the value of the profile option PA_FORECASTING_PERIOD_TYPE: General Ledger (GL) accounting periods, or Oracle Projects (PA) periods. Because the profile option governs which branch of the UNION returns rows, the view functions as a runtime switch that aligns the forecast period list with the customer's configured forecasting calendar. In Oracle EBS 12.1.1 and 12.2.2, it supports forecasting submissions, period selection lists, and validation logic in the projects forecasting user interface and related reports. The suffix "_TMP_V" and the use of the current profile value indicate the view is intended as a transient, session-scoped lookup rather than a persistent reporting source.

Underlying Base Objects

The documented metadata lists the following referenced objects: FND_PROFILE (package), GL_DATE_PERIOD_MAP, GL_LOOKUPS, GL_PERIODS, GL_PERIOD_STATUSES, GL_SETS_OF_BOOKS, PA_IMPLEMENTATIONS, PA_PERIODS_V, and PA_PERIOD_PROCESS_PKG. The GL branch joins PA_IMPLEMENTATIONS, GL_SETS_OF_BOOKS, GL_PERIODS, GL_PERIOD_STATUSES, GL_LOOKUPS and GL_DATE_PERIOD_MAP, filtering on the active set of books, the GL accounting period type, valid closing statuses (C, F, N, O, P from the CLOSING_STATUS lookup type), and the PA application ID resolved through PA_PERIOD_PROCESS_PKG.APPLICATION_ID. The PA branch reads PA_PERIODS_V directly. In both directions, FND_PROFILE.VALUE('PA_FORECASTING_PERIOD_TYPE') determines which result set is populated.

Key Columns

• PERIOD_TYPE — Literal identifier ('GL' or 'PA') indicating which calendar branch supplied the row.
• PERIOD_YEAR — The fiscal or project period year derived from GL_PERIODS or PA_PERIODS_V.
• PERIOD_NAME — The period name (for example, a GL period name or Projects period name) used for display and selection.
• START_DATE — Start of the period; sourced as GLPER.START_DATE in the GL branch and PAPERIOD.PA_START_DATE in the PA branch.
• END_DATE — End of the period; sourced as GLPER.END_DATE in the GL branch and PAPERIOD.PA_END_DATE in the PA branch.

Common Use Cases and Queries

Typical uses include populating a forecast period list of values, validating a user-entered forecast period, and generating period lookups in custom reports. Because the profile option drives the UNION, a query returns data for only one period type in a given session. A representative query is:

• SELECT period_type, period_year, period_name, start_date, end_date FROM apps.pa_fcst_periods_tmp_v ORDER BY period_year, start_date;
• SELECT period_name, start_date, end_date FROM apps.pa_fcst_periods_tmp_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND end_date;
• SELECT period_name FROM apps.pa_fcst_periods_tmp_v WHERE period_year = :p_year;

Set the profile option PA_FORECASTING_PERIOD_TYPE to 'GL' or 'PA' as appropriate before relying on results, since the view resolves the profile at query time and returns no rows if the profile value does not match either branch.