Search Results pqh_element_commitments_ef_pk

Overview

The table PQH_ELEMENT_COMMITMENTS_EFC is a dedicated data object within the Oracle E-Business Suite (EBS) Public Sector Human Resources (PQH) module. As explicitly stated in its metadata, this table is a copy of the standard PQH_ELEMENT_COMMITMENTS table, specifically populated by the EFC (Euro as Functional Currency) process. It resides in the HR schema and carries a VALID status. The primary purpose of this table is to support multi-currency environments where the Euro is adopted as the functional currency. When an EFC conversion process runs, it replicates element commitment data into this table, ensuring that historical or transaction-level commitment amounts are accurately recorded and retrievable in the Euro denomination without altering the base table’s native currency data. This mechanism allows EBS to maintain both the original currency records and the converted Euro equivalents, thereby facilitating compliance, reporting, and financial consolidation in Euro-based public sector scenarios.

Key Information Stored

The table’s structure centers on two critical columns that form its composite primary key:

• ELEMENT_COMMITMENT_ID: This column is the primary identifier from the source table (PQH_ELEMENT_COMMITMENTS) and uniquely identifies a specific element commitment record prior to any currency conversion.
• EFC_ACTION_ID: This column links the record to a specific Euro functional currency conversion action, as defined in the HR_EFC_ACTIONS table. It captures the instance of the conversion run that generated this copy.

Together, these columns form the primary key constraint PQH_ELEMENT_COMMITMENTS_EF_PK. Additional columns in this table mirror those of its source, including commitment amounts (stored in Euro equivalent), element links, assignment identifiers, effective dates, and status flags. The table retains a full copy of the commitment data but transforms the monetary values to the Euro functional currency based on the conversion rates and methodology defined for the associated EFC action.

Common Use Cases and Queries

Typical use cases for PQH_ELEMENT_COMMITMENTS_EFC include auditing historical commitment data converted to Euros, reconciling financial reports after an EFC process, and supporting data migration or system consolidation projects. The following sample SQL patterns illustrate practical access:

• Retrieve all Euro-converted commitments for a specific action:
  SELECT ec.ELEMENT_COMMITMENT_ID, ec.EFC_ACTION_ID, ec.commitment_amount_efc
FROM PQH_ELEMENT_COMMITMENTS_EFC ec
WHERE ec.EFC_ACTION_ID = :p_action_id;
• Join with HR_EFC_ACTIONS to get conversion details:
  SELECT ec.ELEMENT_COMMITMENT_ID, ea.effective_date, ea.conversion_rate
FROM PQH_ELEMENT_COMMITMENTS_EFC ec, HR_EFC_ACTIONS ea
WHERE ec.EFC_ACTION_ID = ea.EFC_ACTION_ID;
• Compare original commitment versus Euro equivalent:
  SELECT a.ELEMENT_COMMITMENT_ID, a.commitment_amount AS original_amount, b.commitment_amount AS eur_amount
FROM PQH_ELEMENT_COMMITMENTS a, PQH_ELEMENT_COMMITMENTS_EFC b
WHERE a.ELEMENT_COMMITMENT_ID = b.ELEMENT_COMMITMENT_ID;

Related Objects

Based on the documented metadata, the primary related object is:

• HR_EFC_ACTIONS: This table stores the overarching Euro functional currency conversion actions. The PQH_ELEMENT_COMMITMENTS_EFC table references it via the foreign key column EFC_ACTION_ID. The relationship is:
  PQH_ELEMENT_COMMITMENTS_EFC.EFC_ACTION_ID → HR_EFC_ACTIONS.EFC_ACTION_ID

Additionally, the source table PQH_ELEMENT_COMMITMENTS is indirectly related, as the EFC table is a copy of its structure. However, no formal foreign key constraint between these two tables is documented. Other objects in the PQH schema, such as element entry tables and pay-related EFC views, may also depend on this table for reporting and conversion validation, though the metadata provided does not list them explicitly.