Search Results pre_defined_flag




Overview
Explore in AI Chat

Overview

PA_FINPLAN_TYPES_V is a consolidated Oracle E-Business Suite view owned by the APPS schema within the Projects (PA) module. Its purpose is to present every valid budget type and financial plan type that a project may use for its various business functions. Rather than forcing reporting and integration consumers to query multiple base tables and resolve context-sensitive LOV logic themselves, the view delivers a single, unified result set combining both legacy budget types and the newer financial plan types.

The view is classified as VALID in ETRM for both 12.1.1 and 12.2.2, and it exposes a discriminator column, FP_TYPE_CODE, whose values are either 'BUDGET_TYPE' or 'PLAN_TYPE'. This distinguishes the origin of each row. Because the view is project-context sensitive, it relies on PA_BUDGET_PUB.GET_PROJECT_ID to determine the current project, meaning results can vary depending on the runtime project context established by the calling form, report, or concurrent program. Typical consumers include project setup forms, budgeting and forecasting pages, and custom reporting solutions that need to enumerate the plan types available to a given project.

Underlying Base Objects

The documented base objects referenced by PA_FINPLAN_TYPES_V are:

  • PA_BUDGET_TYPES (synonym) — source of legacy budget type rows.
  • PA_FIN_PLAN_TYPES_B (synonym) — base table for financial plan type definitions.
  • PA_FIN_PLAN_TYPES_VL (view) — the multilingual (translated) view over plan types, supplying name and description.
  • PA_PROJ_FP_OPTIONS (synonym) — project-level financial plan options that determine which plan types are enabled.
  • PA_BUDGET_PUB (package) — provides GET_PROJECT_ID, used to bind the query to the active project context.

The definition is a UNION of two branches. The first branch selects from PA_BUDGET_TYPES with a synthetic FIN_PLAN_TYPE_ID of -1, filtering out the FORECASTING_BUDGET_TYPE and restricting to budget types active on the current date (START_DATE_ACTIVE through NVL(END_DATE_ACTIVE, SYSDATE)). It further excludes any budget type already migrated to a financial plan type, as detected through the NOT EXISTS subquery against PA_FIN_PLAN_TYPES_B and PA_PROJ_FP_OPTIONS. The second branch joins PA_FIN_PLAN_TYPES_VL to PA_PROJ_FP_OPTIONS, returning the actual plan type ID, translated name and description, plan class, workflow flag, approved cost/revenue plan type flags, primary forecast flags, and workplan usage flag. A mapped column, PO.FIN_PLAN_PREFERENCE_CODE exposed as BUDGET_AMOUNT_CODE, carries through the project-specific preference setting.

Key Columns

Common Use Cases and Queries

Typical uses include populating LOVs for plan type selection, validating plan type eligibility on project forms, and building custom budget-versus-forecast comparison reports. Because filtering depends on project context, queries are usually invoked inside a form or after PA_BUDGET_PUB has been primed with a project ID.

Listing all available plan types for the current project context:

SELECT fin_plan_type_id, name, description, fp_type_code,
       approved_cost_plan_type_flag, approved_rev_plan_type_flag,
       primary_cost_forecast_flag, primary_rev_forecast_flag
FROM   apps.pa_finplan_types_v
ORDER BY fp_type_code, name;

Separating legacy budget types from migrated plan types:

SELECT fp_type_code, COUNT(*)
FROM   apps.pa_finplan_types_v
GROUP BY fp_type_code;

Identifying the primary forecast plan types in use:

SELECT name, description, plan_class_code
FROM   apps.pa_finplan_types_v
WHERE  fp_type_code = 'PLAN_TYPE'
AND    NVL(primary_cost_forecast_flag,'N') = 'Y';

Developers should note that the view is context-dependent and returns rows conditionally based on active date ranges and migration status; results therefore cannot be assumed identical across projects or over time.