Results for “hr_pump_ranges_pk”

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

Overview

HR.HR_PUMP_RANGES is an interface-layer table in the Oracle E-Business Suite HR schema that stores the range partitioning definition used when a data pump batch is split into parallel units of work. Each row describes a single processing range within a batch, bounded by a start and end process sequence value, so that concurrent workers can consume discrete, non-overlapping segments of the parent batch rather than contending for the same records. The table is registered in FND Design Data as PER.HR_PUMP_RANGES and resides in the APPS_TS_INTERFACE tablespace, which signals its role as transient, high-volume working storage rather than a permanent transactional store.

In Oracle EBS 12.1.1 and 12.2.2 the HR data pump is used to move large volumes of person, assignment, and related records between business groups or during migration and upgrade activities. HR_PUMP_RANGES is the mechanism that makes that movement parallelisable. Under a heuristic Data Vault classification, this table is satellite-leaning: its primary key is a composite of the batch identifier and a range sequence number, and it carries descriptive, mutable attributes such as status and sequence boundaries that describe the state of the parent batch rather than serving as an independent hub or a pure associative link.

Key Information Stored

The table contains five documented columns, of which the most significant are:

• BATCH_ID — NUMBER(15), mandatory. Identifies the parent data pump batch and is the foreign key to HR_PUMP_BATCH_HEADERS. It is the primary correlation key for all range activity.
• RANGE_NUMBER — NUMBER(15), mandatory. Distinguishes one range from another within the same batch and forms the second component of the composite key.
• STARTING_PROCESS_SEQUENCE — NUMBER(15). The inclusive lower bound of the process sequence interval assigned to this range.
• ENDING_PROCESS_SEQUENCE — NUMBER(15). The inclusive upper bound of the process sequence interval assigned to this range. Together with the starting value it defines the slice of work a worker is authorised to process.
• RANGE_STATUS — VARCHAR2. Tracks the processing state of the individual range, allowing the pump controller to determine which slices are pending, in progress, or complete.

The surrogate primary key is documented as HR_PUMP_RANGES_PK, implemented as a unique normal index on (BATCH_ID, RANGE_NUMBER). Because the primary key is also the only unique index, (BATCH_ID, RANGE_NUMBER) is simultaneously the business-key candidate — there is no separate artificial identifier column. The range boundaries themselves are not unique; multiple batches may legitimately define identical numeric intervals.

Common Use Cases and Queries

The principal use case is operational monitoring of a running or failed data pump. Administrators query the table to determine how a batch was divided and which ranges remain outstanding.

• Listing all ranges for a batch and their status: SELECT RANGE_NUMBER, STARTING_PROCESS_SEQUENCE, ENDING_PROCESS_SEQUENCE, RANGE_STATUS FROM HR.HR_PUMP_RANGES WHERE BATCH_ID = :batch_id ORDER BY RANGE_NUMBER;
• Counting incomplete ranges to assess remaining work: SELECT RANGE_STATUS, COUNT(*) FROM HR.HR_PUMP_RANGES WHERE BATCH_ID = :batch_id GROUP BY RANGE_STATUS;
• Detecting overlap or gap defects in the range definition by ordering on STARTING_PROCESS_SEQUENCE and comparing each ending value with the next starting value.
• Joining to HR_PUMP_BATCH_HEADERS on BATCH_ID to report batch-level attributes alongside per-range progress.

Because the data is transient, historical trend reporting against this table is of limited value; it is primarily a diagnostic and control object.

Related Objects

• HR_PUMP_BATCH_HEADERS — the parent table, joined on BATCH_ID, holding the batch-level definition and overall status.
• HR_PUMP_BATCH_LINES — referenced in the column comments as the ultimate source of the batch being executed, providing the process sequence values that the ranges bound.
• HR_PUMP_RANGES# — the underlying object listed among the dependencies that reference HR_PUMP_RANGES, typically the base table behind any editioning or synonym construct in 12.2.2.
• PER.HR_PUMP_RANGES — the FND Design Data registration that governs the object's definition during patching and upgrades.

No other database objects are documented as being referenced by this table, and it does not itself reference any object other than through its single foreign key to HR_PUMP_BATCH_HEADERS. Any application logic that drives the HR data pump reads and updates RANGE_STATUS directly rather than through a documented public API.