Results for “atomic_linked_calls”

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

Overview

The HR_PUMP_BATCH_HEADERS table is a core repository within the Oracle Human Resources (PER) product module that stores information on batches processed by the data pump. It functions as the master registration point for batch-based data loading operations used across Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Each record in this table represents a discrete batch — a named unit of work that groups related data transfer lines, ranges, and requests into a single loadable, traceable entity.

From a dimensional modeling perspective, the ETRM heuristic Data Vault classification for this object is hub-leaning. This reflects the fact that BATCH_ID acts as a durable, business-independent surrogate key that is referenced by multiple dependent child tables. Modelers constructing a Data Vault or similar warehouse layer should therefore treat HR_PUMP_BATCH_HEADERS as a hub candidate, with its descriptive attributes (name, status, business group) potentially distributed to a satellite structure.

Key Information Stored

The table is physically owned by the HR schema and contains eleven documented columns. The most operationally significant are:

• BATCH_ID — the surrogate primary key, defined by the constraint HR_PUMP_BATCH_HEADERS_PK. It uniquely identifies each batch and is the column through which all child tables link back to the header.
• BATCH_NAME — the human-readable batch identifier, enforced as a business key through the unique index HR_PUMP_BATCH_HEADERS_UK1. This distinguishes the surrogate key from the logical unique identifier of the batch.
• BATCH_STATUS — records the lifecycle state of the batch, indicating whether it is pending, in progress, completed, or otherwise disposed.
• BUSINESS_GROUP_NAME — identifies the business group context in which the batch was defined, supporting multi-organization data separation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns capturing who created and last modified the record, when, and through which login session.
• REFERENCE — a free-text or coded reference field associated with the batch.
• ATOMIC_LINKED_CALLS — a control column relating to atomic linked call handling during pump execution.

Together these columns allow a batch to be uniquely identified, audited, and tracked through its processing lifecycle.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting data pump activity. Administrators query this table to determine which batches exist, their current status, and which business group they affect. A typical status-check query joins the header to its lines to assess load progress:

• SELECT h.BATCH_ID, h.BATCH_NAME, h.BATCH_STATUS, h.BUSINESS_GROUP_NAME FROM hr.hr_pump_batch_headers h WHERE h.BATCH_STATUS = 'PENDING';
• SELECT h.BATCH_NAME, l.LINE_ID FROM hr.hr_pump_batch_headers h, hr.hr_pump_batch_lines l WHERE h.BATCH_ID = l.BATCH_ID;

Reporting scenarios include batch throughput analysis by creation date, audit trails of who initiated loads, and reconciliation of batch names against request logs. Because BATCH_NAME is uniquely indexed, lookups by name are efficient and suited to interactive diagnostics.

Related Objects

Three documented foreign keys reference this table, confirming its role as a parent hub:

• HR_PUMP_BATCH_LINES — links via BATCH_ID, holding the individual data lines belonging to each batch.
• HR_PUMP_RANGES — links via BATCH_ID, defining range-based selection criteria for the batch.
• HR_PUMP_REQUESTS — links via BATCH_ID, recording requests submitted against the batch.

These child objects depend directly on the header record and are the principal tables to join when tracing batch contents, scope, and execution history.