Search Results pa_fin_plan_types_w_v




Overview
Explore in AI Chat

Overview

PA_FIN_PLAN_TYPES_W_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite (validated for 12.1.1 and 12.2.2). It belongs to the Projects (PA) product family and supports the Plan Types page within the Project Management workbench and financial plan setup. The view returns, for a given project identifier, the set of financial plan types that are currently active as working plan types, together with aggregated labor, cost, and revenue measures derived from the associated budget versions. It functions as a presentation and integration layer: rather than exposing raw transactional budget data, it consolidates plan-type configuration, security plan class mapping, and summarized financial figures into a single row per project/plan-type combination. This makes it a convenient source for EBS Forms-based pages, OAF regions, and downstream reporting or integration queries that need a project-scoped view of active financial plans.

Underlying Base Objects

The view is defined over four documented referenced objects:

This mix of a package function call, translated type definitions, and aggregate budget version data is what distinguishes the view from a simple configuration lookup; the aggregations mean that returned measures reflect the working plan types for the project rather than an ungrouped transaction stream.

Key Columns

  • PROJECT_ID — identifies the project whose working financial plan types are returned.
  • NAME and FIN_PLAN_TYPE_CODE — the display name and code of the financial plan type.
  • FIN_PLAN_TYPE_ID — the primary key of the plan type, used for joins to plan type setup.
  • PLAN_CLASS_CODE — the plan class assigned to the plan type in setup.
  • SECURITY_PLAN_CLASS_CODE — the plan class derived via PA_FIN_PLAN_TYPE_GLOBAL.PLANTYPE_TO_PLANCLASS for the specific project; used for security and menu behavior.
  • FIN_PLAN_PREFERENCE_CODE — the project's preference for the plan type, sourced from PA_PROJ_FP_OPTIONS.
  • LABOR_QUANTITY — summed labor hours, conditionally filtered by REPORT_LABOR_HRS_FROM_CODE and VERSION_TYPE.
  • COST — the summed cost figure, computed differently depending on whether MARGIN_DERIVED_FROM_CODE is 'R' (raw cost) or 'B' (burdened cost), and adjusted for lent resources, unassigned time, inter-project transfers, and cost adjustments.
  • Revenue-related aggregate columns — derived from BV.REVENUE and BV.TOTAL_PROJECT_REVENUE with transfer revenue adjustments.

Common Use Cases and Queries

Typical scenarios include reconstructing the Plan Types page data for a project, auditing which plan types are active and how they roll up financially, and feeding project financial summaries into custom reports. A basic retrieval for a single project:

  • SELECT project_id, name, fin_plan_type_code, plan_class_code, security_plan_class_code, fin_plan_preference_code, labor_quantity, cost FROM apps.pa_fin_plan_types_w_v WHERE project_id = :p_project_id;

To compare preference codes across projects, join the view to PA_PROJECTS and aggregate. Because the view performs SUM aggregations over budget versions, results are returned per plan type rather than per version, so callers should not expect version-level granularity. Queries should always constrain PROJECT_ID where possible, since the package function call and aggregate scans are evaluated per project. When integrating, note the dependency on the PA_FIN_PLAN_TYPE_GLOBAL package; the view cannot be queried successfully if that package is invalid.