Results for “hr_pump_batch_lines_pk”

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

Overview

HR.HR_PUMP_BATCH_LINES is a core interface table within the Oracle E-Business Suite HR (Human Resources) schema, registered under FND Design Data PER.HR_PUMP_BATCH_LINES. It stores the individual API call records that make up a Data Pump batch. The Oracle HR Data Pump is the batch-processing engine used to execute Business Process APIs (such as create_employee, update_person, and create_assignment) in bulk, either synchronously or as part of a concurrent program run. Each row in HR_PUMP_BATCH_LINES corresponds to one queued API invocation, with its parameter values and processing state captured so the Data Pump can serialize, order, and execute the call.

In Data Vault modeling terms, the heuristic classification mined from the foreign-key structure is satellite-leaning. This is a modeling suggestion: the table's grain is the batch line (each API call), and it carries descriptive and processing attributes that describe the parent batch rather than acting as an independent business entity. It is best treated as a child/satellite of the batch header, not as a hub or link.

The table resides in the APPS_TS_INTERFACE tablespace with PCT Free 10, reflecting its role as a transient interface object. Records are typically inserted by the Data Pump loader, processed, and then archived or deleted. In 12.2.2 the documented physical schema contains 239 columns.

Key Information Stored

The most important columns fall into identification, control, and parameter categories:

• BATCH_LINE_ID (NUMBER 15) — System-generated surrogate primary key, uniquely identifying each API call. It is the single-column unique index HR_PUMP_BATCH_LINES_PK.
• BATCH_ID (NUMBER 15) — Foreign key to HR_PUMP_BATCH_HEADERS, identifying the parent batch. It participates in the business-key candidate HR_PUMP_BATCH_LINES_UK1 (BATCH_ID, BATCH_LINE_ID).
• API_MODULE_ID (NUMBER 15) — Foreign key to HR_API_MODULES, specifying which Business Process API is to be executed for this line.
• LINE_STATUS (VARCHAR2) — Processing status of the batch line, used by the pump to track pending, processed, or errored calls.
• LINK_VALUE (NUMBER 15) — Groups API calls that must execute within a single thread.
• USER_SEQUENCE (NUMBER 15) — Overrides the default ordering by BATCH_LINE_ID when the user needs a specific execution order.
• PROCESS_SEQUENCE (NUMBER 15) — System-maintained ordering used during a data pump run; indexed by HR_PUMP_BATCH_LINES_N1 (BATCH_LINE_ID, PROCESS_SEQUENCE).
• PVAL001 … PVAL230 (VARCHAR2 2000 each) — A wide parameter bank holding the argument values passed to the target API.
• PLONGVAL — Stores long parameter values that exceed the PVAL width.
• BUSINESS_GROUP_NAME — Multitenancy/business group discriminator, indexed by HR_PUMP_BATCH_LINES_N2 (BATCH_ID, BUSINESS_GROUP_NAME).

The primary key is the surrogate BATCH_LINE_ID; the unique index HR_PUMP_BATCH_LINES_UK1 (BATCH_ID, BATCH_LINE_ID) serves as a composite business-key candidate scoped to the parent batch.

Common Use Cases and Queries

Typical scenarios include auditing bulk API activity, diagnosing failed Data Pump lines, and measuring throughput. A simple status summary by batch:

SELECT BATCH_ID, LINE_STATUS, COUNT(*) FROM HR.HR_PUMP_BATCH_LINES GROUP BY BATCH_ID, LINE_STATUS;

To inspect failed lines and their API module:

SELECT L.BATCH_LINE_ID, L.API_MODULE_ID, M.API_MODULE_NAME, L.LINE_STATUS FROM HR.HR_PUMP_BATCH_LINES L, HR.HR_API_MODULES M WHERE L.API_MODULE_ID = M.API_MODULE_ID AND L.LINE_STATUS = 'ERROR';

To review execution ordering, query on the ordering index:

SELECT BATCH_LINE_ID, PROCESS_SEQUENCE, USER_SEQUENCE, LINK_VALUE FROM HR.HR_PUMP_BATCH_LINES WHERE BATCH_ID = :p_batch ORDER BY PROCESS_SEQUENCE;

Reporting use cases focus on batch success/failure rates, per-API volume, and multitenant filtering on BUSINESS_GROUP_NAME.

Related Objects

• HR.HR_PUMP_BATCH_HEADERS — Parent batch header; joined on BATCH_ID. Provides batch-level context such as submission and status.
• HR.HR_API_MODULES — API registry; joined on API_MODULE_ID to resolve which Business Process API each line invokes.
• HR.HR_PUMP_BATCH_LINE_USER_KEYS — Child table holding user keys per line; joined on BATCH_LINE_ID. This confirms HR_PUMP_BATCH_LINES as the referenced parent.
• HR_EMPLOYEE_API / PER_* Business Process APIs — The API and PL/SQL Data Pump routines that read these lines and execute the calls.