Results for “class_code_project_r”

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

Overview

APPS.FPA_AW_PROJ_CASHFLOWS_V is a reporting view in Oracle EBS Release 12.1.1 and 12.2.2 that exposes project-level cash flow and funding metrics maintained within the Enterprise Performance Foundation (EPF) / Financial Planning and Analysis (FPA) analytical workspace. Unlike conventional relational views that select directly from base tables, this view is defined over an Oracle OLAP construct: the OLAP_TABLE synonym is used in conjunction with the FPA_UTILITIES_PVT package to materialize the contents of an analytic workspace into a relational row set consumable by SQL.

The view returns one row per valid scenario/project combination, filtered by the predicate WHERE scenario_project_valid = 1, meaning only projects that are active and valid for a given scenario are exposed. It is the primary access point for reporting on project funding requirements, benefits, sunk cost, total cost, and the alignment between recommended and current funding status.

The user's search term class_code_project_r corresponds directly to the CLASS_CODE column in this view, which is populated from the OLAP relation class_code_project_r. This makes the view the authoritative source when reporting or filtering project cash flows by project class code.

Underlying Base Objects

The documented base objects referenced by this view are:

• FPA_UTILITIES_PVT (PL/SQL package) — Supplies the function AW_SPACE_NAME, which returns the name of the analytic workspace. The view concatenates this with ' duration query' to form the fully qualified OLAP query identifier passed to OLAP_TABLE.
• OLAP_TABLE (synonym) — The standard Oracle OLAP row-to-column conversion function. It maps the named workspace dimensions, attributes, and measures into a relational structure whose column shape matches FPA_PROJ_METRICS_TBL.

Internally, the OLAP query references the following dimension, attribute, and measure objects within the workspace:

• Dimensions: scenario_d, project_d
• Attributes: current_funding_status (from funding_status_curr_project_r), recommended_funding_status (from funding_status_rec_scenario_project_r), class_code (from class_code_project_r)
• Measures: funds_required, total_cost (both from scenario_project_cost_m), total_benefit (from scenario_project_benefit_m), sunk_cost (from project_sunk_cost_m), user_rank (from scenario_project_user_rank_m), and scenario_project_valid (from scenario_project_m).

Key Columns

• PROJECT — The project identifier from project_d.
• CLASS_CODE — The project classification, sourced from class_code_project_r. This is the column sought by the search term class_code_project_r.
• SCENARIO — The planning scenario from scenario_d.
• FUNDS_REQUIRED — The funding amount required, derived from scenario_project_cost_m.
• TOTAL_BENEFIT — Aggregate benefit from scenario_project_benefit_m.
• SUNK_COST — Accumulated sunk cost from project_sunk_cost_m.
• TOTAL_COST — Total cost from scenario_project_cost_m.
• USER_RANK — Analyst-assigned ranking from scenario_project_user_rank_m.
• RECOMMENDED_FUNDING_STATUS — Recommended status from funding_status_rec_scenario_project_r.
• CURRENT_FUNDING_STATUS — Current status from funding_status_curr_project_r.
• SCENARIO_PROJECT_VALID — Validity flag; only rows where this equals 1 are returned.

Common Use Cases and Queries

The view is used for project portfolio analysis, funding gap reporting, and prioritization. A representative query filters by class code:

SELECT project, class_code, scenario,
       funds_required, total_benefit, sunk_cost,
       total_cost, user_rank
  FROM apps.fpa_aw_proj_cashflows_v
 WHERE class_code = :p_class_code
   AND scenario  = :p_scenario;

Another frequent pattern compares recommended versus current funding status to identify projects at risk of de-funding:

SELECT project, class_code, funds_required,
       recommended_funding_status, current_funding_status
  FROM apps.fpa_aw_proj_cashflows_v
 WHERE recommended_funding_status <> current_funding_status;

Because the view depends on FPA_UTILITIES_PVT.AW_SPACE_NAME, the FPA analytic workspace must be loaded and current; otherwise the OLAP query will return no rows. Financial analysts typically grant SELECT on this view to reporting users while restricting direct access to the underlying workspace objects.