Search Results hr_pump_requests




Overview
Explore in AI Chat

Overview

The HR_PUMP_REQUESTS table is a core technical object within the Oracle E-Business Suite Human Resources (PER) module, specifically supporting the HRMS Data Pump (HDP) utility. Its primary role is to serve as a runtime tracking and coordination mechanism for concurrent processes initiated by the Data Pump. The table holds metadata for requests that are actively executing, enabling the system to manage batch processing, prevent conflicts, and maintain state integrity during complex data loading and migration operations. It functions as a critical junction point between the logical batch definition and the physical concurrent program execution within the Oracle Applications framework.

Key Information Stored

The table's structure is designed to link a Data Pump batch to its associated concurrent requests. The two columns forming the composite primary key are fundamental. The BATCH_ID column stores the unique identifier for a specific Data Pump batch, as defined in the HR_PUMP_BATCH_HEADERS table. The REQUEST_ID column stores the identifier of the concurrent request (from FND_CONCURRENT_REQUESTS) spawned to process that batch. While the provided metadata does not list additional columns, typical implementations of such a tracking table might include status flags or timestamps to monitor request progression. The presence of these two keys alone confirms the table's purpose: to maintain a definitive, auditable relationship between a logical data load batch and its system-generated execution threads.

Common Use Cases and Queries

This table is primarily accessed for administrative monitoring and troubleshooting of Data Pump processes. A common scenario involves identifying all concurrent requests associated with a stalled or problematic batch to diagnose performance issues or execution errors. Database administrators or functional consultants may query it to understand the execution footprint of a data load. A typical diagnostic query would join to the batch headers and concurrent requests tables:

  • Monitoring Active Data Pump Runs: SELECT r.batch_id, b.batch_name, r.request_id, cr.request_date, cr.phase_code, cr.status_code FROM hr_pump_requests r, hr_pump_batch_headers b, fnd_concurrent_requests cr WHERE r.batch_id = b.batch_id AND r.request_id = cr.request_id AND cr.phase_code = 'R';
  • Investigating a Specific Batch: SELECT request_id FROM hr_pump_requests WHERE batch_id = <batch_id>; This retrieves all concurrent request IDs for a given batch, which can then be used to review log/output files.

Related Objects

The HR_PUMP_REQUESTS table has defined dependencies on other key HDP and application foundation objects, as per the provided relationship data.

  • HR_PUMP_BATCH_HEADERS: This is the primary parent table. A foreign key constraint on HR_PUMP_REQUESTS.BATCH_ID references HR_PUMP_BATCH_HEADERS, ensuring every tracked request is linked to a valid, defined batch.
  • FND_CONCURRENT_REQUESTS (Implied): Although not explicitly listed as a foreign key in the snippet, the REQUEST_ID column is a direct reference to the REQUEST_ID in the application foundation's FND_CONCURRENT_REQUESTS table, which stores the master record for all concurrent program executions.
  • The table itself is referenced by the HRMS Data Pump engine and its associated APIs during the submission and management of batch processes.