Search Results cost_only




Overview
Explore in AI Chat

Overview

APPS.PA_FIN_PLAN_CREATE_PLAN_NOBV_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that supports the creation of financial plans and budget versions. The view consolidates financial plan option settings configured at the project level and resolves them into a single, normalized row per project and financial plan type. Its design is driven by the fin_plan_preference_code attribute on PA_PROJ_FP_OPTIONS, which determines whether cost and revenue planning are handled together or separately. The view applies conditional DECODE logic so that the "generic" columns it exposes—such as plan_level_code, time_phased_code, and resource_list_id—are populated from the correct cost, revenue, or combined source column depending on the preference selected.

The suffix "NOBV" indicates this view does not involve budget version records, distinguishing it from companion views that handle version-level plan creation. Because the source of truth for plan preference is stored in a coded, preference-dependent format, the view exists to simplify consumption by concurrent programs, APIs, and reporting tools that require a flat, denormalized projection. The term "revenue_only" relates directly to one of the supported fin_plan_preference_code values, for which the view directs all generic planning attributes to the revenue-specific source columns.

Underlying Base Objects

The view is defined over three documented objects:

  • PA_PROJ_FP_OPTIONS (referenced via a synonym): Holds project-level financial plan preference settings, including cost, revenue, and combined plan level, time-phasing, and resource list columns, keyed by project_id.
  • PA_FIN_PLAN_TYPES_VL: The financial plan type definition view, supplying fin_plan_type_code and plan_type_name.
  • PA_FIN_PLAN_CREATE_VER_GLOBAL (package): Provides session-scoped functions such as get_project_id, get_pa_current_start_period, and get_gl_current_start_period, which the view calls to derive start period names when time phasing is enabled.

The join reconciles project-level options against plan types, and the package functions supply dynamic context values at query time.

Key Columns

  • project_id: Project identifier linking the row to the project.
  • fin_plan_type_code / plan_type_name: The financial plan type and its descriptive name.
  • fin_plan_preference_code: The controlling preference (for example, COST_ONLY, REVENUE_ONLY, COST_AND_REV_SEP, COST_AND_REV_SAME).
  • plan_level_code: The resolved planning level for the preference.
  • time_phased_code: The resolved time-phasing indicator (for example, P for PA period, G for GL period).
  • resource_list_id: The resolved resource list associated with the preference.
  • Cost-, revenue-, and combined-prefixed variants (cost_plan_level_code, revenue_time_phased_code, etc.) expose the individual source settings when "COST_AND_REV_SEP" is used.
  • cost_start_period_name and related period columns: Derived via the package functions when time phasing applies.

Common Use Cases and Queries

The view is typically used to determine what planning defaults apply to a project before programmatically creating a financial plan. A common pattern is to filter by preference to isolate revenue-driven configurations:

  • Retrieve all projects configured for revenue-only planning: SELECT project_id, plan_type_name FROM pa_fin_plan_create_plan_nobv_v WHERE fin_plan_preference_code = 'REVENUE_ONLY';
  • Inspect resolved defaults for a single project: SELECT plan_level_code, time_phased_code, resource_list_id FROM pa_fin_plan_create_plan_nobv_v WHERE project_id = :p_project_id;
  • Compare cost and revenue settings where plans are separated: query the cost- and revenue-prefixed columns when fin_plan_preference_code = 'COST_AND_REV_SEP'.

Because the view invokes package functions, callers should be aware that it relies on session context supplied by PA_FIN_PLAN_CREATE_VER_GLOBAL, and results can vary with the active project or ledger environment.