Search Results scenario_funds_req_m




Overview
Explore in AI Chat

Overview

APPS.FPA_AW_SCE_FUNDS_V is an Oracle E-Business Suite view used by the Enterprise Territory Management / resource planning components of the ETRM (Enterprise Territory and Resource Management) module set. It exposes scenario-level funding analysis by projecting data out of an Oracle OLAP analytic workspace and presenting it as a conventional relational result set. The three measures it surfaces — funds_available, funds_required, and funding_variance — allow planners, compensation analysts, and reporting tools to evaluate whether the funding allocated to a given scenario or planning cycle is sufficient to cover the funding commitments associated with that scenario.

Because the view returns a standard tabular structure, it can be queried with ordinary SQL, joined to other EBS views, and consumed by Oracle Reports, BI Publisher, Discoverer, or custom concurrent programs. This makes it an integration point between the multidimensional OLAP model (where the financial planning calculations and aggregations are performed efficiently) and the relational reporting layer that most EBS users and downstream systems expect.

Underlying Base Objects

The view is defined entirely over two documented base objects:

  • FPA_UTILITIES_PVT — a PL/SQL package whose function aw_space_name supplies the name of the analytic workspace that stores the ETRM planning data. The package name is concatenated with the literal ' duration query' to build the workspace identifier passed to OLAP_TABLE.
  • OLAP_TABLE — a synonym for the Oracle OLAP OLAP_TABLE pipelined table function, which materializes OLAP multidimensional data into rows and columns.

Inside the OLAP_TABLE call, the view maps the FPA_SCENARIO_TBL output table to a dimension and three measures. The dimension scenario is sourced from the OLAP dimension scenario_d, with the relational attribute planning_cycle drawn from planning_cycle_scenario_r. The measures funds_available, funds_required, and funding_variance are sourced from the OLAP measures scenario_funding_m, scenario_funds_req_m, and scenario_fund_var_m respectively. No base relational EBS tables are referenced directly; all values are resolved through the OLAP workspace.

Key Columns

  • SCENARIO — the scenario identifier from scenario_d. Identifies the planning or funding scenario being analyzed.
  • PLANNING_CYCLE — the planning cycle associated with the scenario, supplied as an attribute via planning_cycle_scenario_r. This ties a scenario to a specific planning period.
  • FUNDS_AVAILABLE — the total funding available for the scenario, sourced from scenario_funding_m. This is the column most directly relevant to the user's "funds_available" search term.
  • FUNDS_REQUIRED — the total funding required by the scenario, sourced from scenario_funds_req_m.
  • FUNDING_VARIANCE — the difference between available and required funds, sourced from scenario_fund_var_m.

Common Use Cases and Queries

The view is typically queried to compare available versus required funds across scenarios and planning cycles, to isolate scenarios with insufficient funding, or to feed downstream incentive and territory planning reports.

Retrieve all funding positions for every scenario:

SELECT scenario,
       planning_cycle,
       funds_available,
       funds_required,
       funding_variance
FROM   apps.fpa_aw_sce_funds_v;

Identify scenarios that are underfunded:

SELECT scenario,
       planning_cycle,
       funds_available,
       funds_required,
       funding_variance
FROM   apps.fpa_aw_sce_funds_v
WHERE  funding_variance < 0
ORDER  BY funding_variance;

Summarize available and required funds by planning cycle:

SELECT planning_cycle,
       SUM(funds_available) AS total_available,
       SUM(funds_required)  AS total_required,
       SUM(funding_variance) AS total_variance
FROM   apps.fpa_aw_sce_funds_v
GROUP  BY planning_cycle;

Because the data originates in an OLAP workspace, response times depend on the state of the analytic workspace referenced by FPA_UTILITIES_PVT.AW_SPACE_NAME. Queries should generally be run after the relevant planning data has been loaded and the workspace refreshed.