Search Results pc_class_code_m

Overview

The view APPS.FPA_AW_PC_INV_MATRICES_V belongs to the FPA (Project Portfolio Analysis) product family within Oracle EBS 12.1.1 and 12.2.2. It exposes investment mix data for planning cycles, organized by project classification category and class code. Rather than storing data in a conventional heap table, the view is defined over an Oracle OLAP analytic workspace. It uses the OLAP_TABLE table function to project multidimensional AW data into a relational row-and-column format, allowing standard SQL to be issued against analytic workspace measures that would otherwise be inaccessible to relational reporting tools.

The view is documented with a status of INVALID, which is significant. Because it depends on the runtime availability of the OLAP analytic workspace named by FPA_UTILITIES_PVT.AW_SPACE_NAME, the view will appear INVALID whenever the workspace has not been loaded, refreshed, or attached in the current database instance. In practice, many FPA installations carry this view in an invalid state outside of active portfolio analysis sessions.

Underlying Base Objects

The documented referenced base objects are:

• FPA_UTILITIES_PVT (PACKAGE) — Supplies the analytic workspace name via the global AW_SPACE_NAME, which the view concatenates with the string ' DURATION QUERY' to identify the AW and the specific limit map used for the projection.
• OLAP_TABLE (SYNONYM) — The synonym resolving to the OLAP_TABLE table function, which is the mechanism that converts multidimensional AW data into relational rows.

The view text declares two dimensions — PLANNING_CYCLE mapped from PLANNING_CYCLE_D and CLASS_CODE mapped from CLASS_CODE_D — and three measures: PC_CATEGORY from PC_CATEGORY_M, INVESTMENT_MIX from PC_CLASS_CODE_TARGET_MIX_M, and IS_VALID_PC_CLASS_CODE from PC_CLASS_CODE_M. The projection is filtered by IS_VALID_PC_CLASS_CODE = 1, so only class codes that are valid for the given planning cycle and category are returned.

Key Columns

• PLANNING_CYCLE — The planning cycle dimension value, identifying the portfolio analysis cycle for which the investment mix applies.
• PC_CATEGORY — The portfolio analysis category measure, relevant to the user's search term "pc_category." It provides the category dimensioning applied to the investment mix row.
• CLASS_CODE — The classification (class) code dimension value, representing the grouping to which the investment mix target applies.
• INVESTMENT_MIX — The target investment mix measure associated with the class code, sourced from PC_CLASS_CODE_TARGET_MIX_M.
• IS_VALID_PC_CLASS_CODE — A validity flag sourced from PC_CLASS_CODE_M. Because of the view's WHERE clause, this column always returns 1 in query results.

Common Use Cases and Queries

This view is typically queried when validating or reporting on investment mix targets configured for a planning cycle. A representative query filtered by the searched term pc_category is:

SELECT planning_cycle, pc_category, class_code, investment_mix
FROM apps.fpa_aw_pc_inv_matrices_v
WHERE pc_category = :p_category
ORDER BY planning_cycle, class_code;

Because the view is filtered to valid class codes only, it is suited to join against portfolio analysis setup tables when building exception reports or feeding downstream mix-validation logic. Analysts should be aware that any query will fail or return no rows if the underlying OLAP analytic workspace is not attached and populated. Verifying that FPA_UTILITIES_PVT.AW_SPACE_NAME resolves to a loaded workspace is a prerequisite before relying on this view in SQL*Plus, concurrent programs, or Discoverer/EBS reporting.