Results for “class_code”

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

Overview

FPA_AW_PROJS_V is a PL/SQL-based view owned by the APPS schema within the FPA (Project Portfolio Analysis) product family of Oracle E-Business Suite. It exposes project-level analytical data that has been materialized into an Oracle OLAP analytic workspace, rather than data stored in conventional relational tables. The view is defined not over a base table but over the OLAP_TABLE function, which projects multidimensional analytic workspace objects into a relational, queryable result set. It therefore functions as the bridge between the OLAP engine used by Project Portfolio Analysis and standard SQL-based reporting, integration, and extraction tools.

Its practical role is to present, for each project in the analytical workspace, the project identifier together with the descriptive attributes CLASS_CODE, PORTFOLIO, and PLANNING_CYCLE. This makes project classification and portfolio assignment available to concurrent programs, reports, and downstream interfaces without requiring direct OLAP API calls. The view is documented as VALID in ETRM for 12.1.1 and 12.2.2, and its metadata is consistent across those releases.

Underlying Base Objects

The documented referenced base objects are the package FPA_UTILITIES_PVT and the synonym OLAP_TABLE. The view body is:

• SELECT PROJECT, CLASS_CODE, PORTFOLIO, PLANNING_CYCLE FROM TABLE (OLAP_TABLE(FPA_UTILITIES_PVT.AW_SPACE_NAME || ' DURATION QUERY', 'FPA_PROJ_TBL', '', 'DIMENSION PROJECT FROM PROJECT_D WITH ATTRIBUTE CLASS_CODE FROM CLASS_CODE_PROJECT_R ATTRIBUTE PORTFOLIO FROM PORTFOLIO_PROJECT_R ATTRIBUTE PLANNING_CYCLE FROM PC_PROJECT_R'))

Two dependencies deserve emphasis. First, FPA_UTILITIES_PVT.AW_SPACE_NAME supplies the name of the runtime analytic workspace; the view is valid only when that workspace exists and has been built for the current session or environment. The literal ' DURATION QUERY' is concatenated to form the OLAP_TABLE query identifier. Second, the analytical objects referenced in the OLAP_TABLE clause — FPA_PROJ_TBL, PROJECT_D, CLASS_CODE_PROJECT_R, PORTFOLIO_PROJECT_R, and PC_PROJECT_R — are dimensional and relational (relation) objects inside the analytic workspace, not database tables. Because the source is an OLAP construct, the view is a read-only projection and its contents reflect the last state of the analytic workspace.

Key Columns

• PROJECT — The project dimension value, mapped from the PROJECT_D dimension. It identifies the project for which portfolio analysis data is being reported.
• CLASS_CODE — The project classification code, sourced from the CLASS_CODE_PROJECT_R relation. This is the column most commonly targeted by searches, as it carries the classification used to group and filter projects in portfolio analysis.
• PORTFOLIO — The portfolio to which the project belongs, sourced from the PORTFOLIO_PROJECT_R relation. It supports grouping of projects into investment portfolios.
• PLANNING_CYCLE — The planning cycle associated with the project, sourced from the PC_PROJECT_R relation. It allows analysis to be scoped to a particular planning horizon.

All four columns are exposed as simple scalar attributes projected from the multidimensional model; no keys or foreign-key relationships to relational tables are documented on the view itself.

Common Use Cases and Queries

Because the view flattens OLAP dimensionality into rows, it is typically used for validation, reconciliation, and lightweight reporting of project classification and portfolio membership. Typical patterns include confirming which projects carry a given classification code, listing projects by portfolio, and restricting output to a planning cycle.

• Retrieve projects for a specific classification: SELECT PROJECT, CLASS_CODE, PORTFOLIO FROM APPS.FPA_AW_PROJS_V WHERE CLASS_CODE = :p_class_code;
• List portfolio membership: SELECT PORTFOLIO, PROJECT FROM APPS.FPA_AW_PROJS_V ORDER BY PORTFOLIO, PROJECT;
• Scope by planning cycle: SELECT PROJECT, CLASS_CODE FROM APPS.FPA_AW_PROJS_V WHERE PLANNING_CYCLE = :p_cycle;

Queries against this view require the analytic workspace referenced by FPA_UTILITIES_PVT.AW_SPACE_NAME to be available; otherwise the OLAP_TABLE call fails at runtime. For this reason the view is best treated as a reporting and diagnostic aid rather than a foundation for high-volume or transactional processing.