Search Results pqh_element_commitments




Overview
Explore in AI Chat

Overview

The PQH_ELEMENT_COMMITMENTS table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It is designed to capture and store element commitment data for specific budgetary periods. In the context of public sector budgeting and compensation management, an element commitment represents a formal allocation or earmarking of funds associated with a particular compensation or benefits element (e.g., a specific allowance, differential, or benefit) against a defined budget version. This table enables organizations to plan, track, and control personnel-related expenditures by linking detailed compensation components to the broader budgetary framework, ensuring financial accountability and alignment with approved budgets.

Key Information Stored

The table's primary purpose is to record commitments tied to individual compensation elements. While the full column list is not detailed in the provided metadata, the structure revolves around a unique identifier and key foreign keys. The primary key, ELEMENT_COMMITMENT_ID, uniquely identifies each commitment record. A critical foreign key column is BUDGET_VERSION_ID, which links each commitment to a specific budget definition in the PQH_BUDGET_VERSIONS table. Other columns typically found in such a structure would include identifiers for the specific compensation element (likely an ELEMENT_TYPE_ID or ELEMENT_ENTRY_ID), the commitment amount, the effective date or period for the commitment, and audit columns such as CREATION_DATE and LAST_UPDATE_DATE. The table essentially serves as a junction between budget versions and detailed compensation elements.

Common Use Cases and Queries

This table is central to budgetary control and reporting in Public Sector HR. A primary use case is generating reports that compare committed personnel costs against budgeted amounts for a given fiscal period or budget version. Financial analysts may query this table to analyze commitment trends by element type or to identify areas of potential budget overrun. Common SQL patterns involve joining to PQH_BUDGET_VERSIONS for budget details and to element-related tables (like PAY_ELEMENT_TYPES_F) for element descriptions. A foundational query would be:

SELECT ec.element_commitment_id,
       ec.budget_version_id,
       bv.budget_name,
       ec.element_entry_id,
       ec.commitment_amount
FROM   hr.pqh_element_commitments ec,
       hr.pqh_budget_versions bv
WHERE  ec.budget_version_id = bv.budget_version_id
AND    bv.budget_unit_id = :p_unit_id;

This table is also critical during the budget preparation and revision cycles, where new commitments are created or existing ones are adjusted.

Related Objects

The PQH_ELEMENT_COMMITMENTS table has defined relationships with other key Public Sector HR objects, primarily through foreign key constraints. Based on the provided metadata:

  • PQH_BUDGET_VERSIONS: This is the primary parent table. The foreign key PQH_ELEMENT_COMMITMENTS.BUDGET_VERSION_ID references PQH_BUDGET_VERSIONS. This relationship ensures every element commitment is associated with a valid, approved budget version.

While not listed in the provided excerpt, this table would logically have relationships with core HR and Payroll tables to resolve the specific compensation element details, such as PAY_ELEMENT_TYPES_F or PAY_ELEMENT_ENTRIES_F. However, the documented and enforced relationship is explicitly with the PQH_BUDGET_VERSIONS table, anchoring it firmly within the Public Sector HR budgeting subsystem.