Results for “pafv_budget_versions”

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

Overview

PAFV_BUDGET_VERSIONS is an APPS-owned business view in the Oracle E-Business Suite Projects (PA) module that exposes information about versions of project budgets. In EBS 12.1.1 and 12.2.2, the view presents a denormalized, reporting-friendly projection of budget version records by joining the core budget version table to project, budget type, resource list, and person reference data, and by resolving several coded columns into their lookup meanings in-line. Its name follows the PA "FV" convention for formatted business views, indicating that the columns are pre-decorated with lookup translations via the EBS descriptor mechanism (the "_LA:", "_DF:", and "_SEC:" prefixes visible in the view text) rather than returning raw codes. This makes the view suitable for direct consumption in Oracle Reports, BI Publisher datasets, OAF pages, and ad-hoc SQL without additional joins to FND_LOOKUPS or PA_LOOKUPS.

Underlying Base Objects

The view is defined over five referenced base objects, all accessed through APPS synonyms:

• PA_BUDGET_VERSIONS (alias PBV) — the driving table containing budget version header data.
• PA_PROJECTS_ALL (alias PPA) — joined on PROJECT_ID to supply project name and project number (SEGMENT1); also enforces the org security predicate "_SEC:PPA.ORG_ID".
• PA_BUDGET_TYPES (alias PBT) — joined on BUDGET_TYPE_CODE to return the descriptive budget type.
• PA_RESOURCE_LISTS_ALL_BG (alias PRLA) — joined on RESOURCE_LIST_ID to give the resource list name.
• PER_ALL_PEOPLE_F (alias PAP) — outer-joined on BASELINED_BY_PERSON_ID (with the (+) operator) and constrained to the row effective at TRUNC(SYSDATE), yielding the baselining person's FULL_NAME.

The view is created WITH READ ONLY, so it cannot be used as a DML target. The security predicate on PPA.ORG_ID ensures only projects visible to the operating unit context are returned.

Key Columns

The view exposes the budget version primary key (BUDGET_VERSION_ID), VERSION_NUMBER, VERSION_NAME, and DESCRIPTION, along with the parent PROJECT_ID, PROJECT_NAME, and PROJ (project number). Financial and effort measures include LABOR_QUANTITY, RAW_COST, BURDENED_COST, and REVENUE. Lookup-decorated columns include CURRENT_FLAG, ORIGINAL_FLAG, CURRENT_ORIGINAL_FLAG, BUDGET_STATUS, CHANGE_REASON, PM_PRODUCT, WF_STATUS, and LABOR_UNIT_OF_MEASURE. The user's search term, BASELINED_BY_PERSON_ID, is the foreign key to PER_ALL_PEOPLE_F identifying the person who baselined the version; the view also surfaces the resolved BASELINED_BY_PERSON_NAME (FULL_NAME) and the BASELINED_DATE. BUDGET_TYPE_CODE and BUDGET_TYPE, RESOURCE_LIST_ID and its name, PM_BUDGET_REFERENCE, and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) complete the projection. A descriptive flexfield column is rendered via the PA_BUDGET_VERSIONS_DESC_FLEX descriptor.

Common Use Cases and Queries

Typical uses include baseline audit reporting, budget version comparisons, and workflow status tracking. To find versions by the baselining person:

• Baselined budget audit: SELECT project_name, version_name, baselined_by_person_name, baselined_date FROM pafv_budget_versions WHERE baselined_by_person_id = :person_id ORDER BY baselined_date DESC;
• Current baselines per project: SELECT project_id, project_name, version_name, budget_status, baselined_date FROM pafv_budget_versions WHERE current_flag = 'Y';
• Cost and revenue summary by budget type: SELECT project_name, budget_type, SUM(raw_cost), SUM(burdened_cost), SUM(revenue) FROM pafv_budget_versions GROUP BY project_name, budget_type;

Because lookups are pre-resolved, filters such as BUDGET_STATUS = 'Baseline' or CURRENT_FLAG = 'Y' may be applied directly against the decorated columns.