Results for “pa_fin_plan_create_plan_bv_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PA_FIN_PLAN_CREATE_PLAN_BV_V view is a Projects (PA) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as being used in the Create, View, and Edit Versions OA (Oracle Application) page, and its purpose is to retrieve information about a budget version given a budget version id. The view therefore acts as a presentation-layer data source that supplies a JSP/OA framework page with the descriptive, structural, and preference attributes of a single financial plan budget version, rather than serving as a standalone analytical reporting object. Because it is defined in the APPS schema and is a view rather than a table, it provides no persistent storage; it materializes its result set at query time from the underlying project and budget version definitions. Its reliance on the PA_FIN_PLAN_CREATE_VER_GLOBAL package indicates that it is tightly coupled to the financial plan version creation and maintenance flow, and it is best understood as a lightweight accessor for version metadata rather than a general-purpose planning fact source.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_BUDGET_VERSIONS (synonym) — supplies the budget/financial plan version attributes, including version name, description, change reason, budget version id, record version number, budget status, period profile, version type, and descriptive flexfield (attribute) columns.
• PA_FIN_PLAN_TYPES_VL (view) — supplies the financial plan type code and translated plan type name.
• PA_PROJ_FP_OPTIONS (synonym) — supplies the project-level financial plan preference and the cost, revenue, and combined level, time-phased, and resource list options referenced by the DECODE logic.
• PA_FIN_PLAN_UTILS (package) — provides the GET_PERIOD_PROFILE_START_DATE and GET_PERIOD_PROFILE_END_DATE functions used to derive the start and end period names from the version's period profile.
• PA_FIN_PLAN_CREATE_VER_GLOBAL (package) — referenced for global state and context used during version creation and maintenance.

The join of these objects allows a single version identifier to be resolved into a fully described plan version, combining version-level data with project-level financial plan preferences and the human-readable plan type and period profile boundaries.

Key Columns

The view exposes identifiers and descriptive fields alongside preference-driven behavioral attributes:

• PROJECT_ID, BUDGET_VERSION_ID, RECORD_VERSION_NUMBER — the project and version keys plus the optimistic locking version number.
• VERSION_NAME, DESCRIPTION, CHANGE_REASON_CODE, BUDGET_STATUS_CODE — descriptive and status attributes of the version.
• FIN_PLAN_TYPE_CODE, PLAN_TYPE_NAME — the financial plan type and its translated name.
• FIN_PLAN_PREFERENCE_CODE — the project's financial plan preference, which drives the conditional logic for the derived columns.
• PLAN_LEVEL_CODE, TIME_PHASED_CODE, RESOURCE_LIST_ID — derived through DECODE expressions that select the cost, revenue, combined-separate, or combined-same option depending on the preference and, where relevant, the version type.
• START_PERIOD_NAME, END_PERIOD_NAME — returned by the period profile functions. END_PERIOD_NAME in particular is the last period of the version's period profile, and is the term most commonly searched in relation to this view.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE(n) — descriptive flexfield context and segment values.

Common Use Cases and Queries

Because the view is designed for a specific OA page, it is most frequently queried by the page controller, but it is also useful for ad hoc inspection of a plan version's configuration. A typical retrieval by version id is:

• SELECT version_name, plan_type_name, budget_status_code, start_period_name, end_period_name FROM pa_fin_plan_create_plan_bv_v WHERE budget_version_id = :p_version_id; — resolves a version into its descriptive and period boundary attributes.
• SELECT project_id, budget_version_id, end_period_name, plan_level_code, time_phased_code FROM pa_fin_plan_create_plan_bv_v WHERE project_id = :p_project_id ORDER BY version_name; — lists all plan versions for a project with their derived planning behavior.
• Diagnostic queries comparing PLAN_LEVEL_CODE or TIME_PHASED_CODE across versions help confirm that the project-level financial plan preference and version type are being interpreted as intended.

Users should recognize that the derived columns depend on FIN_PLAN_PREFERENCE_CODE and VERSION_TYPE; if the project's financial plan options change, the values returned for existing versions may change accordingly. The view performs no aggregation, so it is suited to single-version inspection rather than financial plan reporting or totals.