Search Results plan_level_code




Overview
Explore in AI Chat

Overview

APPS.PA_FIN_PLAN_CREATE_PLAN_BV_V is a financial-planning view in Oracle EBS Projects (PA) that presents the resolved plan attributes for a budget version being created or edited through the Financial Plan creation flow. It is a "BV" (budget version) view purpose-built for the Create Financial Plan UI and its supporting logic, rather than a general-purpose reporting view. Its central role is to translate a project's stored financial plan preference into concrete defaults for plan level, time-phasing, and resource list, so the Create Plan page and downstream APIs can present a single, consistent set of attributes for the version in context.

The view is significant because it encodes the branching logic for the preference code COST_AND_REV_SAME — the value referenced by the search term cost_and_rev_same. When a project plans cost and revenue together, the view returns the combined ("all") plan level, time-phased code, and resource list; when cost and revenue are planned separately, it resolves default attributes per version type. This makes the view the authoritative decoder of plan preferences during version creation.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is owned by APPS and defined over the following base objects:

  • PA_BUDGET_VERSIONS (SYNONYM) — supplies the budget version identity and descriptive attributes: budget_version_id, version_name, description, change_reason_code, version_type, budget_status_code, record_version_number, period_profile_id, and the attribute1..15 descriptive flexfield columns.
  • PA_PROJ_FP_OPTIONS (SYNONYM) — supplies the project's financial plan preference (fin_plan_preference_code) and the preference-specific codes for cost, revenue, or combined plans (plan level, time-phased, resource list).
  • PA_FIN_PLAN_TYPES_VL (VIEW) — supplies the plan type code and translated name joined to the version.
  • PA_FIN_PLAN_CREATE_VER_GLOBAL (PACKAGE) — used in the WHERE clause via get_project_id to constrain the result to the project currently in the Create Version context.
  • PA_FIN_PLAN_UTILS (PACKAGE) — supplies Get_Period_Profile_Start_Date and Get_Period_Profile_End_Date to derive start and end period names from the period profile.

The view is therefore a join-and-decode layer that does not store data itself; it resolves a single logical row for the version being created.

Key Columns

  • project_id, budget_version_id — identity of the project and version.
  • version_name, description, change_reason_code, version_type — descriptive version attributes.
  • fin_plan_type_code, plan_type_name — the financial plan type and its display name.
  • fin_plan_preference_code — the driving preference (COST_ONLY, REVENUE_ONLY, COST_AND_REV_SEP, COST_AND_REV_SAME).
  • plan_level_code — decoded plan level; for COST_AND_REV_SAME it returns all_fin_plan_level_code.
  • time_phased_code — decoded time-phasing; for COST_AND_REV_SAME it returns all_time_phased_code.
  • resource_list_id — decoded resource list; for COST_AND_REV_SAME it returns all_resource_list_id.
  • budget_status_code, record_version_number — workflow/status and concurrency control.
  • start_period_name, end_period_name — derived from the period profile.
  • attribute_category and attribute1..15 — version DFF columns.

Common Use Cases and Queries

The view is typically queried during plan creation to seed defaults, or by extensions validating preference resolution. Because results are filtered by PA_FIN_PLAN_CREATE_VER_GLOBAL.get_project_id, it returns data only within the Create Version session context.

  • Confirming how COST_AND_REV_SAME resolves plan level and time-phasing.
  • Populating Create Plan page defaults for a version.
  • Integration diagnostics for financial plan setup.

Sample query:

SELECT project_id, budget_version_id, version_name, fin_plan_preference_code, plan_level_code, time_phased_code, resource_list_id, start_period_name, end_period_name FROM apps.pa_fin_plan_create_plan_bv_v WHERE fin_plan_preference_code = 'COST_AND_REV_SAME';

Note that effective use requires the Create Version context to be initialized; outside that context the join to get_project_id may return no rows.