Results for “pa_fp_periods_tmp_v”

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

Overview

The PA_FP_PERIODS_TMP_V view is a temporary reporting and validation object owned by the APPS schema within the Oracle Projects (PA) module. It exposes period information — the period type, the period name, and the corresponding start and end dates — that is relevant to a specific budget version during forecasting and budgeting operations. The view resolves the active budget version dynamically through the PA_FP_VIEW_PLANS_PUB.GET_VERSION_ID() API call, so the rows returned always pertain to the plan or budget version currently in scope for the user session.

Because the view draws from both Oracle Projects periods (PERIOD_TYPE = 'PA') and General Ledger periods (PERIOD_TYPE = 'GL'), it functions as a normalized bridge that presents either Projects-defined or GL-defined calendar periods in a single, uniform column structure. This makes it useful in Oracle EBS 12.1.1 and 12.2.2 form logic, concurrent program support, and custom reporting where the caller cannot predict whether the underlying period profile is PA-based or GL-based.

As a temporary ("_TMP_") view, it should be treated as session-context dependent: its output is not a static reference list, but a dynamic projection governed by the currently selected budget version. It is not intended as a persistent data source.

Underlying Base Objects

The view is defined over four documented base objects:

• PA_PROJ_PERIOD_PROFILES (SYNONYM, aliased PPP) — supplies the PLAN_PERIOD_TYPE and links the period profile to the budget version via PERIOD_PROFILE_ID.
• PA_PERIODS_V (VIEW, aliased PAPERIOD) — supplies the period year, period name, and PA start/end dates.
• PA_BUDGET_VERSIONS (SYNONYM, aliased PBV) — filters the result set to the budget version returned by the PA_FP_VIEW_PLANS_PUB package API.
• PA_FP_VIEW_PLANS_PUB (PACKAGE) — the PL/SQL package whose GET_VERSION_ID() function drives the current-context filter.

The join path runs from the budget version to its period profile, then to the period definition, with a DISTINCT modifier applied to eliminate duplicated period rows that can arise from multiple matching profiles. PA_PROJECTS is also documented among the referenced objects, reflecting the broader forecasting context in which the view is used.

Key Columns

• PERIOD_TYPE — a DECODE-derived discriminator distinguishing 'PA' (Projects) from 'GL' (General Ledger) periods, sourced from PPP.PLAN_PERIOD_TYPE.
• PERIOD_YEAR — the fiscal/calendar year of the period, taken from PAPERIOD.PERIOD_YEAR.
• PERIOD_NAME — the period label. For 'PA' rows this is PAPERIOD.PERIOD_NAME; for 'GL' rows it is GL_PERIOD_NAME.
• START_DATE — the period start. Returns PA_START_DATE for 'PA' rows and GL_START_DATE for 'GL' rows.
• END_DATE — the period end, returning PA_END_DATE or GL_END_DATE depending on period type.

Common Use Cases and Queries

Typical uses include validating that a forecast, budget, or plan version falls within a valid period range, populating period LOVs in custom forms, and aligning Projects forecasting data with GL calendars. A representative query:

• SELECT period_type, period_year, period_name, start_date, end_date FROM apps.pa_fp_periods_tmp_v ORDER BY period_year, start_date;
• Filtering a single period type: SELECT period_name, start_date, end_date FROM apps.pa_fp_periods_tmp_v WHERE period_type = 'GL';
• Date-window lookup: SELECT period_name FROM apps.pa_fp_periods_tmp_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND end_date;

Because results depend on PA_FP_VIEW_PLANS_PUB.GET_VERSION_ID(), callers must ensure a plan/budget version context is established before querying; otherwise the view may return no rows. It is best used within the Projects forecasting forms and concurrent processes that set that context.