Search Results pay_batch_lines_pk

Overview

PAY_BATCH_LINES is a Payroll (PAY) module table owned by the HR schema. It stores the individual batch lines that belong to a Batch Element Entry (BEE) batch. Where PAY_BATCH_HEADERS represents a batch as a whole, PAY_BATCH_LINES captures the granular element entries within that batch, each row corresponding to a single element entry for an assignment, ready to be processed by the Batch Element Entry process. This table is central to high-volume payroll and element entry loading scenarios, where payroll administrators or integrations supply many element entries at once rather than entering them interactively.

In Data Vault modeling terms, the mined foreign-key structure suggests a satellite-leaning classification. PAY_BATCH_LINES hangs off PAY_BATCH_HEADERS via BATCH_ID and carries descriptive, context-specific attributes (entry values, statuses, effective dates, cost allocation references) rather than acting as a standalone hub or a pure link between two hubs. Practitioners modeling this data for warehouse purposes may therefore treat it as a satellite of the batch hub, with the line-level detail attached to the batch parent.

Key Information Stored

The table is defined with 116 columns in the documented 12.2.2 schema. The most significant columns and their roles are:

• BATCH_LINE_ID — the surrogate primary key, uniquely identifying each batch line (PAY_BATCH_LINES_PK). This is the single documented unique index and the primary business-key candidate for row identification.
• BATCH_ID — foreign key to PAY_BATCH_HEADERS, associating the line with its parent batch.
• COST_ALLOCATION_KEYFLEX_ID — foreign key to PAY_COST_ALLOCATION_KEYFLEX, linking the line to its cost allocation flexfield setup.
• ELEMENT_TYPE_ID — the element type being entered on the line.
• ASSIGNMENT_ID and ASSIGNMENT_NUMBER — the assignment to which the element entry applies.
• BATCH_LINE_STATUS — the processing status of the individual line within the batch.
• EFFECTIVE_DATE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and DATE_EARNED — date context for the entry.
• ENTRY_TYPE and REASON — the entry classification and any associated reason.
• ELEMENT_NAME — a descriptive reference to the element.
• VALUE_1 through VALUE_15 — the input values supplied for the element entry.
• SEGMENT1 through SEGMENT30 and CONCATENATED_SEGMENTS — key flexfield segment values and their concatenated form for the entry.
• ATTRIBUTE1 through ATTRIBUTE20 and ENTRY_INFORMATION1 through ENTRY_INFORMATION30 — descriptive flexfield and entry information storage.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle framework.

Common Use Cases and Queries

Typical use cases include auditing batches before processing, reconciling lines against expected element entries, and reporting on batch content by assignment, element, or status. A common query pattern joins lines to their parent batch and to assignments:

• Retrieving all lines for a given batch: select from PAY_BATCH_LINES where BATCH_ID = :batch_id, ordered by BATCH_SEQUENCE.
• Filtering by processing state using BATCH_LINE_STATUS to identify unprocessed or errored lines.
• Joining to PAY_BATCH_HEADERS on BATCH_ID to obtain batch-level metadata alongside line detail.
• Joining to PAY_COST_ALLOCATION_KEYFLEX on COST_ALLOCATION_KEYFLEX_ID to resolve cost allocation segments.
• Aggregating line counts and element value sums (VALUE_1, VALUE_2, and so on) per batch for pre-process validation.

Because the table is wide, reporting queries should project only the columns required to avoid unnecessary I/O across the 116 attributes.

Related Objects

• PAY_BATCH_HEADERS — the parent table; joined via PAY_BATCH_LINES.BATCH_ID = PAY_BATCH_HEADERS.BATCH_ID.
• PAY_COST_ALLOCATION_KEYFLEX — provides cost allocation flexfield definitions; joined via PAY_BATCH_LINES.COST_ALLOCATION_KEYFLEX_ID.
• PAY_ELEMENT_TYPES_F — resolves element metadata via ELEMENT_TYPE_ID.
• PER_ALL_ASSIGNMENTS_F — resolves assignment detail via ASSIGNMENT_ID.
• PAY_ELEMENT_ENTRIES_F — the destination of successfully processed batch lines.
• PAY_BATCH_LINES_PK — the primary key constraint/unique index on BATCH_LINE_ID.

Batch Element Entry APIs and concurrent processes that consume PAY_BATCH_HEADERS and PAY_BATCH_LINES together are the principal programmatic dependencies for this object.