Results for “hr_pump_batch_line_user_keys”

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

Overview

The HR.HR_PUMP_BATCH_LINE_USER_KEYS table is a child table within the Oracle E-Business Suite Human Resources (PER) product family. It stores user keys and their associated information that are generated when entities requiring user keys are created through the HR Pump processing framework. The HR Pump architecture is a high-volume data loading mechanism used during worker, assignment, and related HR entity imports, where each logical record is tracked as a batch line and enriched with user-defined key attributes. This table records those key attributes at the batch-line granularity.

The object resides in the HR schema and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2. Under the heuristic Data Vault classification supplied in the ETRM metadata, this table is assessed as satellite-leaning. Its structure — a foreign key to a parent batch-line hub plus descriptive user-key attributes and standard audit columns — is consistent with a satellite that hangs off the HR_PUMP_BATCH_LINES link/hub. This classification should be treated as a modeling suggestion rather than a functional constraint.

Key Information Stored

The table contains nine documented columns. The most significant are:

• BATCH_LINE_ID — Foreign key to HR_PUMP_BATCH_LINES. Ties each user-key record to the originating batch line and establishes the parent-child relationship that drives the satellite-leaning classification.
• USER_KEY_ID — Identifier for the individual user key definition associated with the batch line.
• USER_KEY_VALUE — The actual value assigned to the user key. This column is the documented unique index candidate (business key) via HR_PUMP_BATCH_LINE_USER_KE_UK1.
• UNIQUE_KEY_ID — A further identifier used to disambiguate or group unique key combinations during entity creation.
• CREATED_BY, CREATION_DATE — Standard WHO columns capturing the originating user and timestamp of the row insert.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and its session context.

Note the distinction between the surrogate identifier columns (USER_KEY_ID, UNIQUE_KEY_ID, BATCH_LINE_ID) and the business-key candidate USER_KEY_VALUE, which carries the documented unique constraint HR_PUMP_BATCH_LINE_USER_KE_UK1.

Common Use Cases and Queries

Typical usage centers on diagnosing HR Pump loads and validating user-key generation. Common patterns include:

• Reviewing all user keys captured for a specific batch line:
  SELECT user_key_id, unique_key_id, user_key_value
FROM hr.hr_pump_batch_line_user_keys
WHERE batch_line_id = :p_batch_line_id;
• Joining to the parent batch line to reconcile user keys with their source records:
  SELECT l.batch_line_id, u.user_key_value
FROM hr.hr_pump_batch_lines l, hr.hr_pump_batch_line_user_keys u
WHERE l.batch_line_id = u.batch_line_id;
• Locating duplicates or conflicts on the business key for troubleshooting failed imports:
  SELECT user_key_value, COUNT(*)
FROM hr.hr_pump_batch_line_user_keys
GROUP BY user_key_value HAVING COUNT(*) > 1;
• Auditing who created or last modified key records within a load window using the WHO columns.

Related Objects

• HR_PUMP_BATCH_LINES — Parent table; joined on BATCH_LINE_ID. The primary dependent relationship for this object.
• HR_PUMP_BATCH_HEADERS — Provides batch-level context via the batch line parent.
• PER_ALL_PEOPLE_F — Downstream recipient of user keys created for worker entities during the pump process.
• PER_ALL_ASSIGNMENTS_F — Assignments whose user keys may be generated by the same load pipeline.
• FND_USER — Resolves the CREATED_BY and LAST_UPDATED_BY values to named users.
• HR Pump concurrent programs and PL/SQL batch loaders that populate batch lines and their user keys.