Results for “scenario_discount_rate_m”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.FPA_AW_SCE_NPVS_V belongs to the FPA (Project Portfolio Analysis) product family within Oracle E-Business Suite, and is catalogued in ETRM for releases 12.1.1 and 12.2.2. It exposes analytic scenario metrics generated through Oracle OLAP, presenting discount rate and net present value figures per portfolio analysis scenario. The view name follows the FPA_AW_SCE_NPVS convention, indicating a Portfolio Analysis (FPA) analytic workspace (AW) source, a scenario (SCE) dimension, and net present value series (NPVS).

Functionally, the view serves reporting and integration consumers that need scenario-level financial metrics without querying OLAP objects directly. It is a thin projection over an OLAP_TABLE invocation, so all the computation occurs inside the OLAP analytic workspace rather than in the relational SQL layer. The view is currently documented with a status of INVALID, meaning the underlying OLAP metadata, worksheet, or package state was not valid at the time of capture; consumers should recompile or revalidate before relying on it in a production report.

Underlying Base Objects

The documented base objects referenced by this view are FPA_UTILITIES_PVT (PACKAGE) and OLAP_TABLE (SYNONYM). The package FPA_UTILITIES_PVT supplies the analytic workspace name constant AW_SPACE_NAME, which is concatenated with the literal ' DURATION QUERY' to form the OLAP_TABLE query identifier. OLAP_TABLE is the synonym for the Oracle OLAP relational interface that materialises a dimensioned result set from an analytic workspace object into rows and columns.

The view definition includes an OLAP_TABLE specification with three clauses: a limit map named 'LMT DAY_D TO LIMIT( LIMIT(DAY_D TO DAY_D GT TODAY) KEEP ANY(SCENARIO_CASHFLOW_DAY_M NE NA, DAY_D)) TODAY', a dimension clause mapping SCENARIO from SCENARIO_D, and measure clauses mapping DISCOUNT_RATE from SCENARIO_DISCOUNT_RATE_M and NET_PRESENT_VALUE from SCENARIO_NPV_M. The result is typed as FPA_SCENARIO_TBL. The KEEP ANY condition restricts the day dimension to periods beyond the current day where scenario cash flow is not null, which is why cash flow-driven measures such as NPV are meaningful at the returned grain.

Key Columns

• SCENARIO — The scenario identifier sourced from the SCENARIO_D OLAP dimension. It distinguishes competing portfolio scenarios (for example baseline versus alternate funding or schedule cases) that FPA users compare.
• DISCOUNT_RATE — The discount rate measure read from SCENARIO_DISCOUNT_RATE_M. This is the rate applied to future cash flows for the scenario, and it is the attribute most commonly sought by users searching the term "discount_rate" against this object.
• NET_PRESENT_VALUE — The NPV measure read from SCENARIO_NPV_M. It represents the discounted value of scenario cash flows for the retained day periods, and is the principal decision metric for portfolio prioritisation.

Because the projection is limited to these three columns over a typed OLAP table, the row grain is scenario-by-retained-day, although the visible output surfaces scenario-level measures for discount rate and NPV.

Common Use Cases and Queries

Typical usage is scenario comparison and downstream integration into custom reports, Discoverer workbooks, or BI Publisher extracts. A representative query returning the full projection is:

• SELECT scenario, discount_rate, net_present_value FROM apps.fpa_aw_sce_npvs_v ORDER BY scenario;
• SELECT scenario, net_present_value FROM apps.fpa_aw_sce_npvs_v WHERE discount_rate IS NOT NULL ORDER BY net_present_value DESC;
• SELECT discount_rate, COUNT(*) FROM apps.fpa_aw_sce_npvs_v GROUP BY discount_rate; — used to confirm which rates are in effect across scenarios.

Before using the view, verify that it compiles successfully, since its documented status is INVALID. If it remains invalid, check the FPA_UTILITIES_PVT package state and the availability of the associated analytic workspace, then recompile the view. In practice the view should be treated as an OLAP-dependent reporting artefact rather than a conventional relational join source.