Results for “hr_efc_actions”

50+ results




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

Overview

HR_EFC_ACTIONS is a PER (Human Resources) module table in the HR schema of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. The table contains one row for each execution of the EFC conversion process or the delete _EFC table data process. EFC refers to the Euro/Funding Conversion (Enhanced Financial Conversions) utilities that were introduced for migration and reconciliation of large legislative or currency-driven payroll and HR data sets. Every run of the conversion or purge program is registered here, providing the audit anchor and grouping key for the entire family of _EFC staging and converted tables.

Functionally, the table behaves as a control or run-registry object. It records what type of action was performed, its progress and completion status, the business group context, sequence information, and timing metadata. From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a hub. The surrogate primary key, EFC_ACTION_ID, is referenced by the majority of _EFC tables across HR, PER, PQH, PAY, and PQP product prefixes, which is precisely the behavior expected of a hub distributing its key to dependent satellites and links. This classification is a modeling suggestion rather than a physical constraint.

Key Information Stored

The table is documented with 14 columns. The most significant are:

Note that the surrogate key (EFC_ACTION_ID) and the business-key candidate (MATCHING_EFC_ACTION_ID) are distinct concepts: the former uniquely identifies a run, the latter relates runs to one another.

Common Use Cases and Queries

The primary use cases are conversion monitoring, purge auditing, and downstream data lineage. Typical queries include:

  • Current and recent runs: SELECT efc_action_id, efc_action_type, efc_action_status, efc_progress_status, start_date, finish_date FROM hr.hr_efc_actions WHERE business_group_id = :p_bg_id ORDER BY start_date DESC;
  • Runtime and failure analysis: SELECT efc_action_id, efc_action_type, (finish_date - start_date) * 86400 AS elapsed_seconds FROM hr.hr_efc_actions WHERE efc_action_status = 'ERROR';
  • Lineage for a specific staging row: join any _EFC table (for example, PQH_WORKSHEET_DETAILS_EFC) back to HR_EFC_ACTIONS on EFC_ACTION_ID to determine which conversion run produced the record.
  • Paired action reconciliation: self-join on MATCHING_EFC_ACTION_ID to compare conversion and delete runs.

These patterns are especially relevant when users search for PQH_WORKSHEET_DETAILS_EFC, because that table carries EFC_ACTION_ID and therefore cannot be interpreted without the controlling row in HR_EFC_ACTIONS.

Related Objects

HR_EFC_ACTIONS is referenced by a large set of dependent _EFC tables through the EFC_ACTION_ID foreign key. The most significant include:

Any query or concurrent program that consumes an _EFC table should join HR_EFC_ACTIONS on EFC_ACTION_ID to filter by run status and action type, ensuring only completed and validated conversion runs are reported.