Search Results use_for_workplan_flag




Overview
Explore in AI Chat

Overview

APPS.PA_FINPLAN_TYPES_V is a reporting and integration view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that presents a consolidated, project-context-aware list of financial plan types available to the Projects application. It bridges two historically distinct modeling constructs: legacy budget types stored in PA_BUDGET_TYPES and newer financial plan types stored in PA_FIN_PLAN_TYPES_B/VL. The view is defined with a UNION of two branches, each tagged by an FP_TYPE_CODE discriminator ('BUDGET_TYPE' or 'PLAN_TYPE'), allowing callers to enumerate valid plan types for a given project without hard-coding which repository the definition originates from.

The view is context-sensitive: particularly in its PLAN_TYPE branch, it is filtered against PA_PROJ_FP_OPTIONS for the project returned by PA_BUDGET_PUB.GET_PROJECT_ID, and against active date ranges (start_date_active through nvl(end_date_active, sysdate)). Because it resolves a project via a PL/SQL package call, the view must be queried within a session where the project context (e.g., FND_GLOBAL or the budget entry context used by PA_BUDGET_PUB) has been established.

Underlying Base Objects

The documented referenced objects are: PA_BUDGET_PUB (package), PA_BUDGET_TYPES (synonym), PA_FIN_PLAN_TYPES_B (synonym), PA_FIN_PLAN_TYPES_VL (view), and PA_PROJ_FP_OPTIONS (synonym).

  • PA_BUDGET_TYPES — source of the 'BUDGET_TYPE' branch. Rows are eligible only when budget_type_code <> 'FORECASTING_BUDGET_TYPE', the record is date-active, and no corresponding migrated row already exists in PA_FIN_PLAN_TYPES_B for the project.
  • PA_FIN_PLAN_TYPES_VL — translatable view over PA_FIN_PLAN_TYPES_B supplying the 'PLAN_TYPE' branch, joined to PA_PROJ_FP_OPTIONS at the PLAN_TYPE option level.
  • PA_PROJ_FP_OPTIONS — holds the per-project financial plan option configuration, including fin_plan_preference_code (exposed as budget_amount_code) and fin_plan_option_level_code.
  • PA_BUDGET_PUB — supplies get_project_id, resolving the current project context used to scope both branches.

Key Columns

  • fin_plan_type_id — surrogate identifier; -1 for the legacy BUDGET_TYPE branch, the real ID for PLAN_TYPE rows.
  • name / description — from budget_type or plan type name/description.
  • fp_type_code — discriminator: 'BUDGET_TYPE' or 'PLAN_TYPE'.
  • plan_class_code — populated only for PLAN_TYPE rows; NULL for budget types.
  • budget_type_code — populated only for BUDGET_TYPE rows; NULL otherwise.
  • budget_amount_code — budget_amount_code for budget types; fin_plan_preference_code for plan types.
  • pre_defined_flag, enable_wf_flag — seeded/workflow-enabled indicators carried from both branches.
  • approved_cost_plan_type_flag, approved_rev_plan_type_flag — approval semantics (PLAN_TYPE rows only).
  • primary_cost_forecast_flag, primary_rev_forecast_flag — primary forecast designation (PLAN_TYPE rows only).
  • use_for_workplan_flag — carried from PA_FIN_PLAN_TYPES_VL in the PLAN_TYPE branch; NULL for BUDGET_TYPE rows. This is the column sought by the search term and indicates whether a plan type may be used for workplan (task/assignment) planning.
  • migrated_frm_bdgt_typ_code — links a plan type back to its originating budget type.

Common Use Cases and Queries

The view is typically used to drive LOVs and validation routines in project financial planning, budget entry, and workplan setup. A representative query lists plan types available for workplan usage:

  • SELECT fin_plan_type_id, name, fp_type_code, plan_class_code, use_for_workplan_flag FROM apps.pa_finplan_types_v WHERE nvl(use_for_workplan_flag,'N') = 'Y';
  • SELECT fin_plan_type_id, name, budget_amount_code FROM apps.pa_finplan_types_v WHERE fp_type_code = 'PLAN_TYPE' AND approved_cost_plan_type_flag = 'Y';
  • SELECT name, fp_type_code, migrated_frm_bdgt_typ_code FROM apps.pa_finplan_types_v ORDER BY fp_type_code, name;

Because project scoping is resolved through PA_BUDGET_PUB.GET_PROJECT_ID and date filters are applied at runtime, results reflect the current project and active-date context of the session, making the view suitable for both interactive reporting and integration validation of plan-type selection.