Search Results hr_summary_efc_pk




Overview
Explore in AI Chat

Overview

The HR.HR_SUMMARY_EFC table is a specialized data object within Oracle E-Business Suite (EBS) Human Resources (HR) modules, specifically supporting the Euro Functional Currency (EFC) conversion process. Its primary role is to serve as an audit and reference repository for critical financial data prior to currency conversion. The table is not a transactional base table but a derivative snapshot table, maintained exclusively by automated EFC processes. It exists to preserve a historical copy of National Currency Unit (NCU) values and their corresponding currency codes, ensuring data integrity and providing a point-in-time reference for values that were converted during the transition to the Euro or other functional currency revaluations mandated by the EFC process.

Key Information Stored

The table's structure is intentionally narrow, focusing on the linkage to source data and the preserved numerical values. The key columns are:

  • ID_VALUE (NUMBER): A foreign key that links directly to the HR_SUMMARY base table. This column identifies the specific summary record for which NCU values are being preserved.
  • EFC_ACTION_ID (NUMBER): A foreign key that links to the HR_EFC_ACTIONS table. This column identifies the specific EFC conversion process run that created this snapshot record.
  • NUM_VALUE1 (NUMBER) and NUM_VALUE2 (NUMBER): These columns hold the actual NCU numerical values copied from the base table prior to conversion. Their specific semantic meaning (e.g., salary, cost, etc.) is defined by the corresponding columns in the base HR_SUMMARY table, to which documentation should be referred.
The primary key constraint HR_SUMMARY_EFC_PK, defined on the combination of ID_VALUE and EFC_ACTION_ID, enforces data integrity by ensuring a unique snapshot per summary record per EFC action.

Common Use Cases and Queries

The primary use case for this table is audit and reconciliation reporting related to the EFC process. It allows users to compare pre-conversion NCU values against post-conversion Euro values stored in the main HR_SUMMARY table. A typical query would join these tables to facilitate this analysis. For example, to retrieve the preserved NCU values for a specific EFC conversion run, one might execute: SELECT hse.ID_VALUE, hse.EFC_ACTION_ID, hse.NUM_VALUE1, hse.NUM_VALUE2
FROM hr.hr_summary_efc hse
WHERE hse.EFC_ACTION_ID = &action_id;
 Another common pattern involves a three-way join to bring together the snapshot data, the current summary data, and the descriptive action details: SELECT hea.ACTION_NAME, hs.*, hse.NUM_VALUE1 AS ORIGINAL_NCU_VALUE1
FROM hr.hr_summary hs,
hr.hr_summary_efc hse,
hr.hr_efc_actions hea
WHERE hs.ID_VALUE = hse.ID_VALUE
AND hse.EFC_ACTION_ID = hea.EFC_ACTION_ID
AND hs.ID_VALUE = &summary_id;
 Direct data manipulation (INSERT, UPDATE, DELETE) by users or custom code is strongly discouraged, as the table is designed to be maintained solely by the official EFC process.

Related Objects

The HR.HR_SUMMARY_EFC table has defined relationships with two other core EBS HR objects, forming a critical part of the EFC data model.

  • Primary Key: The table's structure is governed by the HR_SUMMARY_EFC_PK primary key constraint on the columns (ID_VALUE, EFC_ACTION_ID).
  • Foreign Key Reference (Parent): The table references HR.HR_EFC_ACTIONS via the column EFC_ACTION_ID. This relationship provides the context of which specific conversion process created the snapshot record.
  • Logical Foreign Key Reference: While not explicitly listed as a formal database foreign key in the provided metadata, the ID_VALUE column is documented as a "Foreign Key to HR_SUMMARY." This is the fundamental link to the main summary data table (HR.HR_SUMMARY) from which the NCU values (NUM_VALUE1, NUM_VALUE2) were copied.
These relationships are essential for constructing accurate audit reports and understanding the complete lifecycle of a converted summary record.