Results for “fpa_scenario_tbl”

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

Overview

FPA_AW_SCES_V is a database view owned by the APPS schema within the FPA (Project Portfolio Analysis) product family in Oracle E-Business Suite. In 12.1.1 and 12.2.2, this view exposes scenario and planning cycle metadata derived from an Oracle OLAP analytic workspace, presenting that data through a conventional relational interface that SQL-based components can query directly.

The view's role is essentially translational. Project Portfolio Analysis relies on multidimensional OLAP structures to store and manipulate scenario-based portfolio data, but most of the EBS application stack — concurrent programs, forms, OAF pages, and reporting tools — operates against relational objects. FPA_AW_SCES_V bridges that gap by projecting two logical dimensions from the OLAP workspace into a two-column relational result set. Its status is VALID, indicating it is compiled and available in the documented environment.

Because it surfaces planning scenario definitions and their associated cycles, the view supports disaggregated reporting and validation logic that needs to enumerate which scenarios exist and how they map to planning cycles, without requiring direct OLAP API calls.

Underlying Base Objects

The view is defined over an inline OLAP_TABLE invocation rather than a conventional base table. The documented base objects are:

• FPA_UTILITIES_PVT (PACKAGE) — a PL/SQL package supplying the analytic workspace space name via the function AW_SPACE_NAME. The view text concatenates this value with the literal ' DURATION QUERY' to form the OLAP query identifier passed to OLAP_TABLE.
• OLAP_TABLE (SYNONYM) — the standard OLAP access mechanism that materializes rows from a multidimensional workspace into a relational rowset, using a specified table shape and dimension/attribute mapping clause.

The view text reads the SCENARIO dimension from the SCENARIO_D dimension object, with PLANNING_CYCLE sourced from the PLANNING_CYCLE_SCENARIO_R relation, and returns the result using the FPA_SCENARIO_TBL row type as its shape. Consequently, the view's contents are only meaningful when the FPA analytic workspace is attached and populated; if the workspace is unavailable, the view will fail rather than return stale rows. This dependency means query performance and availability are tied to analytic workspace state rather than to ordinary table access.

Key Columns

The view exposes exactly two columns, both scalar character values:

• SCENARIO — the identifier or name of a portfolio analysis scenario held in the SCENARIO_D dimension. Each row represents one scenario defined in the workspace.
• PLANNING_CYCLE — the planning cycle associated with that scenario, obtained through the PLANNING_CYCLE_SCENARIO_R relation. This column links each scenario to the planning cycle under which it is evaluated or reported.

Together the two columns form a scenario-to-planning-cycle mapping. There is no primary key constraint, no date column, and no numeric measure; the view is purely a dimensional listing. Consumers should treat the pairing as the unit of meaning and expect potential one-to-many relationships if a scenario is valid across multiple cycles.

Common Use Cases and Queries

Typical uses include populating scenario selection lists in custom reports, validating that a requested scenario exists before running portfolio calculations, and joining scenario identifiers to relational facts for cross-dimensional reporting.

• Enumerating all available scenarios for a portfolio analysis session.
• Determining which planning cycle governs a given scenario.
• Driving concurrent program parameters that require a scenario/cycle pair.

Sample SQL:

SELECT scenario, planning_cycle
FROM   apps.fpa_aw_sces_v
ORDER BY scenario;

SELECT scenario
FROM   apps.fpa_aw_sces_v
WHERE  planning_cycle = :p_cycle;

Because the view depends on the analytic workspace, queries should be issued in sessions where the FPA environment is initialized, and exception handling for OLAP errors is advisable in any programmatic use.