Results for “hr_pump_requests”

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

Overview

HR.HR_PUMP_REQUESTS is a core Human Resources (PER) table within Oracle E-Business Suite 12.1.1 and 12.2.2 that holds information on data pump concurrent requests currently running. It functions as a tracking ledger that links a logical data pump batch, defined in HR_PUMP_BATCH_HEADERS, to the individual Oracle Concurrent Manager request executing that batch. As such, it is central to the administration, monitoring, and troubleshooting of HR data pump operations — the mechanism by which Oracle HRMS moves large volumes of person, assignment, and related records between business groups, or performs bulk data migrations.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning. It is best modeled conceptually as a satellite surrounding the batch header entity, capturing the current execution context (the request that is actively running a given batch). Because it also carries a foreign key to an external entity (the concurrent request), it exhibits a mild link characteristic, but its predominant role is descriptive context for the parent batch header.

Key Information Stored

The documented physical schema contains three columns, and the primary key is the composite HR_PUMP_REQUESTS_PK. The most important attributes are:

• BATCH_ID — Part of the composite primary key. This is the foreign key to HR_PUMP_BATCH_HEADERS.BATCH_ID, identifying the logical data pump batch to which the request belongs. It is a business-key candidate because it participates in the unique index HR_PUMP_REQUESTS_PK.
• REQUEST_ID — Part of the composite primary key. This identifies the Oracle Concurrent Manager request that is executing (or has executed) the parent batch. Because there is no separate single-column surrogate key, the combination of BATCH_ID and REQUEST_ID uniquely identifies each record.
• PROCESS_TYPE — A descriptive indicator of the type of data pump processing performed by the request, used to distinguish among the various phases or categories of the pump operation. It is a non-key attribute and is not part of the unique index.

The composite unique index HR_PUMP_REQUESTS_PK (BATCH_ID, REQUEST_ID) is the only documented business-key candidate, and no independent surrogate primary key column is present in the underlying table.

Common Use Cases and Queries

Typical usage revolves around operational monitoring and reconciliation of HR data pump activity. Administrators join HR_PUMP_REQUESTS to HR_PUMP_BATCH_HEADERS and to the Concurrent Manager tables to determine which requests belong to which batch and whether they are still running.

• Identifying currently running requests for a given batch, checking for duplicate or orphaned request rows.
• Reconciliation of batch headers against their execution requests to confirm every batch has a corresponding concurrent request record.
• Reporting on the distribution of PROCESS_TYPE values across batches to understand workload composition.

A representative query pattern:

• SELECT r.BATCH_ID, r.REQUEST_ID, r.PROCESS_TYPE FROM HR.HR_PUMP_REQUESTS r WHERE r.BATCH_ID = :batch_id;
• SELECT r.BATCH_ID, r.REQUEST_ID, r.PROCESS_TYPE FROM HR.HR_PUMP_REQUESTS r JOIN FND_CONCURRENT_REQUESTS c ON c.REQUEST_ID = r.REQUEST_ID WHERE c.PHASE_CODE = 'R';

Related Objects

The most significant relationships are the parent batch header and the concurrent request infrastructure that consumes the request identifier:

• HR_PUMP_BATCH_HEADERS — The immediate parent. Joined on HR_PUMP_REQUESTS.BATCH_ID = HR_PUMP_BATCH_HEADERS.BATCH_ID (documented foreign key).
• FND_CONCURRENT_REQUESTS — Referenced through REQUEST_ID; supplies request phase, status, and completion details.
• FND_CONCURRENT_PROGRAMS — Identifies the executable program associated with each concurrent request.
• HR_PUMP_BATCH_LINES and related HR_PUMP_* detail tables — Provide the transaction-level records processed by the batch tracked here.

Together these objects support end-to-end tracing from a logical HR data pump batch down to the actual concurrent request execution and its processed detail lines.