Search Results scenario_class_code_irr_m

Overview

The view APPS.FPA_AW_PCLASS_FIN_METRICS_V is an Oracle E-Business Suite (EBS) reporting object belonging to the Enterprise Performance Foundation / Financial Portfolio Analysis (FPA) analytical warehouse constructs delivered in EBS 12.1.1 and 12.2.2. It presents project class-level financial metrics that have been pre-aggregated and stored inside an Oracle OLAP analytic workspace, then surfaced to relational SQL through the OLAP_TABLE pipelined function. In practical terms, the view conforms analytical workspace measures into a conventional rows-and-columns result set so that standard relational tooling, Oracle Reports, BI Publisher, and application integration layers can consume OLAP-derived project classification metrics without writing native OLAP DML.

The view is not a stored table. Its rows are computed at query time by projecting dimensions and measures out of the analytic workspace named by FPA_UTILITIES_PVT.AW_SPACE_NAME. The view therefore behaves as a governed access layer over the analytic workspace, and it materially simplifies downstream consumption of capital-project financial metrics.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is owned by APPS and is defined over two referenced base objects:

• FPA_UTILITIES_PVT (PACKAGE) — supplies AW_SPACE_NAME, the package constant/variable that resolves the runtime name of the analytic workspace being queried. Because the workspace name is dynamic, the same view definition can address different workspace instances.
• OLAP_TABLE (SYNONYM) — the OLAP API entry point (OLAP_TABLE) used to map analytic workspace dimensions and measures into relational columns via an OLAP_TABLE specification string.

The OLAP specification declares the external table type FPA_PROJ_CLASS_TBL, the limit map LMT SCENARIO_D TO SCENARIO_D, the dimensions SCENARIO (from SCENARIO_D) and CLASS_CODE (from CLASS_CODE_D), and the measure-to-column mappings drawn from the analytic workspace measures SCENARIO_CLASS_CODE_FUNDING_M, ..._FUNDS_REQ_M, ..._FUND_VAR_M, ..._BENEFIT_M, ..._NPV_M, ..._IRR_M, ..._ROI_M, ..._PAYBACK_M, and SCENARIO_CLASS_CODE_M.

Key Columns

• CLASS_CODE — project classification dimension value identifying the project class being analyzed.
• SCENARIO — scenario dimension, allowing metric comparison across modeled planning scenarios.
• FUNDS_AVAILABLE / FUNDS_REQUIRED — funding capacity versus funding demand for the class/scenario combination.
• FUNDING_VARIANCE — the difference between available and required funds.
• TOTAL_BENEFIT, NET_PRESENT_VALUE, INTERNAL_RATE_RETURN, RETURN_ON_INV, PAYBACK_PERIOD — capital-budgeting measures used to rank and select projects.
• SCE_CLASS_CODE_VALID — an analytical validity flag on the class code. The view filters WHERE sce_class_code_valid = 1, so only valid class codes are returned; this column is exposed but always equals 1 in the result set.

Common Use Cases and Queries

Because the view always restricts to valid class codes, callers do not need to re-apply validity filtering. A typical scenario comparison query is:

• SELECT class_code, scenario, net_present_value, internal_rate_return FROM apps.fpa_aw_pclass_fin_metrics_v ORDER BY net_present_value DESC;
• SELECT class_code, scenario, funding_variance FROM apps.fpa_aw_pclass_fin_metrics_v WHERE funding_variance < 0;
• SELECT class_code, total_benefit, payback_period FROM apps.fpa_aw_pclass_fin_metrics_v WHERE scenario = :scenario;

Typical applications include capital planning dashboards, project-class profitability ranking, funding-gap exception reporting, and integration extracts feeding external portfolio tools. Performance depends on the analytic workspace remaining refreshed and valid; stale or invalid workspaces will yield empty or incomplete results. Because the view inherits APPS privileges, invoking users require APPS-schema access, which is normally supplied to responsibilities through standard EBS security, not through direct grants.