Search Results funding_variance




Overview
Explore in AI Chat

Overview

APPS.FPA_AW_PCLASS_FUNDS_V is a reporting view in Oracle EBS Release 12.1.1 and 12.2.2 that exposes project class funding data held in an Oracle OLAP analytic workspace. It is the principal surface through which the Enterprise Project Portfolio Analysis (Project Funding / Capital Planning) application presents, for each project classification and planning scenario, the funds made available, the funds required, the resulting funding variance, and the associated total benefit. The view is the object most commonly returned by a search for the term "funding_variance", because funding_variance is one of the measures it publishes.

Rather than selecting from a conventional relational table, the view is defined over a table function call. The OLAP_TABLE function resolves rows from the FPA_PROJ_CLASS_TBL OLAP object within an analytic workspace whose logical name is assembled at runtime from FPA_UTILITIES_PVT.AW_SPACE_NAME concatenated with the literal string " duration query". This design makes the view a relational projection of a multidimensional cube: dimensions and measures are mapped to relational columns inside the OLAP_TABLE invocation, and the outer query filters the result set.

Underlying Base Objects

Two base objects are documented for this view: the package FPA_UTILITIES_PVT and the synonym OLAP_TABLE.

  • FPA_UTILITIES_PVT — a package in the APPS schema that supplies the analytic workspace name (AW_SPACE_NAME) used to identify the cube at runtime. Because the name is resolved dynamically, the view reflects the workspace configured for the current environment rather than a hard-coded object.
  • OLAP_TABLE — the synonym for the Oracle OLAP table function that converts a stored OLAP object (FPA_PROJ_CLASS_TBL) into a relational row source. The dimension and measure clauses inside the call bind each OLAP element to an output column.

The view therefore does not read base tables directly; it depends on the analytic workspace being built and populated by the Project Portfolio Analysis processes.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing funding shortfalls or surpluses by project classification for a planning cycle, comparing scenarios, and feeding variance data into dashboards or custom concurrent programs. Because the validity flag is applied internally, callers automatically see only valid scenario/class combinations.

Querying all variances for a scenario:

  • SELECT class_code, scenario, planning_cycle, funds_available, funds_required, funding_variance, total_benefit FROM apps.fpa_aw_pclass_funds_v WHERE scenario = :p_scenario ORDER BY funding_variance;

Isolating classifications with a funding shortfall:

  • SELECT class_code, funding_variance, total_benefit FROM apps.fpa_aw_pclass_funds_v WHERE scenario = :p_scenario AND funding_variance < 0;

Because the rows originate from an OLAP table function, performance depends on the analytic workspace being current; queries should be restricted by scenario and planning cycle where possible.