Search Results proj_fin_planning_options_id




Overview

The view APPS.PA_FIN_PLAN_TYPES_W_V is an Oracle Application Object Library (FND) design data view registered against the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as an internal, unsupported object: Oracle Corporation does not support direct access to application data through this view except from standard Oracle Applications programs. Its internal name carries the _W_V suffix, which indicates it is a translatable or "Who" style wrapper view presenting financial plan type definitions together with planning option attributes.

Functionally, the view exposes the catalogue of project financial plan types (for example Budget and Forecast plan types) along with the option flags that govern how each plan type behaves. It joins plan type metadata held on PA_FIN_PLAN_TYPES_VL with per-plan-type options stored on PA_PROJ_FP_OPTIONS. Because the query surface includes the column PROJ_FIN_PLANNING_OPTIONS_ID — the primary key of PA_PROJ_FP_OPTIONS — the view is most relevant to users investigating how a financial plan type's planning options are identified and linked to project-level or global configuration. It is a read-only reporting construct rather than a table, and no database object references it, so it serves purely as a query entry point.

Underlying Base Objects

The documented dependency list defines the objects over which the view is constructed:

  • PA_FIN_PLAN_TYPES_VL (VIEW) — the translated base view for financial plan types, supplying FIN_PLAN_TYPE_ID, FIN_PLAN_TYPE_CODE, PLAN_CLASS_CODE, NAME and related descriptive attributes.
  • PA_PROJ_FP_OPTIONS (SYNONYM) — the project financial planning options entity, which provides PROJ_FIN_PLANNING_OPTIONS_ID and the option flags such as GENERATED_FLAG, VERSIONS_FLAG, and ALLOW_EDIT_AFTER_BASELINE_FLAG.
  • PA_BUDGET_VERSIONS (SYNONYM) — the budget versioning table, referenced for version-related behaviour exposed through VERSIONS_FLAG.
  • PA_FIN_PLAN_TYPE_GLOBAL (PACKAGE) — a PL/SQL package invoked by the view definition, typically to derive global planning defaults, preference codes, or security plan class values at runtime.

The view therefore acts as a consolidated projection across plan type definition, planning options, budget versioning, and global package logic. PA_FIN_PLANNING_OPTIONS_ID in the output is the direct correlation to PA_PROJ_FP_OPTIONS, making it the join key sought by users who trace a plan type back to its options record.

Key Columns

  • PROJECT_ID — the project context under which the plan type and options combination applies.
  • FIN_PLAN_TYPE_ID / FIN_PLAN_TYPE_CODE — the surrogate key and code of the financial plan type.
  • NAME — the translated display name of the plan type from the VL view.
  • PLAN_CLASS_CODE and SECURITY_PLAN_CLASS_CODE — the plan classification (for example Budget vs Forecast) and the up-to 4000-character security class derivation.
  • PROJ_FIN_PLANNING_OPTIONS_ID — the identifier of the associated PA_PROJ_FP_OPTIONS row; the column the user searched for.
  • FIN_PLAN_PREFERENCE_CODE — default preference indicator for the plan type.
  • Measure flags: LABOR_QUANTITY, COST, REVENUE, MARGIN, MARGIN_PERCENT, HEAD_COUNT, TOTAL_UTILIZATION_HOURS, TOTAL_UTILIZATION_PERCENT, EQUIPMENT_QUANTITY, PEOPLE_QUANTITY — indicating which financial dimensions the plan type reports.
  • GENERATED_FLAG, VERSIONS_FLAG, ALLOW_EDIT_AFTER_BASELINE_FLAG — option controls governing generation, versioning and post-baseline editing.

Common Use Cases and Queries

The principal practical use is locating the planning options identifier for a given plan type and project, and reviewing which measures and flags a plan type exposes. A representative query is:

  • SELECT PROJECT_ID, FIN_PLAN_TYPE_ID, FIN_PLAN_TYPE_CODE, PLAN_CLASS_CODE, PROJ_FIN_PLANNING_OPTIONS_ID FROM APPS.PA_FIN_PLAN_TYPES_W_V WHERE PROJECT_ID = :p_project_id;
  • SELECT FIN_PLAN_TYPE_CODE, NAME, GENERATED_FLAG, VERSIONS_FLAG, ALLOW_EDIT_AFTER_BASELINE_FLAG FROM APPS.PA_FIN_PLAN_TYPES_W_V WHERE PLAN_CLASS_CODE = 'BUDGET';

Because access is unsupported outside standard Oracle programs, such queries should be used for diagnostic or integration reporting only, and joined back to PA_PROJ_FP_OPTIONS via PROJ_FIN_PLANNING_OPTIONS_ID to retrieve the full options record where deeper analysis is required.