Search Results net_present_value




Overview
Explore in AI Chat

Overview

APPS.FPA_AW_SCE_NPVS_V is a reporting view within the Oracle E-Business Suite Financial Planning and Analysis (FPA) module, part of the Enterprise Tax, Treasury and Risk Management (ETRM) product family. The view exposes net present value (NPV) calculations produced by the Oracle OLAP analytic workspace engine. Rather than storing results in a conventional relational table, the view dynamically projects measures from an in-memory OLAP analytic workspace into relational rows and columns using the OLAP_TABLE table function. This design reflects the FPA reporting architecture, in which scenario-based cash flow analytics are computed in the OLAP workspace and then surfaced to standard SQL consumers for reporting and integration.

The view is registered under the APPS schema, the standard owner for shared EBS application database objects in both 12.1.1 and 12.2.2. It is chiefly relevant to users and developers searching for the term net_present_value, as the view is one of the primary relational access points for NPV results generated by FPA scenario modeling. The view is read-only by nature, since its contents are computed at query time and cannot be updated through DML.

Underlying Base Objects

The documented referenced base objects are the package FPA_UTILITIES_PVT and the synonym OLAP_TABLE. The view definition is:

  • FPA_UTILITIES_PVT — a private utility package whose public variable AW_SPACE_NAME supplies the runtime name of the OLAP analytic workspace. The view concatenates this value with the literal string ' duration query' to form the fully qualified analytic workspace identifier passed to OLAP_TABLE. Because the workspace name is resolved at runtime, the view always targets the currently active FPA analytic workspace.
  • OLAP_TABLE — the synonym for the Oracle OLAP OLAP_TABLE function, which converts OLAP workspace data into a SQL row source. It accepts the workspace identifier, the OLAP relational table representation (FPA_SCENARIO_TBL), a limiting clause, and a mapping clause that binds dimensions and measures to relational columns.

The limiting clause LMT DAY_D TO LIMIT(LIMIT(DAY_D TO DAY_D GT TODAY) KEEP ANY(SCENARIO_CASHFLOW_DAY_M NE NA, DAY_D)) TODAY restricts the result set to future-dated cash flow periods that contain non-null scenario cash flow data, effectively returning forward-looking scenario projections. The mapping clause exposes the SCENARIO_D dimension and the measures SCENARIO_DISCOUNT_RATE_M and SCENARIO_NPV_M as relational columns.

Key Columns

  • SCENARIO — the scenario dimension value derived from SCENARIO_D. Identifies the modeled scenario (for example, a base case, stress case, or user-defined planning scenario) to which the NPV figures apply.
  • DISCOUNT_RATE — the discount rate measure sourced from SCENARIO_DISCOUNT_RATE_M. Represents the rate applied in the NPV calculation for the scenario, typically reflecting a scenario-specific cost of capital or yield curve assumption.
  • NET_PRESENT_VALUE — the NPV measure sourced from SCENARIO_NPV_M. Represents the present value of the scenario's projected future cash flows, discounted at the corresponding scenario discount rate.

Each row returned represents one scenario's NPV and associated discount rate for the qualifying future cash flow horizon, providing a compact, scenario-comparative result set.

Common Use Cases and Queries

Typical uses include scenario comparison reports, treasury and risk dashboards, and integration extracts that feed downstream planning or reporting tools. A representative query is:

  • SELECT scenario, discount_rate, net_present_value FROM apps.fpa_aw_sce_npvs_v; — returns all scenario NPV rows.
  • SELECT scenario, net_present_value FROM apps.fpa_aw_sce_npvs_v WHERE net_present_value IS NOT NULL ORDER BY net_present_value DESC; — ranks scenarios by NPV, useful for identifying the most favorable outcome.
  • SELECT scenario, discount_rate, net_present_value FROM apps.fpa_aw_sce_npvs_v WHERE discount_rate > 0.05; — filters scenarios by discount rate threshold for sensitivity analysis.

Because the view depends on the active OLAP analytic workspace, queries should be executed only after the FPA workspace has been loaded and refreshed. Performance is governed by OLAP workspace availability rather than conventional table indexing, so report design should account for analytical engine latency.