Search Results planning_cycle




Overview
Explore in AI Chat

Overview

FPA_AW_PC_PROJECTS_V is an Oracle Application Object Library (APPS) view within the FPA (Project Portfolio Analysis) product family. It exposes the association between a planning cycle and the projects that participate in that cycle, drawing its data from an OLAP analytic workspace rather than from conventional relational base tables. In Oracle EBS 12.1.1 and 12.2.2, Project Portfolio Analysis relies on analytic workspace (AW) technology to evaluate, score, and rank project portfolios. This view provides a relational, SQL-accessible projection of selected dimensions and attributes stored in that AW, allowing standard reports, concurrent programs, and integrations to read planning-cycle-to-project relationships without directly manipulating AW objects.

The view is documented with a status of INVALID, meaning the underlying dependency (typically the OLAP workspace or the referenced package) must be validated, recompiled, or the AW must be built before the view returns rows. Its role is primarily as a reporting and integration bridge: it translates multidimensional AW content into a flat, two-column relational result set that conforming SQL tools can consume.

Underlying Base Objects

The view is defined over two documented base objects:

  • FPA_UTILITIES_PVT (PACKAGE) — supplies the analytic workspace name through the function/constant reference FPA_UTILITIES_PVT.AW_SPACE_NAME. This package centralizes AW naming and management logic for Project Portfolio Analysis, so the view dynamically targets the correct workspace rather than hard-coding a space name.
  • OLAP_TABLE (SYNONYM) — the Oracle OLAP table function that materializes AW data as rows and columns. The view invokes it with the concatenated workspace and query string ('DURATION QUERY'), the output table type FPA_PC_PROJ_TBL, and a dimension/attribute specification.

The OLAP_TABLE call maps the AW dimension PROJECT (from the PROJECT_D dimension) and attaches the attribute PLANNING_CYCLE sourced from the PC_PROJECT_R relation. In effect, the analytic workspace holds projects and their planning-cycle membership, and this view surfaces those memberships in relational form.

Key Columns

  • PLANNING_CYCLE — identifies the planning cycle to which a project belongs. Planning cycles are the periodic review windows in which portfolios are analyzed and decisions are made. This column is the primary filter for cycle-scoped reporting.
  • PROJECT — the project identifier (typically the project number or name as represented in the AW PROJECT dimension). It links the view to standard project entities used elsewhere in Oracle Projects.

Because the output table type is a two-column structure (FPA_PC_PROJ_TBL), no additional attributes are exposed. Any further project or cycle detail must be obtained by joining to relational project tables on the PROJECT column.

Common Use Cases and Queries

This view is used to enumerate the projects assigned to a given planning cycle, to validate AW population after a portfolio build, and to feed downstream reporting or extracts. A typical query filters by cycle:

  • SELECT planning_cycle, project FROM apps.fpa_aw_pc_projects_v WHERE planning_cycle = :cycle ORDER BY project;
  • SELECT planning_cycle, COUNT(*) FROM apps.fpa_aw_pc_projects_v GROUP BY planning_cycle;
  • SELECT p.planning_cycle, p.project FROM apps.fpa_aw_pc_projects_v p JOIN apps.pa_projects_all pr ON pr.segment1 = p.project;

If the view returns no rows or raises an OLAP error, verify that FPA_UTILITIES_PVT resolves a valid AW_SPACE_NAME and that the analytic workspace has been built for the target cycle. Recompiling the view or rebuilding the AW typically restores the INVALID status to VALID and enables querying.