Search Results pay_batch_headers_v1




Overview
Explore in AI Chat

Overview

The PAY_BATCH_HEADERS_V1 view is a public, APPS-owned database object within the Oracle E-Business Suite Payroll (PAY) product family. Its stated purpose is to provide a consolidated, fully denormalized summary of payroll batch headers for consumption by the Oracle Forms screen PAYWSSBS (Batch Summary). In the Oracle EBS 12.1.1 and 12.2.2 releases this view holds a status of VALID and is exposed from the APPS schema, making it available to any reporting, integration, or extension component that connects with the standard APPS credentials or an equivalent synonym-owning schema.

Because the view resolves the opaque numeric batch identifier into a human-readable batch name, batch reference, and lookup-driven status label, it serves as the canonical read-only interface for batch-level payroll processing data. It is frequently used by Fast Formulas, concurrent extracts, BI Publisher reports, and third-party integration layers that need to enumerate or filter payroll batches without joining the underlying base tables manually.

Underlying Base Objects

The view definition joins the PAY_BATCH_HEADERS synonym against the HR_LOOKUPS view, and additionally invokes the PAY_PAYWSQEE_PKG package through a PL/SQL function call embedded in the WHERE clause. The documented referenced base objects are:

  • PAY_BATCH_HEADERS (SYNONYM) — supplies the core batch attributes.
  • HR_LOOKUPS (VIEW) — supplies the translated meaning of the batch status code where LOOKUP_TYPE = 'BATCH_STATUS' and APPLICATION_ID = 800.
  • PAY_PAYWSQEE_PKG (PACKAGE) — its BATCH_OVERALL_STATUS function computes the current overall status for each batch identifier.
  • HR_API (PACKAGE) — an indirect dependency referenced by the PAY product stack.

The join is an inner join, so a batch row is returned only when the computed status maps to a valid BATCH_STATUS lookup code, and only when the batch belongs to the applicable business group.

Key Columns

  • BATCH_ID — Surrogate primary key of the payroll batch; used as the bind variable to the status function and as the foreign key to downstream batch detail tables.
  • BATCH_NAME — User-assigned descriptive name for the batch, typically the label employees recognize in the Batch Summary form.
  • BATCH_REFERENCE — Free-text reference identifier attached to the batch. This is the column most relevant to the search term “batch_reference” and is the primary candidate for filtering, cross-referencing with external systems, or reconciliation of payroll transmissions.
  • BATCH_STATUS — The decoded meaning of the batch’s current state (for example, unprocessed, processed, or transferred), resolved through the BATCH_STATUS lookup.
  • BUSINESS_GROUP_ID — The HR business group that owns the batch, enabling multi-organization and legislative data segregation in global deployments.

Common Use Cases and Queries

The principal use case is the Batch Summary form query, which relies on this view to present one row per batch together with its friendly name and status. Reporting extensions and integrations typically reuse the same projection. A typical query filtering on the searched attribute is:

SELECT batch_id,
       batch_name,
       batch_reference,
       batch_status,
       business_group_id
FROM   apps.pay_batch_headers_v1
WHERE  batch_reference = :p_batch_reference
  AND  business_group_id = :p_business_group_id;

Because BATCH_STATUS is computed row-by-row via PAY_PAYWSQEE_PKG.BATCH_OVERALL_STATUS, queries against large batch populations can be expensive; predicates on BATCH_ID or BATCH_REFERENCE should be supplied wherever possible to reduce the number of function invocations. A common variant lists all active batches for a business group:

SELECT batch_name, batch_reference, batch_status
FROM   apps.pay_batch_headers_v1
WHERE  business_group_id = :p_business_group_id
ORDER  BY batch_name;

In integration scenarios the view is often wrapped in a database view or synonym for downstream systems that must reconcile batch references against payroll results. Note that BATCH_REFERENCE is not guaranteed unique; consumers should confirm uniqueness within a business group before treating it as an external key.