Search Results project_d




Overview
Explore in AI Chat

Overview

FPA_AW_PROJ_NPVS_V is an Oracle E-Business Suite view owned by the APPS schema that exposes project-level net present value (NPV) metrics calculated within the Enterprise Territory and Resource Management (ETRM) analytic workspace. The view abstracts a query executed against an Oracle OLAP analytic workspace, presenting the result as a conventional relational row set. Each row represents one valid scenario/project combination together with its computed net present value.

The view is a thin but functionally important presentation layer. Rather than requiring a caller to understand OLAP_TABLE syntax, dimension descriptors, or the analytic workspace naming convention, the view returns four plain columns that can be joined, filtered, and reported on using ordinary SQL. It plays a dual role: as a reporting source for NPV-by-scenario analysis, and as an integration point for downstream EBS programs, concurrent requests, and BI tools that expect a relational interface to OLAP-derived data. The defining characteristic of the view is that it exposes only combinations where the scenario-to-project relationship is considered valid, as enforced by the trailing predicate.

Underlying Base Objects

The view is defined over a single inline construct that invokes the OLAP_TABLE function, and the documented referenced base objects are FPA_UTILITIES_PVT (PACKAGE) and OLAP_TABLE (SYNONYM).

  • FPA_UTILITIES_PVT supplies the package-level function AW_SPACE_NAME, whose return value is concatenated with the literal ' duration query' to form the fully qualified analytic workspace query name passed to OLAP_TABLE. This package is the only PL/SQL dependency recorded for the view.
  • OLAP_TABLE is the synonym for the OLAP_TABLE SQL table function that materializes workspace query results into rows and columns, using an out-of-line type identifier (FPA_PROJ_METRICS_TBL) and a dimension/measure mapping string.
  • Scenario_d and project_d are the OLAP dimensions addressed in the mapping. The user search term "scenario_d" corresponds directly to the SCENARIO dimension referenced both in the dimension list and inside the CALC_SCE_PROJ_NPV_PRG expression.
  • CALC_SCE_PROJ_NPV_PRG, SCENARIO_PROJECT_M, and AW_EXPR are the analytic workspace calculation program, validity measure, and expression construct referenced by the mapping string; they reside in the analytic workspace rather than in relational tables.

Because the underlying data lives in the OLAP analytic workspace, the view reflects the workspace state at query time; it does not store data itself.

Key Columns

  • PROJECT — Identifier of the project dimension member (from the PROJECT_D dimension) for which the NPV has been computed.
  • SCENARIO — Identifier of the scenario dimension member (from SCENARIO_D) under which the project valuation was calculated. This is the column most closely associated with the search term "scenario_d".
  • NET_PRESENT_VALUE — The computed NPV value, derived through the AW_EXPR measure that invokes CALC_SCE_PROJ_NPV_PRG. The calculation navigates the scenario and project dimensions using the STATVAL/STATRANK constructs to resolve the current member positions.
  • SCENARIO_PROJECT_VALID — A validity indicator sourced from the SCENARIO_PROJECT_M measure. The view filters on this column, so only rows with a value of 1 are returned, guaranteeing that each PROJECT/SCENARIO pair is a permitted combination.

Common Use Cases and Queries

Typical uses include scenario comparison reporting, portfolio NPV ranking, and feeding downstream planning or integration processes that require a relational NPV feed restricted to valid scenario/project pairings.

  • Retrieve the NPV for every valid project under a specific scenario: 
    SELECT project, net_present_value
FROM   apps.fpa_aw_proj_npvs_v
WHERE  scenario = :scenario_id
ORDER  BY net_present_value DESC;
  • Compare all scenarios for a single project: 
    SELECT scenario, net_present_value
FROM   apps.fpa_aw_proj_npvs_v
WHERE  project = :project_id;
  • Aggregate scenario-level totals: 
    SELECT scenario, COUNT(*), SUM(net_present_value)
FROM   apps.fpa_aw_proj_npvs_v
GROUP  BY scenario;

Because SCENARIO_PROJECT_VALID is always 1 in the result set, callers need not re-test validity. Note that the view is driven by FPA_UTILITIES_PVT.AW_SPACE_NAME, so the analytic workspace must be available and correctly named; if the workspace query cannot be resolved, the view returns no rows or raises an OLAP error. The same behavior is observed in both Oracle EBS 12.1.1 and 12.2.2.