Search Results sce_class_code_valid




Overview

The view FPA_AW_PCLASS_STR_SCORES_V belongs to the FPA – Project Portfolio Analysis module of Oracle E-Business Suite and is owned by the APPS schema. It exposes weighted strategic scoring results that Project Portfolio Analysis calculates for project classifications across scenarios, planning cycles, and investment criteria. Because the underlying analysis is performed inside an Oracle OLAP analytic workspace rather than in conventional relational tables, the view acts as the bridge that converts multidimensional OLAP data into a flat, relational result set that can be joined to other EBS objects or reported on directly.

The view is documented with a status of INVALID in the ETRM metadata, which signals that the object requires recompilation (for example, after an upgrade, patch application, or change to a dependent object such as FPA_UTILITIES_PVT). Its record set is deliberately filtered to rows where SCE_CLASS_CODE_VALID = 1, so only classifications valid for the active scenario are returned. This filtered form of the data is the layer most commonly consumed by reporting and integration logic, and it is the object users encounter when investigating the column and value they searched for, sce_class_code_valid.

Underlying Base Objects

The view is defined over two documented base objects. The first is the package FPA_UTILITIES_PVT, which supplies the analytic workspace name through the function AW_SPACE_NAME. This value is concatenated with the literal string ' DURATION QUERY' and passed as the query identifier to the second base object, the synonym OLAP_TABLE (mapping to the server's OLAP_TABLE function). The OLAP_TABLE invocation defines the dimensions and measures to be extracted from the analytic workspace:

The target relational shape of the OLAP output is described by the analysis workspace object name FPA_PROJ_CLASS_STR_TBL. Because it depends on a package function to resolve the workspace name at runtime, the view is environment-aware and must be recompiled whenever the surrounding project analysis configuration or the OLAP structures change.

Key Columns

The view projects a compact set of columns that together identify each scoring result and quantify it:

  • CLASS_CODE — the project classification being scored, drawn from the CLASS_CODE_D dimension.
  • SCENARIO — the portfolio analysis scenario in which the score applies, from SCENARIO_D.
  • PLANNING_CYCLE — the planning cycle associated with the scenario, from the PLANNING_CYCLE_SCENARIO_R relation.
  • INVESTMENT_CRITERIA — the strategic objective against which the classification is evaluated, from STRATEGIC_OBJ_D.
  • WEIGHTED_SCORE — the scored value for the classification under the given scenario and criterion.
  • COST_WEIGHTED_SCORE — the corresponding score adjusted by cost weighting.
  • SCE_CLASS_CODE_VALID — the validity flag for the scenario/classification combination; only rows with a value of 1 survive the view's WHERE clause, so consumers of the view always see valid combinations. Queries against the underlying measure are required to observe invalid combinations.

Common Use Cases and Queries

Typical uses include extracting classification scores for reporting, reconciling portfolio analysis output with relational project data, and diagnosing why a particular classification appears (or fails to appear) in strategic scoring reports. A representative query lists weighted scores for a scenario:

SELECT class_code, investment_criteria, weighted_score, cost_weighted_score
FROM   apps.fpa_aw_pclass_str_scores_v
WHERE  scenario = :scenario
AND    planning_cycle = :cycle
ORDER BY class_code;

A second pattern aggregates scores by criterion to rank classifications within a scenario:

SELECT investment_criteria, class_code,
       SUM(weighted_score) AS total_weighted_score
FROM   apps.fpa_aw_pclass_str_scores_v
WHERE  scenario = :scenario
GROUP BY investment_criteria, class_code;

Because the view is filtered on SCE_CLASS_CODE_VALID = 1, any troubleshooting of missing classifications should query the OLAP measure directly rather than this view; a classification absent here may simply be flagged invalid for the selected scenario. Recompilation via ALTER VIEW APPS.FPA_AW_PCLASS_STR_SCORES_V COMPILE resolves the INVALID status when the analytic workspace and FPA_UTILITIES_PVT are correctly configured.