Search Results worksheet_bdgt_elmnt_id




Overview
Explore in AI Chat

Overview

The PQH_WORKSHEET_BDGT_ELMNTS table is a core data object within the Oracle E-Business Suite Public Sector HR (PQH) module, specifically for versions 12.1.1 and 12.2.2. It serves a critical function in the budgeting and workforce planning processes by storing the element-wise distribution of measurement units. In essence, this table acts as a junction that breaks down a high-level budget set into its constituent compensation elements, such as salaries, allowances, or benefits. It enables detailed budgetary control by associating specific budgeted amounts or units (like headcount or full-time equivalents) with individual payroll elements, forming the granular foundation for budget worksheets and financial analysis.

Key Information Stored

The table's structure is designed to link budget sets with specific payroll elements and track their distribution. The primary identifier is the WORKSHEET_BDGT_ELMNT_ID, a system-generated primary key. Two other columns form a unique constraint, defining the core relationship: WORKSHEET_BUDGET_SET_ID links the record to a parent budget set defined in the PQH_WORKSHEET_BUDGET_SETS table, and ELEMENT_TYPE_ID identifies the specific payroll element (likely referencing PAY_ELEMENT_TYPES_F). While the full column list is not provided in the excerpt, the table's description implies it contains columns to store the distributed measurement units (e.g., quantity, percentage, or amount) allocated to each element within the budget set.

Common Use Cases and Queries

This table is central to generating detailed budget reports and ensuring payroll costs align with allocated budgets. A common operational use case is reviewing all elements and their allocated units for a specific budget worksheet. For reporting, analysts frequently join this table to element and budget set descriptions to produce human-readable summaries. A typical query pattern involves filtering by the worksheet budget set to analyze its composition:

  • SELECT pwbe.WORKSHEET_BDGT_ELMNT_ID, pwbe.ELEMENT_TYPE_ID, petf.ELEMENT_NAME, pwbe.MEASUREMENT_UNIT_VALUE
  • FROM HR.PQH_WORKSHEET_BDGT_ELMNTS pwbe,
  • APPS.PAY_ELEMENT_TYPES_F petf,
  • HR.PQH_WORKSHEET_BUDGET_SETS pwbs
  • WHERE pwbe.WORKSHEET_BUDGET_SET_ID = pwbs.WORKSHEET_BUDGET_SET_ID
  • AND pwbe.ELEMENT_TYPE_ID = petf.ELEMENT_TYPE_ID
  • AND pwbs.WORKSHEET_BUDGET_SET_ID = :p_budget_set_id;

Data in this table is typically created and maintained through the application's dedicated budgeting screens and workflows, not via direct SQL manipulation.

Related Objects

The table exists within a well-defined schema relationship, as documented in the ETRM metadata. Its integrity is maintained through specific foreign key constraints.

  • Parent Table (Referenced Foreign Key): PQH_WORKSHEET_BDGT_ELMNTS.WORKSHEET_BUDGET_SET_ID references PQH_WORKSHEET_BUDGET_SETS. This defines the parent-child relationship where a budget set contains multiple budget elements.
  • Child Table (Referencing Foreign Key): PQH_WORKSHEET_FUND_SRCS.WORKSHEET_BDGT_ELMNT_ID references PQH_WORKSHEET_BDGT_ELMNTS. This indicates that each detailed budget element can be further broken down by funding source, creating a hierarchical data model for granular budget tracking.