Search Results pqh_budget_pools

Overview

The PQH_BUDGET_POOLS table is a core data object within the Oracle E-Business Suite (EBS) Public Sector HR (PQH) module. It functions as the master definition table for budget reallocation pools. In the context of public sector budgeting, a pool represents a reservoir of funds within a specific budget version and for a particular budget measurement unit (BMU). This structure enables financial managers to aggregate and centrally manage budget amounts that are available for redistribution or reallocation across different positions, jobs, or organizational units, facilitating flexible budget control and planning within the constraints of a defined budget version.

Key Information Stored

The table's primary purpose is to uniquely define each budget pool. Its key columns, as indicated by the primary and unique keys, are essential for this identification and integrity. The POOL_ID column serves as the table's primary surrogate key. For functional uniqueness, the combination of BUDGET_VERSION_ID and BUDGET_UNIT_ID forms a unique key, ensuring only one pool can exist for a given unit within a specific budget version. The BUDGET_VERSION_ID is a foreign key linking the pool to its parent PQH_BUDGET_VERSIONS record, anchoring the pool to a specific budget cycle. The BUDGET_UNIT_ID is a foreign key to PER_SHARED_TYPES, which classifies the type of budget measurement unit (e.g., a specific position, job, or organization) to which the pool's funds are allocated and from which reallocations are managed.

Common Use Cases and Queries

This table is central to budget reallocation processes. A common operational use case is verifying the existence of a pool before creating reallocation transactions or generating reports on available pool balances. Typical queries involve joining with related budget and shared type tables for comprehensive reporting. For example, to list all pools for a specific budget version with descriptive information, a query might join PQH_BUDGET_POOLS to PQH_BUDGET_VERSIONS and PER_SHARED_TYPES. Another critical use case is ensuring data integrity during budget setup, where administrators must confirm that a unique pool is defined for each required budget unit within a version. SQL queries often filter on BUDGET_VERSION_ID for version-specific analysis or on BUDGET_UNIT_ID to track fund pools across different budget cycles for a particular unit type.

Related Objects

As per the provided metadata, PQH_BUDGET_POOLS has integral relationships with several other EBS objects. It is a parent table to PQH_BDGT_POOL_REALLOCTIONS via the POOL_ID foreign key, meaning individual reallocation transactions are stored in that child table. It is a child table to PQH_BUDGET_VERSIONS, deriving its budget context from that master budget definition. The link to PER_SHARED_TYPES via BUDGET_UNIT_ID provides the classification for the budget measurement unit. Consequently, any processes, reports, or interfaces involving budget reallocations will typically traverse from PQH_BUDGET_VERSIONS to PQH_BUDGET_POOLS and then to PQH_BDGT_POOL_REALLOCTIONS, forming the core data model for the reallocation functionality within Public Sector HR.