Results for “total_cost”

50+ results




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

Overview

The FPA_AW_PROJ_CASHFLOWS_V view is a reporting and integration object in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the APPS schema in the FPA - Project Portfolio Analysis module. It exposes project-level cash flow and benefit metrics that have been materialized into an Oracle OLAP analytic workspace, providing a relational, query-accessible projection of multidimensional planning data.

Rather than reading transactional tables directly, the view relies on the OLAP_TABLE operator to pivot an analytic workspace cube—identified dynamically through FPA_UTILITIES_PVT.AW_SPACE_NAME—into a conventional row-and-column result set. This design allows users running portfolio analysis (ranking scenarios, comparing funding requirements, and evaluating recommended versus current funding decisions) to consume analytical results through standard SQL, without needing direct OLAP API access. It is typically surfaced in FPA dashboards, portfolio review reports, and any custom extraction that must reconcile project scenario results into relational form.

Underlying Base Objects

The documented referenced base objects are:

  • FPA_UTILITIES_PVT (PACKAGE) — Provides the AW_SPACE_NAME constant used to resolve the name of the analytic workspace at runtime, ensuring the view targets the correct populated cube.
  • OLAP_TABLE (SYNONYM) — The synonym over the OLAP PL/SQL table function that maps workspace dimensions, attributes, and measures into columns.
  • FPA_PROJ_METRICS_TBL — The OLAP_TABLE out-type (object type) referenced in the query text, shaping the returned rows.

The view defines dimensions SCENARIO (from SCENARIO_D) and PROJECT (from PROJECT_D), attributes CURRENT_FUNDING_STATUS, RECOMMENDED_FUNDING_STATUS, and CLASS_CODE, and measures FUNDS_REQUIRED, TOTAL_BENEFIT, SUNK_COST, TOTAL_COST, USER_RANK, and SCENARIO_PROJECT_VALID. All measures and attributes are resolved from workspace relations (for example SCENARIO_PROJECT_COST_M, SCENARIO_PROJECT_BENEFIT_M, PROJECT_SUNK_COST_M).

Key Columns

  • PROJECT — Project identifier within the portfolio scenario being analyzed.
  • CLASS_CODE — Classification code for grouping or categorizing projects.
  • SCENARIO — The named portfolio planning scenario the metrics belong to.
  • FUNDS_REQUIRED — Cost measure representing capital needed for the project in the scenario.
  • TOTAL_BENEFIT — Projected benefit measure used in ranking and funding decisions.
  • SUNK_COST — Cost already committed or expended, independent of scenario.
  • TOTAL_COST — Aggregate scenario project cost measure.
  • USER_RANK — User-defined priority/rank measure within the scenario.
  • CURRENT_FUNDING_STATUS — Attribute indicating the funding status the project currently holds.
  • RECOMMENDED_FUNDING_STATUS — Attribute indicating the status recommended by analysis.
  • SCENARIO_PROJECT_VALID — Validity flag; the view filters on SCENARIO_PROJECT_VALID = 1.

Common Use Cases and Queries

Typical scenarios include validating funding recommendations against current status, ranking projects by benefit or user rank, and extracting scenario totals for downstream reporting. A simple retrieval is:

  • SELECT scenario, project, class_code, user_rank, funds_required FR FROM fpa_aw_proj_cashflows_v ORDER BY scenario, user_rank;
  • SELECT scenario, project, current_funding_status, recommended_funding_status FROM fpa_aw_proj_cashflows_v WHERE recommended_funding_status <> current_funding_status;
  • SELECT project, SUM(funds_required), SUM(total_benefit) FROM fpa_aw_proj_cashflows_v GROUP BY project;

Because the OLAP_TABLE function depends on the analytic workspace being populated for the current session context, the view should be queried only after the FPA portfolio analysis process has refreshed the workspace.