Search Results dflt_budget_element_id

Overview

The PQH_DFLT_BUDGET_ELEMENTS table is a core data structure within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a child table that stores the specific budget elements which constitute a predefined budget set. A budget set is a template or default configuration used to streamline the budgeting process for positions or assignments, particularly in public sector organizations where funding sources and budgetary controls are complex and strictly regulated. This table's role is to define the individual line-item components—such as salary, benefits, or operational costs—that make up the total budget for a given set, enabling standardized and repeatable budget allocation.

Key Information Stored

The table's primary purpose is to link a budget element to its parent budget set and define its characteristics. The key columns, inferred from the provided metadata and standard Oracle design patterns, include:

• DFLT_BUDGET_ELEMENT_ID: The primary key (PK) uniquely identifying each budget element record.
• DFLT_BUDGET_SET_ID: A foreign key (FK) column linking the element to its parent budget set in the PQH_DFLT_BUDGET_SETS table. This defines the template to which the element belongs.
• Additional columns (not explicitly listed but typical for such structures) would likely store details like ELEMENT_TYPE_ID (linking to a lookup for salary, bonus, etc.), a distribution percentage or fixed amount, and sequence number for ordering elements within the set. The existence of the child table PQH_DFLT_FUND_SRCS suggests this table may also store or allow the specification of default funding source rules for each element.

Common Use Cases and Queries

This table is central to operations involving the creation, review, or application of default budget templates. A common use case is during position or vacancy budgeting, where a pre-defined budget set is applied to automatically generate budget lines. For reporting, administrators may query this table to audit or document the composition of all budget sets. A typical analytical query would join to the parent set table and potentially to lookup values for element types.

Sample Query: To list all budget elements for a specific budget set name:

SELECT bset.budget_set_name, belem.*
FROM pqh_dflt_budget_elements belem,
     pqh_dflt_budget_sets bset
WHERE belem.dflt_budget_set_id = bset.dflt_budget_set_id
AND bset.budget_set_name = '&BUDGET_SET_NAME';

Another critical use case involves data integrity checks, such as identifying orphaned budget elements that no longer reference a valid parent budget set.

Related Objects

The table exists within a defined hierarchy of budget default objects, as evidenced by the foreign key relationships documented in the ETRM.

• Parent Table (Referenced Foreign Key):
  • PQH_DFLT_BUDGET_SETS: The PQH_DFLT_BUDGET_ELEMENTS.DFLT_BUDGET_SET_ID column references the primary key of this table. This establishes that every budget element must belong to a valid budget set.
• Child Table (Referencing Foreign Key):
  • PQH_DFLT_FUND_SRCS: This table's DFLT_BUDGET_ELEMENT_ID column references the primary key of PQH_DFLT_BUDGET_ELEMENTS. This indicates that each budget element can have one or more default funding sources defined against it, further detailing the financial structure.

This relationship chain (PQH_DFLT_BUDGET_SETS → PQH_DFLT_BUDGET_ELEMENTS → PQH_DFLT_FUND_SRCS) forms a core data model for templatized budget configuration within the Public Sector HR module.