Results for “pqh_budget_elements”

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

Overview

The PQH_BUDGET_ELEMENTS table resides in the HR schema and belongs to the Public Sector HR (PQH) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the element-wise distribution of a budget, meaning it defines how a parent budget set is allocated across individual budget elements and the percentage of the total that each element represents. The table acts as a child of PQH_BUDGET_SETS and as a parent for PQH_BUDGET_FUND_SRCS, forming the structural bridge between a budget definition and its associated funding sources.

Under the Data Vault classification heuristic derived from its foreign key topology, this table is characterized as satellite-leaning. In modeling terms, this suggests the object behaves primarily as a descriptive dependent of a hub-like parent (PQH_BUDGET_SETS), carrying attributes that qualify the budget set rather than representing an independent business entity. The presence of OBJECT_VERSION_NUMBER and audit columns further supports a slowly-changing, version-aware satellite interpretation.

Key Information Stored

The table is documented with ten columns. The surrogate primary key is BUDGET_ELEMENT_ID, enforced by the PQH_BUDGET_ELEMENTS_PK constraint. A separate unique index, PQH_BUDGET_ELEMENTS_UK, defines the business-key candidate as the combination of BUDGET_SET_ID and ELEMENT_TYPE_ID, ensuring that a given element type appears only once per budget set.

• BUDGET_ELEMENT_ID — Surrogate primary key uniquely identifying each budget element row.
• BUDGET_SET_ID — Foreign key to PQH_BUDGET_SETS, tying the element to its parent budget set.
• ELEMENT_TYPE_ID — Identifier for the budget element type being distributed.
• DISTRIBUTION_PERCENTAGE — The proportional share of the budget allocated to this element.
• OBJECT_VERSION_NUMBER — Optimistic locking and versioning column.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit trail columns.
• CREATED_BY, CREATION_DATE — Creation audit columns.

Common Use Cases and Queries

Typical reporting scenarios include validating that distribution percentages sum correctly across a budget set, joining elements to their funding sources, and auditing recent changes. A representative query retrieves all elements for a budget set:

• SELECT BUDGET_ELEMENT_ID, ELEMENT_TYPE_ID, DISTRIBUTION_PERCENTAGE FROM PQH_BUDGET_ELEMENTS WHERE BUDGET_SET_ID = :p_set_id;
• SELECT e.ELEMENT_TYPE_ID, e.DISTRIBUTION_PERCENTAGE, f.* FROM PQH_BUDGET_ELEMENTS e JOIN PQH_BUDGET_FUND_SRCS f ON f.BUDGET_ELEMENT_ID = e.BUDGET_ELEMENT_ID;
• Aggregate check: SELECT BUDGET_SET_ID, SUM(DISTRIBUTION_PERCENTAGE) FROM PQH_BUDGET_ELEMENTS GROUP BY BUDGET_SET_ID HAVING SUM(DISTRIBUTION_PERCENTAGE) <> 100;
• Change audit: filter on LAST_UPDATE_DATE to identify recently modified distributions.

Related Objects

• PQH_BUDGET_SETS — Parent table referenced via BUDGET_SET_ID; defines the governing budget set.
• PQH_BUDGET_FUND_SRCS — Child table referencing BUDGET_ELEMENT_ID; holds funding source detail per element.
• PQH budget maintenance APIs and concurrent programs that insert, update, or validate budget element distributions.
• Element type validation views that resolve ELEMENT_TYPE_ID to descriptive element names.