Results for “budgeted_entity”

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

Overview

PQH_BUDGET_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PQH (Public Sector HR) product family. It exposes budget detail information for organizations and positions that participate in position budgeting, consolidating data from the budget header, budget version, budget detail, and budget period entities into a single queryable structure. The view is a denormalized presentation layer designed to support budget analysis, position-level commitment and actual cost reporting, and integration extracts required by public sector and government customers who perform budgeting against a position hierarchy.

The view is valid in both EBS 12.1.1 and 12.2.2. It relies on several synonyms, packages, and other views rather than being defined directly over base tables, which means its behavior is largely governed by the PQH budget configuration and by the PL/SQL functions it invokes for derived columns.

Underlying Base Objects

The documented base objects referenced by PQH_BUDGET_DETAILS_V are:

• PQH_BUDGETS_V (VIEW) — supplies the budget definition attributes, including calendar, style, budgeted entity, organization structure, version, and the primary budget measurement unit.
• PQH_BUDGET_VERSIONS (SYNONYM) — provides the version identity and effective dates for each budget version.
• PQH_BUDGET_DETAILS (SYNONYM) — the position-level budget detail records, including the budgeted value per position.
• PQH_BUDGET_PERIODS (SYNONYM) — supplies budget period identifiers and period-level budgeted values.
• PER_TIME_PERIODS (SYNONYM) — joined to derive the beginning and ending dates used to build a readable budget period name.
• PQH_MGMT_RPT_PKG (PACKAGE) — exposes GET_POSITION_ACTUAL_CMMTMNTS, which computes commitment and actual amounts for a position within a budget version and date range.
• HR_GENERAL (PACKAGE) — supplies DECODE_ORGANIZATION and DECODE_POSITION_LATEST_NAME for resolving business group and position names.
• PQH_UTILITY (PACKAGE) — a supporting utility package in the PQH budget processing stack.

Because the view is built over other views, synonyms, and PL/SQL functions, its performance and output depend on the integrity of the underlying budget setup and on the execution cost of the package functions, which are evaluated per row.

Key Columns

The view exposes descriptive budget attributes alongside numeric budgeted, commitment, and actual values. Notable columns include:

• BUDGET_NAME, BUDGET_ID — identity of the budget definition.
• BUDGET_CALENDAR_NAME, BUDGET_CALENDAR_FREQUENCY — the period set and period type governing the budget cycle.
• BUDGET_START_DATE, BUDGET_END_DATE — the effective window of the budget.
• ORGANIZATION_HIERARCHY_NAME and ORGANIZATION_HIERARCHY_VERSION — the organization structure and the specific hierarchy version used for budgeting. This is the column named in the user search and is central to determining which hierarchy snapshot drives the budget.
• STARTING_ORGANIZATION_NAME — the organization at which hierarchy-based budgeting begins.
• BUDGET_MEASUREMENT_TYPE, BUDGET_UNIT_ID, BUDGET_UNIT_AGGREGATE — the unit of measure and aggregation level for budget amounts.
• BUDGET_VERSION_ID, BUDGET_VERSION_NUMBER, BUDGET_VERSION_START_DATE, BUDGET_VERSION_END_DATE — version identity and effective range.
• POSITION_ID, POSITION_NAME — the position to which budget detail applies.
• BUDGET_DETAIL_ID, BUDGET_DETAIL_BUDGETED_VALUE — the detail row and its budgeted amount.
• BUDGET_DETAIL_CMMTMNT_VALUE, BUDGET_DETAIL_ACTUAL_VALUE — commitment and actual amounts returned by PQH_MGMT_RPT_PKG for the position and budget window.
• BUDGET_PERIOD_ID, BUDGET_PERIOD_NAME, BUDGET_PERIOD_BUDGETED_VALUE — the budget period identity, a formatted date range string, and the period-level budgeted value.
• BUSINESS_GROUP_ID, BUSINESS_GROUP_NAME — the business group context for the budget.

Common Use Cases and Queries

Typical uses include reconciliation of budgeted versus committed and actual position costs, reporting by organization hierarchy version, and extraction of budget detail into external reporting or data warehouse environments. Analysts frequently filter on the hierarchy version and business group to reproduce a specific budget snapshot.

A representative query returning position-level budget versus commitment and actual values for a given hierarchy version is:

• SELECT budget_name, organization_hierarchy_name, organization_hierarchy_version, position_name, budget_detail_budgeted_value, budget_detail_cmmtmnt_value, budget_detail_actual_value FROM apps.pqh_budget_details_v WHERE organization_hierarchy_version = :p_version AND business_group_id = :p_bg AND budget_start_date >= :p_from ORDER BY budget_name, position_name;

A second common pattern aggregates period-level budgeted values by budget and calendar:

• SELECT budget_id, budget_name, budget_calendar_name, budget_period_name, SUM(budget_period_budgeted_value) period_total FROM apps.pqh_budget_details_v WHERE organization_hierarchy_version = :p_version GROUP BY budget_id, budget_name, budget_calendar_name, budget_period_name;

Because commitment and actual amounts are produced by PQH_MGMT_RPT_PKG.GET_POSITION_ACTUAL_CMMTMNTS on a per-row basis, queries that return large position sets should be constrained by business group, budget version, and hierarchy version to limit function executions and overall runtime.