Search Results pqh_budget_versions




Overview
Explore in AI Chat

Overview

The PQH_BUDGET_VERSIONS table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It serves as the primary repository for budget version records, which represent specific iterations or snapshots of a budget over a defined date range. Each record in this table is a child of a master budget header defined in the PQH_BUDGETS table. The table's central role is to manage the lifecycle of budgeting activities, enabling organizations to create, revise, and track different versions of a budget for planning, forecasting, and commitment tracking purposes within the public sector HR context.

Key Information Stored

While the provided metadata does not list specific columns, the table's primary key is BUDGET_VERSION_ID, which uniquely identifies each budget version. A critical foreign key column is BUDGET_ID, which links the version to its parent budget definition in the PQH_BUDGETS table. Based on its description as "Budget for a date range," the table likely contains columns to define the effective start and end dates for the version, a version number or name for identification, status indicators (e.g., Draft, Approved), and potentially summary financial amounts. The structure supports maintaining a history of budget changes and multiple concurrent budget scenarios.

Common Use Cases and Queries

A primary use case is the generation of reports to analyze budget versions across different master budgets or to track the progression of a single budget through its revision history. Administrators may run queries to identify all active budget versions within a specific period or to audit the relationships between budget versions and their associated details and commitments. Common SQL patterns include joining to the parent PQH_BUDGETS table to retrieve master budget information and filtering on date columns to find versions effective for a given payroll or accounting period. For example, a query to list all budget versions for a specific budget might follow this pattern:

  • SELECT bv.* FROM pqh_budget_versions bv, pqh_budgets b WHERE bv.budget_id = b.budget_id AND b.budget_name = '<BUDGET_NAME>' ORDER BY bv.effective_start_date DESC;

Related Objects

The PQH_BUDGET_VERSIONS table is a central node in the Public Sector HR budgeting schema, with documented relationships to several key tables. It references the PQH_BUDGETS table via the BUDGET_ID column, establishing the version's parent budget. More significantly, it is referenced as a parent table by multiple detail and transaction tables, forming the backbone of the budgeting data model. The documented foreign keys referencing PQH_BUDGET_VERSIONS are:

  • PQH_BUDGET_DETAILS via BUDGET_VERSION_ID: Stores granular budget line items for each version.
  • PQH_BUDGET_POOLS via BUDGET_VERSION_ID: Manages pooled budget resources associated with a version.
  • PQH_ELEMENT_COMMITMENTS via BUDGET_VERSION_ID: Tracks salary and benefit commitments against the budget version.
  • PQH_WORKSHEETS via BUDGET_VERSION_ID: Holds worksheet data used for budget planning and analysis.

These relationships indicate that the BUDGET_VERSION_ID is propagated to subordinate tables to maintain data integrity and provide a complete audit trail for all transactions and details pertaining to a specific budget version.