Results for “scenario_initial_m”

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

Overview

FPA_AW_SCE_INFO_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema that exposes scenario-level information from the Enterprise Planning and Budgeting (EPB) / Financial Planning and Analysis (FPA) analytic workspace. Unlike conventional relational views that join base tables, this view is a dynamic OLAP view: its result set is materialized at query time by the OLAP_TABLE function, which maps an OLAP analytic workspace (AW) cube into a relational rowset. The view is part of the EPB data model, which stores planning scenarios, cycles, funding assumptions, and recommendation and approval flags in a multidimensional AW rather than in relational tables.

Because it surfaces scenario metadata such as the working-scenario indicator (the column the user searched for, IS_WORKING_SCENARIO) alongside recommendation and approval flags, this view is the canonical Programmatic interface by which PL/SQL, Oracle Reports, OBIEE, and custom integrations read planning-scenario state for a given planning cycle. It allows applications to determine, per scenario, which scenarios are initial, which is the active or "working" scenario, which are recommended or approved, and what discount rate and funding assumptions apply.

Underlying Base Objects

The documented metadata lists two referenced objects: the package FPA_UTILITIES_PVT and the synonym OLAP_TABLE (which resolves to OLAP_TABLE in the OLAP/Spatial option). The view text invokes FPA_UTILITIES_PVT.AW_SPACE_NAME, a packaged function or constant that returns the name of the FPA analytic workspace. This value is concatenated with the literal ' duration query' and passed as the first argument to OLAP_TABLE, which executes against the running AW instance.

The second argument, FPA_SCENARIO_TBL, is the OLAP table type that defines the output row structure. The fourth argument supplies the OLAP DML statement that describes dimensions and measures: dimension SCENARIO from SCENARIO_D, attribute PLANNING_CYCLE from PLANNING_CYCLE_SCENARIO_R, and measures IS_INITIAL_SCENARIO, IS_WORKING_SCENARIO, RECOMMENDED_FLAG, APPROVED_FLAG, DISCOUNT_RATE, FUNDS_AVAILABLE, and FUNDS_REQUIRED, each sourced from its corresponding *_M measure object inside the analytic workspace. The view therefore depends on both EPB schema objects and the OLAP runtime; the referenced AW must be attached for the query to succeed.

Key Columns

• SCENARIO — Scenario identifier; the primary dimension member.
• PLANNING_CYCLE — Planning cycle attribute associated with the scenario.
• IS_WORKING_SCENARIO — Boolean/flag measure indicating the scenario currently designated as the working scenario for the cycle. This is the attribute most directly relevant to the user's is_working_scenario search.
• IS_INITIAL_SCENARIO — Indicates the seeded or baseline scenario for a planning cycle.
• RECOMMENDED_FLAG — Identifies scenarios the planner has recommended.
• APPROVED_FLAG — Identifies scenarios that have completed approval.
• DISCOUNT_RATE — Discount rate assumption applied to the scenario.
• FUNDS_AVAILABLE and FUNDS_REQUIRED — Funding measures associated with the scenario.

Common Use Cases and Queries

Typical uses include identifying the active working scenario, listing approved scenarios for a cycle, and populating planning dashboards. The following query isolates the working scenario for a planning cycle:

SELECT scenario, planning_cycle, discount_rate
FROM   apps.fpa_aw_sce_info_v
WHERE  is_working_scenario = 'Y';

More commonly the working scenario is combined with the initial and approved flags to drive decision logic:

SELECT scenario, planning_cycle, recommended_flag, approved_flag
FROM   apps.fpa_aw_sce_info_v
WHERE  is_initial_scenario  = 'Y'
OR     is_working_scenario  = 'Y';

Because the view returns one row per scenario per cycle, joins to other FPA_AW_*_V views (for example, funding or project-level cubes) are performed on SCENARIO and PLANNING_CYCLE. Note that the view requires the FPA analytic workspace to be attached; queries executed outside the EPB runtime or after the AW is detached will raise an OLAP error rather than returning rows.