Search Results pay_adjust_batch_groups




Overview

The PAY_ADJUST_BATCH_GROUPS table, owned by the HR schema and part of the Oracle Payroll (PAY) module, stores batch group information used during balance upload processing. It acts as an intermediate grouping structure that organizes adjustment lines into logical batches before they are consolidated and processed against employee balances. In Oracle EBS 12.1.1 and 12.2.2, this table supports the balance adjustment workflow, allowing payroll administrators to upload, stage, and validate balance corrections in controlled groupings rather than processing each line individually.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This suggests it is best treated as a descriptive satellite attached to a parent hub, since it holds descriptive attributes (status, consolidation, prepay indicators) and carries a foreign key to PAY_BALANCE_BATCH_HEADERS rather than being a pure relationship/link table. The heuristic classification should be regarded as a modeling suggestion, not a definitive architectural mandate.

Key Information Stored

The table contains seven documented columns. The most significant are:

  • BATCH_GROUP_ID — The surrogate primary key (PAY_ADJUST_BATCH_GROUPS_PK) that uniquely identifies each batch group record. This is the only documented unique index and therefore the business-key candidate.
  • BATCH_ID — Foreign key to PAY_BALANCE_BATCH_HEADERS, linking each group to its parent balance upload batch.
  • BATCH_GROUP_STATUS — Tracks the processing state of the group (for example, unprocessed, validated, or completed), governing eligibility for downstream processing.
  • CONSOLIDATION_SET_ID — Identifies the consolidation set governing how the group's balance entries are aggregated for payroll processing.
  • PAYROLL_ID — Associates the batch group with a specific payroll, ensuring adjustments are applied within the correct payroll run context.
  • EFFECTIVE_DATE — The date on which the batch group becomes effective, used for date-effective processing and balance period assignment.
  • PREPAY_FLAG — Indicates whether the group relates to prepayment processing, distinguishing prepay adjustments from standard balance uploads.

The distinction between the surrogate key (BATCH_GROUP_ID) and the true business identifiers is important: the batch group is a technical grouping artifact, while the meaningful business context is derived from BATCH_ID, PAYROLL_ID, and the consolidation set.

Common Use Cases and Queries

Typical scenarios include monitoring the status of balance upload groups, auditing adjustments by payroll, and tracing which batch a group belongs to. A representative query joining to the parent batch header is:

SELECT g.batch_group_id,
       g.batch_id,
       g.batch_group_status,
       g.payroll_id,
       g.effective_date,
       g.prepay_flag
FROM   hr.pay_adjust_batch_groups g
WHERE  g.batch_id = :batch_id
ORDER  BY g.effective_date;

To count outstanding (unprocessed) groups per payroll:

SELECT payroll_id, batch_group_status, COUNT(*)
FROM   hr.pay_adjust_batch_groups
GROUP  BY payroll_id, batch_group_status;

Reporting use cases include reconciliation of uploaded adjustment volumes against expected totals, status dashboards for payroll administrators, and troubleshooting consolidation or prepay flag mismatches that affect balance application.

Related Objects

  • PAY_BALANCE_BATCH_HEADERS — Parent table; joined via PAY_ADJUST_BATCH_GROUPS.BATCH_ID = PAY_BALANCE_BATCH_HEADERS.BATCH_ID.
  • PAY_ADJUST_BATCH_LINES — Child table holding individual adjustment lines; joined via PAY_ADJUST_BATCH_LINES.BATCH_GROUP_ID = PAY_ADJUST_BATCH_GROUPS.BATCH_GROUP_ID.
  • PAY_BALANCE_BATCH_LINES — Related balance-level detail supporting the batch hierarchy.
  • PAY_PAYROLLS — Referenced through PAYROLL_ID for payroll context.
  • PAY_CONSOLIDATION_SETS — Referenced through CONSOLIDATION_SET_ID for consolidation grouping.

Together these objects form the batch upload hierarchy used throughout Oracle Payroll balance adjustment processing.