Results for “pay_balance_batch_headers”

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

Overview

PAY_BALANCE_BATCH_HEADERS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the batch header information that defines a balance upload batch. Each row represents a single batch used to group and stage balance adjustments before they are processed into the payroll balance repository. The table acts as the controlling parent record for the lines and adjustment groups that make up the batch, providing the descriptive and status attributes that apply to the batch as a whole.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is hub-leaning. In modeling terms, it can be treated as a hub: BATCH_ID serves as a stable, unique business key that anchors the batch entity, while the descriptive attributes (name, status, source, type, and dates) resemble satellite attributes attached to that hub. This suggests the table is a natural candidate for a reference or master entity in a warehouse design, with dependent line and group tables acting as links or satellites around it.

Key Information Stored

The table exposes 11 documented columns. The most significant of these are:

• BATCH_ID — the surrogate primary key, defined by the unique index PAY_BALANCE_BATCH_HEADERS_PK. It uniquely identifies each batch and is the column through which all dependent tables join.
• BATCH_NAME — the descriptive name assigned to the batch for identification by users and reports.
• BATCH_STATUS — the current state of the batch (for example, unprocessed, processed, or errored), governing which batches are eligible for further processing.
• BATCH_TYPE — classifies the nature of the batch, distinguishing balance uploads from other batch categories.
• BATCH_SOURCE — indicates the origin of the batch, such as manual entry or an external interface.
• BATCH_REFERENCE — an external or user-supplied reference used to trace the batch back to its originating transaction or source document.
• UPLOAD_DATE — the date on which the batch was loaded into the system.
• PAYROLL_ID — the payroll to which the batch belongs; the foreign key that scopes the batch to a specific payroll definition.
• BUSINESS_GROUP_ID — the business group that owns the batch, providing the primary organizational partitioning.
• PAYROLL_NAME and BUSINESS_GROUP_NAME — denormalized descriptive values that identify the payroll and business group without a lookup join.

The surrogate primary key is BATCH_ID, which is also the sole documented unique index and therefore the primary business-key candidate. All other columns are descriptive attributes or foreign-key references to the owning payroll and business group.

Common Use Cases and Queries

Typical applications include tracking the lifecycle of balance upload batches, reconciling uploaded balances against source systems, and reporting on batch volumes by payroll, business group, or status. A common query pattern retrieves all batches with their processing state and date:

• Listing batches by status: SELECT batch_id, batch_name, batch_status, upload_date FROM pay_balance_batch_headers WHERE batch_status = :status ORDER BY upload_date DESC;
• Counting batches per payroll and business group for volume reporting: SELECT payroll_id, business_group_id, COUNT(*) FROM pay_balance_batch_headers GROUP BY payroll_id, business_group_id;
• Joining to lines to inspect batch contents: SELECT h.batch_id, h.batch_name, l.* FROM pay_balance_batch_headers h JOIN pay_balance_batch_lines l ON l.batch_id = h.batch_id WHERE h.batch_id = :batch_id;
• Auditing recent uploads using BATCH_SOURCE and BATCH_REFERENCE to trace the origin of adjustments.

These patterns support interface monitoring, balance reconciliation, and batch error analysis, particularly when filtered by BATCH_STATUS and UPLOAD_DATE.

Related Objects

Three foreign keys from dependent tables reference BATCH_ID in this table, making it the parent in each relationship:

• PAY_BALANCE_BATCH_LINES — the primary child table, joined on PAY_BALANCE_BATCH_LINES.BATCH_ID = PAY_BALANCE_BATCH_HEADERS.BATCH_ID, holding the individual balance entries in the batch.
• PAY_ADJUST_BATCH_GROUPS — joined on PAY_ADJUST_BATCH_GROUPS.BATCH_ID = PAY_BALANCE_BATCH_HEADERS.BATCH_ID, grouping adjustment records associated with the batch.
• PAY_ADJUST_BATCH_LINES — joined on PAY_ADJUST_BATCH_LINES.BATCH_ID = PAY_BALANCE_BATCH_HEADERS.BATCH_ID, containing individual adjustment lines tied to the batch.

In addition, PAYROLL_ID relates the batch to the payroll definition, and BUSINESS_GROUP_ID relates it to the business group, both of which are referenced for organizational context. Together these objects form the balance and adjustment batch framework within the Payroll module, with PAY_BALANCE_BATCH_HEADERS serving as the central header entity.