Search Results people_quantity




Overview
Explore in AI Chat

Overview

APPS.PA_FIN_PLAN_TYPES_B_V is a non-supported, internal Oracle E-Business Suite view in the Projects (PA) schema that exposes the base definition of financial plan types. In Oracle EBS 12.1.1 and 12.2.2, financial plan types drive how budgets, forecasts, and resource plans are structured and validated within the Project Management and Project Costing modules. The view presents the header-level attributes of each financial plan type, including the planning class it belongs to, flags controlling quantity and amount tracking, and behavioral controls such as versioning and baseline editing.

The view is deployed to support standard Oracle Applications programs and is not referenced by any database object; consequently it is a leaf-level read-only object. Oracle explicitly warns against customer access outside standard applications code. Its principal relevance to reporting is as a denormalized, query-friendly projection of plan type metadata that avoids requiring joins across the two-language (VL) view and the global package.

Because the object name ends in _B_V, it represents the base-table layer of a translated entity. The companion entity is PA_FIN_PLAN_TYPES_VL, which surfaces translatable name columns; this view exposes the untranslated base row structure.

Underlying Base Objects

Documented dependencies for the view are:

Reference to a package rather than a table means certain columns may be evaluated dynamically. The PROJECT_ID column indicates the view can be filtered or joined by project context, because plan type behavior may be project-specific through PA_PROJ_FP_OPTIONS.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating configuration, checking which plan types expose utilization measures, and supporting integrations that map external planning tools to EBS plan type behavior. A representative query listing utilization-capable plan types follows:

SELECT fin_plan_type_id, name, fin_plan_type_code, plan_class_code, total_utilization_hours, total_utilization_percent FROM apps.pa_fin_plan_types_b_v WHERE total_utilization_percent IS NOT NULL;

A project-scoped query is also common:

SELECT name, versions_flag, allow_edit_after_baseline_flag FROM apps.pa_fin_plan_types_b_v WHERE project_id = :p_project_id;

These columns support both configuration audits and read-only diagnostics; any modification must occur through supported Oracle forms or programs.