Search Results sunk_cost




Overview
Explore in AI Chat

Overview

The view APPS.FPA_AW_SCE_CASHFLOWS_V is a reporting object within the Oracle E-Business Suite Enterprise Territory and Resource Management (ETRM) / Sales and Operations Planning analytical framework. It exposes cashflow and cost metrics that are stored inside an Oracle OLAP analytic workspace rather than in conventional relational tables. The view presents analytical results on a per-scenario basis, resolving four core financial measures for each scenario defined in the ETRM landscape: FUNDS_REQUIRED, TOTAL_BENEFIT, SUNK_COST, and TOTAL_COST.

The object exists to bridge the gap between the multidimensional OLAP engine and standard SQL-based reporting, BI Publisher extracts, custom concurrent programs, and integration interfaces. Because Oracle EBS reports and forms are designed to query relational views, the OLAP results must be projected into a relational shape. FPA_AW_SCE_CASHFLOWS_V performs this projection, allowing developers and analysts to query OLAP-derived scenario cashflow data using ordinary SQL. The object is owned by APPS and is documented as a view, meaning it holds no physical storage of its own.

Underlying Base Objects

The view is defined entirely through an OLAP_TABLE invocation, which is the standard mechanism for exposing analytic workspace data as relational rows and columns. Two documented base objects are referenced:

  • FPA_UTILITIES_PVT (PACKAGE): Supplies the helper function AW_SPACE_NAME, which resolves the name of the active analytic workspace. The view concatenates this with the literal ' duration query' to build the fully qualified OLAP cursor/query name passed to OLAP_TABLE. This indirection allows the workspace name to vary by installation or environment without editing the view text.
  • OLAP_TABLE (SYNONYM): A synonym that points to the OLAP_TABLE table function provided by Oracle OLAP. It accepts the workspace query name, the target type (FPA_SCE_METRICS_TBL), a row-level filter argument (empty in this definition), and a limit map describing how dimensions and measures map to relational columns.

The limit map declares one dimension and four measures. The dimension SCENARIO is mapped from SCENARIO_D, while the measures map from dedicated measure objects: SCENARIO_FUNDS_REQ_M, SCENARIO_BENEFIT_M, SCENARIO_SUNK_COST_M, and SCENARIO_COST_M. Each measure is resolved into a relational column of the same conceptual name.

Key Columns

  • SCENARIO: The dimensional key. Identifies the planning, simulation, or forecasting scenario to which the returned financial measurements belong.
  • FUNDS_REQUIRED: The cashflow figure representing capital or funding that must be committed for the scenario. This measure is the direct answer to the common "funds_required" lookup, making the view the primary relational access path for that analytic measure.
  • TOTAL_BENEFIT: The aggregate benefit associated with the scenario, typically the sum of projected returns across the scenario's defined benefit lines.
  • SUNK_COST: Costs already incurred and not recoverable, isolated so that decision-makers can distinguish committed expenditure from forward-looking investment.
  • TOTAL_COST: The overall cost position for the scenario, providing the consolidated denominator against which benefit and funding requirements are evaluated.

Common Use Cases and Queries

Typical use cases include funding-requirement reporting, scenario cost/benefit comparison, and feeding downstream planning dashboards. Because the view returns one row per scenario, the most common query is a straightforward projection:

  • Retrieve funding requirements for all scenarios: SELECT scenario, funds_required FROM apps.fpa_aw_sce_cashflows_v ORDER BY funds_required DESC;
  • Compare benefit against total and sunk cost: SELECT scenario, total_benefit, sunk_cost, total_cost FROM apps.fpa_aw_sce_cashflows_v;
  • Filter to scenarios needing specific funding levels: SELECT scenario, funds_required FROM apps.fpa_aw_sce_cashflows_v WHERE funds_required > 0;
  • Derive net position: SELECT scenario, total_benefit - total_cost AS net_position FROM apps.fpa_aw_sce_cashflows_v;

Because the view depends on an initialized analytic workspace via FPA_UTILITIES_PVT.AW_SPACE_NAME, queries may fail if the OLAP workspace is not attached or populated. Report developers should ensure the ETRM planning process has executed and the workspace is available before relying on results. The view is best treated as a read-only analytical interface rather than a transactional source.