Results for “hr_efc_process_components_uk01”

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

Overview

HR.HR_EFC_PROCESS_COMPONENTS is a transactional table in the Oracle E-Business Suite HR schema that records the individual processing scripts executed within each Enterprise Feedback and Correction (EFC) conversion processing run. The table stores one row for each processing script in each conversion processing run, forming a child of HR_EFC_ACTIONS and a parent of HR_EFC_WORKERS. Its registered FND Design Data designation is PER.HR_EFC_PROCESS_COMPONENTS, and the object carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2 environments. The name of the object, HR_EFC_PROCESS_COMPONENTS, together with its unique key HR_EFC_PROCESS_COMPONENTS_UK01, is commonly encountered during data-dictionary or dependency analysis in these releases.

Heuristically, the table leans toward a Data Vault satellite classification, since it carries descriptive attributes (table name, worker counts, step, sub-step) attached to a foreign-key relationship to HR_EFC_ACTIONS rather than functioning purely as a hub or link. This classification should be treated as a modeling suggestion, not as an authoritative schema designation.

Key Information Stored

The table's surrogate primary key is EFC_PROCESS_COMPONENT_ID, a NUMBER(15) column. The unique index HR_EFC_PROCESS_COMPONENTS_UK01 spans two business-key candidates: EFC_ACTION_ID and PROCESS_COMPONENT_NAME, which together identify a process component within a given EFC action. Notable columns include:

• EFC_PROCESS_COMPONENT_ID — surrogate primary key for the row.
• EFC_ACTION_ID — foreign key to HR_EFC_ACTIONS, identifying the parent conversion action.
• PROCESS_COMPONENT_NAME — VARCHAR2(80); the name of the SQL script that ran the component.
• TABLE_NAME — VARCHAR2(30); the table modified by the process component.
• TOTAL_WORKERS — NUMBER(15); number of worker processes executing parallel instances of the component.
• STEP — VARCHAR2(30); the main processing step during which the component ran.
• SUB_STEP — NUMBER(15); sub-step number for the component run.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• CREATION_DATE, CREATED_BY — standard WHO creation columns.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while both unique indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical usage includes tracing which SQL scripts ran during an EFC conversion run, measuring worker concurrency per component, and reconciling modified tables against HR_EFC_WORKERS processing activity. A common pattern joins the table to its parent action and its child workers:

• SELECT EFC_PROCESS_COMPONENT_ID, EFC_ACTION_ID, PROCESS_COMPONENT_NAME, TABLE_NAME, TOTAL_WORKERS, STEP, SUB_STEP FROM HR.HR_EFC_PROCESS_COMPONENTS;
• Filter by STEP or SUB_STEP to sequence processing within a run.
• Aggregate TOTAL_WORKERS by EFC_ACTION_ID to gauge parallelism.
• Join to HR_EFC_ACTIONS on EFC_ACTION_ID and to HR_EFC_WORKERS on EFC_PROCESS_COMPONENT_ID for run-level reporting.

Related Objects

• HR.HR_EFC_ACTIONS — parent; joined on EFC_ACTION_ID.
• HR.HR_EFC_WORKERS — child; references EFC_PROCESS_COMPONENT_ID.
• HR_EFC_PROCESS_COMPONENTS_PK — unique index on EFC_PROCESS_COMPONENT_ID.
• HR_EFC_PROCESS_COMPONENTS_UK01 — unique index on EFC_ACTION_ID and PROCESS_COMPONENT_NAME.
• FND Design Data PER.HR_EFC_PROCESS_COMPONENTS — registration record.