Search Results net_present_value




Overview
Explore in AI Chat

Overview

FPA_AW_PROJ_NPVS_V is an Oracle Applications (APPS) database view belonging to the FPA – Project Portfolio Analysis product within Oracle E-Business Suite. Its purpose is to expose Net Present Value (NPV) metrics calculated for project and scenario combinations held in an Oracle OLAP analytic workspace. The view name itself reflects this role: FPA (the product), AW (analytic workspace), PROJ (project), NPVS (net present values), and the _V suffix denoting a view.

Unlike conventional relational views that join base tables, this view is a presentation layer over multidimensional OLAP data. It retrieves NPV values that have been computed and stored inside an OLAP analytic workspace, then surfaces them in a flat, row-oriented format that standard SQL tools, reports, and integrations can consume. This is significant because FPA portfolio analysis calculations — discounting future cash flows to a present value, comparing scenarios, and validating scenario/project pairings — are performed inside the OLAP engine and are not natively available as relational columns. The view therefore acts as the bridge between the multidimensional analytic workspace and the relational reporting environment. In Oracle EBS 12.1.1 and 12.2.2, such OLAP-backed views are used primarily by Project Portfolio Analysis functionality and by custom reporting that must reconcile portfolio metrics.

The documented status of the object is INVALID, meaning it requires recompilation in the environment where it was captured. Because the view depends on OLAP metadata and a package function, validity depends on the analytic workspace being properly attached and the underlying PL/SQL being compiled.

Underlying Base Objects

The documented referenced base objects are limited to two entries: the package FPA_UTILITIES_PVT and the synonym OLAP_TABLE. Both are central to how the view operates.

  • FPA_UTILITIES_PVT — This package supplies the analytic workspace name referenced at runtime. The view text calls FPA_UTILITIES_PVT.AW_SPACE_NAME, appending the literal string ' DURATION QUERY' to construct the fully qualified OLAP query identification passed to OLAP_TABLE. The existence of this helper confirms that the analytic workspace name is environment-specific and resolved dynamically rather than hard-coded.
  • OLAP_TABLE (synonym) — This is the Oracle OLAP function that maps the result of an OLAP query into a relational table structure. It accepts the workspace and query identification, an output table type (FPA_PROJ_METRICS_TBL), and a comma-separated OLAP clause string defining dimensions and measures. The view wraps this function call inside a TABLE() collection expression, which is what allows a multidimensional result set to be queried with ordinary SQL.

The view is defined entirely over these OLAP constructs; it does not reference the underlying FPA project or financial tables directly. Instead, those source data are consumed earlier when the analytic workspace is built and refreshed.

Key Columns

The view exposes four columns, each mapped from an OLAP dimension or measure:

  • PROJECT — The project dimension member. Sourced from PROJECT_D in the OLAP query, identifying which project the NPV figure relates to.
  • SCENARIO — The scenario dimension member. Sourced from SCENARIO_D, identifying the portfolio scenario under which the NPV was calculated.
  • NET_PRESENT_VALUE — The primary measure. This is the calculated NPV produced by the OLAP expression AW_EXPR CALC_SCE_PROJ_NPV_PRG, which invokes the NPV calculation program for the selected scenario/project combination.
  • SCENARIO_PROJECT_VALID — A measure from SCENARIO_PROJECT_M acting as a validity flag for the scenario/project pairing. The view's WHERE clause filters to SCENARIO_PROJECT_VALID = 1, so only valid combinations are returned. Invalid or undefined pairings are excluded.

Because the WHERE filter is embedded in the view definition, consumers always receive the validated subset of scenario/project NPVs.

Common Use Cases and Queries

The primary use case is reporting and reconciliation of portfolio NPV metrics. Analysts compare NPV across scenarios for a given project, or rank projects within a scenario, without needing to understand OLAP internals. Typical queries include:

  • Retrieving all valid NPVs for a single project: SELECT scenario, net_present_value FROM fpa_aw_proj_npvs_v WHERE project = :project;
  • Comparing scenarios that share a project set: SELECT project, scenario, net_present_value FROM fpa_aw_proj_npvs_v ORDER BY project, scenario;
  • Ranking projects by NPV within a scenario: SELECT project, net_present_value FROM fpa_aw_proj_npvs_v WHERE scenario = :scenario ORDER BY net_present_value DESC;
  • Feeding custom dashboards or integration extracts, since the flat structure is directly joinable to project and scenario descriptive tables on the PROJECT and SCENARIO keys.

If the view returns no rows or errors, the cause is typically an invalid object state or an unattached analytic workspace. Recompiling the view and confirming the OLAP workspace resolved by FPA_UTILITIES_PVT.AW_SPACE_NAME will normally restore operation.