Search Results scenario_obj_cwscore_m

Overview

APPS.FPA_AW_SCE_STR_SCORES_V is an Oracle E-Business Suite view that exposes strategic scoring results produced by the Enterprise Territory and Resource Management (ETRM / FPA) analytical engine. It is not a conventional relational view over stored tables; rather, it is a virtual view driven by the Oracle OLAP option. The view text wraps an OLAP_TABLE table function call that resolves against an analytic workspace whose name is supplied at runtime by FPA_UTILITIES_PVT.AW_SPACE_NAME. The view returns scenario-level strategic objective scores in a flat, SQL-queryable form, allowing BI Publisher reports, Discoverer worksheets, OBIEE repositories, and custom concurrent programs to consume OLAP measure data without writing MDX or OLAP DML directly.

Within ETRM 12.1.1 and 12.2.2 it serves as the presentation layer for weighted and cost-weighted investment criteria scoring, which underpins strategic alignment analysis in the territory and resource planning process.

Underlying Base Objects

The documented dependency list for this view is intentionally short:

• FPA_UTILITIES_PVT (PACKAGE) — a private ETRM utility package that supplies the analytic workspace name via the AW_SPACE_NAME function. This indirection allows the view to bind to the correct workspace instance for the current planning configuration.
• OLAP_TABLE (SYNONYM) — the Oracle OLAP table function that materialises multidimensional data as rows and columns for standard SQL access.

The OLAP_TABLE invocation itself names the underlying workspace objects: the dimension SCENARIO_D with attribute relation PLANNING_CYCLE_SCENARIO_R, the dimension STRATEGIC_OBJ_D, and the measures SCENARIO_OBJ_WSCORE_M and SCENARIO_OBJ_CWSCORE_M (mapped into the view as WEIGHTED_SCORE and COST_WEIGHTED_SCORE). The limit map uses the table structure FPA_SCE_STR_SCORES_TBL to shape the output columns. Because the source is an analytic workspace rather than base relational tables, data currency depends on the workspace build and refresh cycle rather than on transactional inserts.

Key Columns

• SCENARIO — the planning scenario identifier, sourced from the SCENARIO_D dimension. It keys every returned row.
• PLANNING_CYCLE — the planning cycle associated with the scenario, obtained as an attribute through the PLANNING_CYCLE_SCENARIO_R relation. This reflects the scenario-to-cycle mapping defined in the workspace.
• INVESTMENT_CRITERIA — the strategic objective or investment criterion from the STRATEGIC_OBJ_D dimension against which scores are measured.
• WEIGHTED_SCORE — the weighted score measure SCENARIO_OBJ_WSCORE_M, expressing the scenario's alignment score for the criterion after weighting.
• COST_WEIGHTED_SCORE — the cost-weighted measure SCENARIO_OBJ_CWSCORE_M, applying cost factors to the weighted score for comparative investment analysis.

Together these columns produce a scenario-by-criterion score matrix, with two complementary scoring perspectives per intersection.

Common Use Cases and Queries

Typical uses include strategic alignment reporting, scenario comparison for investment prioritisation, and reconciliation of OLAP-computed scores against ETRM planning data. A basic retrieval follows:

• SELECT scenario, planning_cycle, investment_criteria, weighted_score, cost_weighted_score FROM apps.fpa_aw_sce_str_scores_v;
• Filter by scenario: ... WHERE scenario = :scenario_id ORDER BY weighted_score DESC;
• Rank criteria across scenarios: SELECT investment_criteria, scenario, cost_weighted_score FROM apps.fpa_aw_sce_str_scores_v WHERE planning_cycle = :cycle ORDER BY investment_criteria, cost_weighted_score DESC;
• Aggregate for scenario totals: SELECT scenario, SUM(weighted_score), SUM(cost_weighted_score) FROM apps.fpa_aw_sce_str_scores_v GROUP BY scenario;

Because access is through OLAP_TABLE, these queries can be resource-intensive; constrain them with scenario or planning cycle predicates wherever possible and confirm the analytic workspace has been refreshed before relying on the results.