Search Results hr_pump_batch_headers




Overview
Explore in AI Chat

Overview

The HR_PUMP_BATCH_HEADERS table is a core technical object within the Oracle E-Business Suite Human Resources (PER) module, specifically designed to support the HRMS Data Pump (HDP) utility. Its primary role is to store high-level metadata and control information for a batch of data to be loaded or processed by the Data Pump. Each record in this table represents a distinct batch, serving as a parent container that groups related data lines, processing requests, and range definitions. The table is fundamental to the batch-oriented architecture of the HDP, enabling the staged, auditable, and controlled loading of HR data such as new hires, assignments, or personal information from external systems or legacy sources into the Oracle HRMS tables.

Key Information Stored

The table's structure is centered on batch identification and status management. The primary identifier is the BATCH_ID, a system-generated unique key. The BATCH_NAME provides a unique, user-defined identifier for the batch, crucial for operational reference. While the provided ETRM excerpt lists only these primary and unique key columns explicitly, typical implementations of this table in Oracle EBS 12.1.1 and 12.2.2 also include columns to track the batch's lifecycle. These commonly include STATUS (e.g., 'CREATED', 'RUNNING', 'COMPLETED', 'ERROR'), CREATION_DATE, LAST_UPDATE_DATE, and possibly a USER_PROCESS_NAME or PROGRAM_NAME to associate the batch with a specific Data Pump process or submission.

Common Use Cases and Queries

The primary use case is monitoring and managing Data Pump batch executions. System administrators and HRIS analysts query this table to assess the volume and success of data loads. Common SQL patterns include checking for batches in an error state to initiate corrective actions, identifying long-running processes, or generating audit reports. For example, a query to list recent batches with their status would be: SELECT batch_id, batch_name, status, creation_date FROM hr_pump_batch_headers WHERE creation_date > SYSDATE - 1 ORDER BY creation_date DESC;. Another critical use is troubleshooting; when a Data Pump process fails, the BATCH_ID from this table is used as a key to join and examine detailed errors in child tables like HR_PUMP_BATCH_LINES to pinpoint invalid data records.

Related Objects

HR_PUMP_BATCH_HEADERS maintains strict parent-child relationships with several other key Data Pump tables, as documented in the foreign key constraints. The BATCH_ID column is the central join point.

  • HR_PUMP_BATCH_LINES: This is the primary child table, containing the individual data rows (e.g., for each employee or assignment) submitted within a batch. The join is on HR_PUMP_BATCH_LINES.BATCH_ID = HR_PUMP_BATCH_HEADERS.BATCH_ID.
  • HR_PUMP_REQUESTS: Stores submission requests for processing a batch, linking the batch to a concurrent request. The join is on HR_PUMP_REQUESTS.BATCH_ID = HR_PUMP_BATCH_HEADERS.BATCH_ID.
  • HR_PUMP_RANGES: Used to define and manage ranges of data within a batch for parallel processing. The join is on HR_PUMP_RANGES.BATCH_ID = HR_PUMP_BATCH_HEADERS.BATCH_ID.

These relationships form the structural backbone of the HRMS Data Pump, ensuring data integrity and traceability from the header batch definition down to the individual data elements.