Results for “hr_efc_workers”

50+ results




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

Overview

HR_EFC_WORKERS is a Human Resources (PER) module table in the Oracle E-Business Suite HR schema. It holds one row for each parallel worker instance of a processing component, making it a core operational table within the Enterprise Foundation Classes (EFC) parallel processing framework. When a large HR process — such as a payroll action, an assignment mass update, or a concurrent data load — is split into parallel chunks, the EFC framework creates one row in this table for every worker thread assigned to a component. Each row therefore represents a single unit of parallel execution, tracking the worker's identity, its parent component, and the status of the work it performs.

From a Data Vault modeling perspective, the heuristic classification of HR_EFC_WORKERS is satellite-leaning. This classification reflects the table's role as a dependent detail structure attached to a parent component: it carries descriptive, execution-specific attributes and a foreign key to its driving component, rather than serving as an independent business hub or an intersection between two hubs. The EFC_WORKER_ID surrogate is generated by the framework, and the table is maintained entirely by internal processing logic rather than by user data entry.

Key Information Stored

The table contains 16 documented columns. The most important are:

  • EFC_WORKER_ID — the surrogate primary key, defined by the HR_EFC_WORKERS_PK primary key constraint. This is the value most commonly searched for as efc_worker_id and is the unique identifier for a single parallel worker instance.
  • EFC_PROCESS_COMPONENT_ID — foreign key to HR_EFC_PROCESS_COMPONENTS, identifying the parent processing component to which the worker belongs.
  • WORKER_NUMBER — the ordinal number of the worker within its component. Together with EFC_PROCESS_COMPONENT_ID, it forms the HR_EFC_WORKERS_UK01 unique index, the documented business-key candidate for this table.
  • EFC_ACTION_ID — foreign key to HR_EFC_ACTIONS, linking the worker to the action being executed.
  • WORKER_PROCESS_STATUS — the current execution status of the worker, used by the framework to track progress, success, and failure.
  • SPID — the database session identifier associated with the worker, useful for correlating the row with a specific database session.
  • PK1 through PK5 — generic parameter key columns used by the EFC framework to pass context values into the worker at runtime.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle EBS audit columns recording who created and last modified each worker row and when.

Common Use Cases and Queries

The primary practical uses of this table are monitoring parallel processing runs, troubleshooting failed workers, and reporting on throughput. A typical diagnostic query retrieves all workers for a component:

  • SELECT w.efc_worker_id, w.worker_number, w.worker_process_status, w.spid FROM hr.hr_efc_workers w WHERE w.efc_process_component_id = :component_id ORDER BY w.worker_number;
  • Joining to HR_EFC_WORKER_AUDITS on EFC_WORKER_ID to trace the message history of a specific worker or to investigate why a parallel run aborted mid-flight.
  • Joining to HR_EFC_ACTIONS on EFC_ACTION_ID to report on all workers associated with a particular action across its components.
  • Aggregating WORKER_PROCESS_STATUS to produce run summaries — counts of completed, in-progress, and failed workers — for operational dashboards and DBA monitoring.

Because the table can grow to many rows per run, queries should always filter by EFC_PROCESS_COMPONENT_ID or EFC_ACTION_ID and leverage the HR_EFC_WORKERS_UK01 unique index.

Related Objects

  • HR_EFC_PROCESS_COMPONENTS — parent table; joined via HR_EFC_WORKERS.EFC_PROCESS_COMPONENT_ID.
  • HR_EFC_ACTIONS — defines the action the workers execute; joined via HR_EFC_WORKERS.EFC_ACTION_ID.
  • HR_EFC_WORKER_AUDITS — dependent audit table holding message and error detail per worker; joined via HR_EFC_WORKER_AUDITS.EFC_WORKER_ID = HR_EFC_WORKERS.EFC_WORKER_ID.
  • EFC parallel processing framework APIs — internal PL/SQL packages that create, update, and close worker rows during submission and completion of parallel jobs.
  • HR concurrent program and request infrastructure — the EFC framework is driven from concurrent processing; worker rows can be correlated with request IDs through the parent component and action records.