Results for “hr_pump_ranges”

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

Overview

HR_PUMP_RANGES is an Oracle E-Business Suite table owned by the HR schema and classified under the PER (Human Resources) product family. Its documented purpose is to control the parallelisation of work when the HR data pump is executing on multiprocessor platforms. In practice, the table partitions a single data pump batch into discrete, independently processable work ranges, allowing multiple concurrent worker processes to operate against separate slices of the same batch without contention.

The object is a transactional control structure rather than a master or reference entity. Under the heuristic Data Vault classification derived from its foreign key topology, HR_PUMP_RANGES is satellite-leaning: its primary key includes a foreign reference to a parent batch, and its non-key columns describe the state and boundaries of that batch's constituent ranges rather than identifying independent business entities. Modelers should treat it as a dependent satellite attached to the batch header, not as a hub or link.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains five columns. The composite primary key, HR_PUMP_RANGES_PK, is defined on (BATCH_ID, RANGE_NUMBER), which serves as the unique business-key candidate and the table's sole documented unique index.

• BATCH_ID — Identifies the parent data pump batch. This column is both part of the composite primary key and a foreign key to HR_PUMP_BATCH_HEADERS.BATCH_ID, anchoring each range to its owning batch.
• RANGE_NUMBER — The remaining component of the composite primary key; distinguishes individual ranges within a batch and defines the assignment of work to a parallel worker.
• STARTING_PROCESS_SEQUENCE — The lower boundary of the process sequence covered by the range, delimiting where a worker's assigned slice begins.
• ENDING_PROCESS_SEQUENCE — The upper boundary of the process sequence covered by the range, delimiting where the worker's assigned slice ends.
• RANGE_STATUS — Tracks the processing state of the individual range, supporting coordination between the pump controller and its parallel workers.

Together, the sequence columns define the interval of work each range represents, while RANGE_STATUS records progress. The surrogate identity of a row is the combination of BATCH_ID and RANGE_NUMBER; no single-column surrogate key is documented.

Common Use Cases and Queries

Primary usage centers on diagnosing and monitoring data pump parallelisation. Administrators and support engineers query this table to determine how a batch was split, whether all ranges completed, and whether any range stalled.

• Enumerating ranges for a specific batch: 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;
• Detecting incomplete ranges across all batches: SELECT batch_id, range_number, range_status FROM hr.hr_pump_ranges WHERE range_status <> 'COMPLETE';
• Measuring parallel fan-out per batch: SELECT batch_id, COUNT(*) range_count FROM hr.hr_pump_ranges GROUP BY batch_id;
• Join-based batch reporting: SELECT h.batch_id, r.range_number, r.range_status FROM hr.hr_pump_batch_headers h JOIN hr.hr_pump_ranges r ON r.batch_id = h.batch_id WHERE h.batch_id = :batch_id;

These patterns support troubleshooting hung or unevenly distributed pump runs, validating range coverage against expected sequence boundaries, and reporting throughput of parallel HR processes.

Related Objects

The dominant relationship is to the batch header, which supplies the parent context for every range row.

• HR_PUMP_BATCH_HEADERS — Referenced via HR_PUMP_RANGES.BATCH_ID → HR_PUMP_BATCH_HEADERS.BATCH_ID. This is the definitive parent table and the primary join path for all reporting.
• HR_PUMP_BATCH_HEADERS primary key — The driving key that enforces referential integrity for the BATCH_ID foreign key.
• HR_PUMP_BATCH_LINES — A closely associated child of the batch headers, representing the individual work items whose process sequences the ranges bound.
• HR_PUMP_BATCH_HEADERS indexes — Supporting indexes on the header table used when joining ranges back to their batch.
• FND tables and the concurrent manager — External consumers that launch the pump as a concurrent program and rely on range-level status to coordinate multiprocessor execution.

Where a full batch is deleted or purged, HR_PUMP_RANGES rows are removed first to satisfy the foreign key constraint to the header.