Results for “hr_efc_process_components”

50+ results




Overview
Explore in AI Chat

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

Overview

The HR_EFC_PROCESS_COMPONENTS table, owned by the HR schema and part of the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2, holds one row for each processing script executed within a conversion processing run. It is a core infrastructure object for the Employee Fast Formula Conversion (EFC) framework, which automates migration of legacy HR data and formulas into Oracle HRMS. Every distinct script that participates in a given conversion action is tracked individually in this table, making it the operational ledger of the conversion pipeline.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. It carries descriptive attributes about each process component (script name, target table, worker counts, and step sequencing) attached to the natural business key of the conversion action. Modelers should consider treating HR_EFC_PROCESS_COMPONENTS as a satellite hanging off a hub or link anchored by EFC_ACTION_ID, with EFC_PROCESS_COMPONENT_ID acting as a surrogate identifier.

Key Information Stored

The table is documented with 12 physical columns. The most significant are:

  • EFC_PROCESS_COMPONENT_ID — the surrogate primary key, uniquely identifying each processing script row (enforced by HR_EFC_PROCESS_COMPONENTS_PK).
  • EFC_ACTION_ID — foreign key to HR_EFC_ACTIONS, tying each component to its parent conversion run. Together with PROCESS_COMPONENT_NAME, this forms the unique business key (HR_EFC_PROCESS_COMPONENTS_UK01).
  • PROCESS_COMPONENT_NAME — the name of the processing script executed in the run; the column users most frequently search on.
  • TABLE_NAME — the database table the component targets or processes during the conversion.
  • TOTAL_WORKERS — the count of worker records spawned by the component, useful for load and throughput analysis.
  • STEP and SUB_STEP — the ordinal position of the component within the conversion sequence, enabling ordered replay and dependency tracking.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns capturing creation and last-modification metadata.

Common Use Cases and Queries

DBAs and HR conversion consultants query this table to monitor conversion progress, detect stuck or failed scripts, and reconcile worker counts. A typical monitoring query lists all components for a given action with step ordering:

SELECT process_component_name, table_name, step, sub_step, total_workers
FROM hr.hr_efc_process_components
WHERE efc_action_id = :action_id
ORDER BY step, sub_step;

A second pattern aggregates worker volume per conversion run to size batch windows:

SELECT efc_action_id, SUM(total_workers) total_workers
FROM hr.hr_efc_process_components
GROUP BY efc_action_id;

Reporting use cases include tracking which target tables were touched during a migration, auditing historical conversion runs by date range, and joining to HR_EFC_WORKERS to drill into individual worker-level outcomes.

Related Objects

  • HR_EFC_ACTIONS — referenced via EFC_ACTION_ID; parent action that defines the conversion processing run.
  • HR_EFC_WORKERS — child table referencing EFC_PROCESS_COMPONENT_ID; stores the individual worker records generated per component.
  • HR_EFC_PROCESS_COMPONENTS_PK — primary key index on EFC_PROCESS_COMPONENT_ID.
  • HR_EFC_PROCESS_COMPONENTS_UK01 — unique business-key index on (EFC_ACTION_ID, PROCESS_COMPONENT_NAME).

These relationships position the table as the connective layer between the conversion action header and the granular worker-level detail, making it indispensable for troubleshooting and performance tuning of HR fast-formula and data conversions in EBS.