Search Results hr_pump_batch_line_user_ke_fk1




Overview
Explore in AI Chat

Overview

HR.HR_PUMP_BATCH_LINE_USER_KEYS is a persistent interface table in the Oracle E-Business Suite 12.1.1 and 12.2.2 HR schema, registered under FND Design Data as PER.HR_PUMP_BATCH_LINE_USER_KEYS and stored in the APPS_TS_INTERFACE tablespace. The table holds data pump user key information — the mapping between business-facing user key values and the surrogate identifiers used by the HR data pump when processing bulk API calls. Each row associates one user key value with the batch line that consumed it, allowing the pump to correlate an externally supplied or surrogate identifier with the API call that created it.

From a Data Vault modeling perspective, the mined dependency structure suggests a satellite-leaning classification. The table carries descriptive and mapping attributes attached to a parent batch line entity, with a single foreign key reference outward rather than multiple hub references, which is characteristic of satellite rather than hub or link behavior. This classification is a heuristic suggestion derived from the foreign key topology, not a physical implementation constraint in the EBS schema.

Key Information Stored

The surrogate primary key of the table is UNIQUE_KEY_ID, while USER_KEY_VALUE serves as the documented business-key candidate through the unique index. USER_KEY_ID differs from UNIQUE_KEY_ID: the former is a reference to the surrogate key of the business entity being pumped, whereas the latter is the table's own generated identifier.

Common Use Cases and Queries

Typical usage centers on diagnosing and reconciling HR data pump runs. Administrators resolve a reported user key back to its originating batch line, confirm whether a key value was already consumed by a prior API call, or audit volumes per batch line. The FK index HR_PUMP_BATCH_LINE_USER_KE_FK1 supports efficient lookups from the parent batch line downward; the unique index supports point lookups by key value.

  • Retrieve all user keys for a batch line: SELECT UNIQUE_KEY_ID, USER_KEY_ID, USER_KEY_VALUE FROM HR.HR_PUMP_BATCH_LINE_USER_KEYS WHERE BATCH_LINE_ID = :batch_line_id;
  • Resolve a user key value to its batch context: SELECT BATCH_LINE_ID, USER_KEY_ID FROM HR.HR_PUMP_BATCH_LINE_USER_KEYS WHERE USER_KEY_VALUE = :value;
  • Count keys per batch line for reconciliation against HR_PUMP_BATCH_LINES processing results.
  • Audit creation activity using CREATION_DATE and CREATED_BY over a date range.

Related Objects

  • HR.HR_PUMP_BATCH_LINES — Parent table joined on HR_PUMP_BATCH_LINE_USER_KEYS.BATCH_LINE_ID = HR_PUMP_BATCH_LINES.BATCH_LINE_ID. The only documented foreign key relationship.
  • HR.HR_PUMP_BATCH_LINE_USER_KEYS# — The editioning or shadow object listed as referencing this table in the dependency listing.
  • HR_PUMP_BATCH_LINE_USER_KE_UK1, HR_PUMP_BATCH_LINE_USER_KEY_N1, HR_PUMP_BATCH_LINE_USER_KE_FK1 — The unique, non-unique, and foreign key indexes that support access paths into this table.
  • HR_PUMP_BATCH_LINE_USER_KEYS (synonym in APPS) — Application-level access typically occurs through the APPS synonym and the PER product's data pump PL/SQL APIs, which populate USER_KEY_VALUE during bulk loader execution.

No additional outbound references are documented; the table is a leaf on the dependency tree aside from the BATCH_LINE_ID pointer into HR_PUMP_BATCH_LINES.