Search Results pa_fp_org_fcst_utils




Overview
Explore in AI Chat

Overview

APPS.PA_FP_SUM_PV_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that presents summarized financial plan amounts from the Project Budgeting and Forecasting solution. It is part of the financial plan (FP) presentation layer and is designed to expose period-by-period forecast and budget values in a structure suitable for reporting, inquiry, and integration with downstream tools. The view aggregates period amounts across amount types and subtypes and pivots the underlying period values into discrete, numbered columns (amount_type_name, project_id, resource_assignment_id, version_name), producing a denormalized, reporting-friendly result set aligned to amount types and planning versions.

Underlying Base Objects

The view is owned by APPS and is defined over several documented base objects, each of which plays a specific role:

  • PA_FP_PERIOD_VALUES_V — Supplies the raw period-level amounts and amount subtype codes that are pivoted and summed into the period1 through periodN columns. This is the principal fact source of the view.
  • PA_BUDGET_VERSIONS — Provides version_name and version_number, identifying the budget or forecast version to which the amounts belong.
  • PA_AMOUNT_TYPES_VL — Supplies amount_type_name (the translated, user-facing amount type label) joined to the corresponding amount_type_code.
  • PA_RESOURCE_ASSIGNMENTS — Provides resource_assignment_id, linking summarized amounts to the specific planning resource.
  • PA_FIN_PLAN_VIEW_GLOBAL — A package used by the financial plan view layer for global formatting and computation logic.
  • PA_FP_ORG_FCST_UTILS — The financial plan organizational forecast utilities package, providing supporting logic for organizational forecasting within the financial plan framework.

The view therefore sits on top of a normalized plan fact table (period values) and a set of conformed dimension objects (versions, amount types, resource assignments), performing aggregation and pivoting so consumers do not need to reproduce that logic.

Key Columns

  • PROJECT_ID — The project to which the summarized amounts belong.
  • RESOURCE_ASSIGNMENT_ID — The planning resource assignment that owns the amount.
  • VERSION_NAME / VERSION_NUM — The budget or forecast version identifier and its numeric sequence.
  • AMOUNT_TYPE_NAME / AMOUNT_TYPE_CODE — The translated amount type label and its code (for example MARGIN, MARGIN_PERCENT, QUANTITY).
  • SHOW_URL_FLAG — A computed display flag that returns 'N' for MARGIN, MARGIN_PERCENT, and QUANTITY, and 'Y' otherwise; used by the UI to determine whether a hyperlink is rendered for the amount type.
  • PRECEDING_PERIODS_AMOUNT / SUCCEEDING_PERIODS_AMOUNT — Carried-through amounts for periods outside the displayed range.
  • PERIOD1 … PERIODN — The pivoted, summed period amounts. Each is computed with a DECODE that negates values for the amount subtypes TP_REVENUE_OUT and TP_COST_OUT, and otherwise returns the raw period amount with NVL handling for nulls.

Common Use Cases and Queries

Typical uses include financial plan reports, forecast comparison screens, and extracts feeding budgeting analysis. A representative query filters to one project and version:

  • SELECT project_id, resource_assignment_id, version_name, amount_type_name, period1, period2, period3 FROM apps.pa_fp_sum_pv_v WHERE project_id = :p_project_id AND version_name = :p_version;
  • Aggregating by amount type to review totals across all resource assignments for a version.
  • Filtering on show_url_flag = 'Y' to list only amount types eligible for drill-down navigation.

Because the negative-sign logic for TP_REVENUE_OUT and TP_COST_OUT is embedded in the view, consumers should be aware that period amounts already reflect this sign convention and should not re-apply it.