Results for “fpa_proj_tbl”

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

Overview

APPS.FPA_AW_PROJS_V is a reporting view in the Oracle E-Business Suite Enterprise Performance Foundation / Financial Analytics (FPA) schema. It exposes project-level analytical data that resides in an Oracle OLAP analytic workspace rather than in a conventional relational table. The view is defined using the OLAP_TABLE mechanism, which maps multidimensional analytic workspace objects to a relational, queryable row-and-column structure. In effect, it presents a virtual relational projection of an OLAP cube: one row per project, enriched with descriptive attributes such as class, portfolio, and planning cycle.

The "AW" in the name denotes "Analytic Workspace," confirming that the underlying source is a multidimensional cube built and maintained by the FPA utilities. The view gives application code and end-user reporting a SQL-accessible interface to that cube, allowing standard EBS reporting tools (BI Publisher, Discoverer, custom concurrent programs) to consume OLAP-derived data without writing native OLAP DML.

Underlying Base Objects

The documented metadata identifies two referenced objects:

• FPA_UTILITIES_PVT (PACKAGE) — A private FPA utility package whose AW_SPACE_NAME function supplies the name of the analytic workspace at runtime. This dynamic naming lets the view resolve to the correct workspace version.
• OLAP_TABLE (SYNONYM) — The Oracle OLAP OLAP_TABLE table function that converts analytic workspace data into relational rows. Here it is invoked with the workspace name concatenated with the literal ' DURATION QUERY', the cube name 'FPA_PROJ_TBL', and a dimension/attribute specification string.

The attribute clause draws dimension members and their attributes from several OLAP dimensions: PROJECT_D (the project dimension) with attribute CLASS_CODE from CLASS_CODE_PROJECT_R, attribute PORTFOLIO from PORTFOLIO_PROJECT_R, and attribute PLANNING_CYCLE from PC_PROJECT_R. These relation names (_R suffix) are OLAP attribute relations linking each project member to its descriptive values. Because the view depends on a runtime workspace, it will return an Oracle error if the FPA analytic workspace is not built, deployed, or accessible in the instance.

Key Columns

• PROJECT — The project dimension member; typically the project identifier or name as modeled in the analytic workspace. This is the grain of the view.
• CLASS_CODE — The project classification attribute, sourced from the CLASS_CODE_PROJECT_R relation. Used to categorize projects for analysis and filtering.
• PORTFOLIO — The portfolio attribute, sourced from PORTFOLIO_PROJECT_R. This is the column directly relevant to the user's search term portfolio_project_r, associating each project with its owning portfolio.
• PLANNING_CYCLE — The planning cycle attribute, sourced from PC_PROJECT_R, indicating which planning cycle(s) the project belongs to.

Common Use Cases and Queries

Typical uses include building portfolio-level project listings, filtering projects by planning cycle, and joining the view's attributes to transactional or planning data in relational tables.

• List all projects with their portfolio and class:

  SELECT project, portfolio, class_code
  FROM   apps.fpa_aw_projs_v;

• Filter by portfolio:

  SELECT project, planning_cycle
  FROM   apps.fpa_aw_projs_v
  WHERE  portfolio = 'DEFAULT_PORTFOLIO';

• Group by planning cycle for a count of projects:

  SELECT planning_cycle, COUNT(*)
  FROM   apps.fpa_aw_projs_v
  GROUP  BY planning_cycle;

Because the view resolves through OLAP_TABLE, queries may be slower than against native tables and should be restricted by portfolio, class, or planning cycle filters. The view is read-oriented and not typically used for transactional insert or update operations.