Search Results fpa_sces_vl




Overview
Explore in AI Chat

Overview

FPA_SCES_VL is a validation view (the _VL suffix) owned by the APPS schema in Oracle E-Business Suite, belonging to the FPA — Project Portfolio Analysis product. It exposes the set of scenario definitions available within the Project Portfolio Analysis analytical workspace, joining the OLAP-resident scenario dimension to the translated object metadata stored in the base applications tables. Because the view resolves the translated NAME and DESCRIPTION columns in the session language, it is the standard presentation layer through which scenario values are surfaced to end users and to validation logic.

The view carries a status of INVALID in the documented ETRM 12.2.2 metadata. This is significant: an invalid view cannot be queried until it is successfully recompiled, and any dependent form, concurrent program, or report that references FPA_SCES_VL will fail at runtime. The invalid status is typically symptomatic of an underlying dependency that has changed — most often the FPA_UTILITIES_PVT package body or the OLAP analytic workspace that the view queries through OLAP_TABLE.

Underlying Base Objects

The documented base objects referenced by FPA_SCES_VL are:

  • FPA_OBJECTS_TL (synonym) — the translated objects table holding NAME, DESCRIPTION and audit columns for FPA metadata objects. The view restricts this table to B.OBJECT = 'SCENARIO' and B.LANGUAGE = USERENV('LANG'), yielding the session-language label for each scenario.
  • FPA_UTILITIES_PVT (package) — supplies the AW_SPACE_NAME value used to build the fully qualified analytic workspace name passed to OLAP_TABLE.
  • OLAP_TABLE (synonym) — the Oracle OLAP function that maps an analytic workspace dimension into relational rows. Here it projects the SCENARIO dimension from the SCENARIO_D dimension, with the PLANNING_CYCLE attribute drawn from the PLANNING_CYCLE_SCENARIO_R relation.

FPA_SCES_VL therefore sits at the intersection of two data sources: the multidimensional scenario dimension in the analytic workspace and the relational translated object metadata. The join key is A.SCENARIO = B.ID, with B.OBJECT pinned to 'SCENARIO'.

Key Columns

  • SCENARIO — the scenario identifier from the OLAP dimension, used as the join key to FPA_OBJECTS_TL.ID.
  • NAME — the translated display name of the scenario, in the session language.
  • DESCRIPTION — the translated description of the scenario.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns sourced from FPA_OBJECTS_TL, used for change tracking and conformance with the WHO column convention.

Note that the PLANNING_CYCLE attribute is specified in the OLAP_TABLE call but is not projected in the outer SELECT list, so it is not exposed as a column of this view.

Common Use Cases and Queries

The view is commonly used as a list-of-values source for scenario pickers in Project Portfolio Analysis, and as a lookup when joining portfolio data back to human-readable scenario names. A typical query is:

SELECT scenario, name, description FROM apps.fpa_sces_vl ORDER BY name;

To retrieve a single scenario by identifier:

SELECT name, description FROM apps.fpa_sces_vl WHERE scenario = :p_scenario_id;

Because the view is reported INVALID, DBAs should first attempt recompilation with ALTER VIEW APPS.FPA_SCES_VL COMPILE; and verify that FPA_UTILITIES_PVT is valid and that the analytic workspace exists. Where the OLAP dependency is unreliable, the equivalent relational lookup can be issued directly against FPA_OBJECTS_TL filtered on OBJECT = 'SCENARIO' and the session language, which provides the translated names without invoking OLAP_TABLE.