Results for “last_processed_date”

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

Overview

The PAY_PDT_BATCH_HEADERS view is a payroll module (PAY) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a simplified, report-oriented projection of payroll batch header data, presenting a consolidated record of each payroll batch processed through the Payroll Batch Loader (PBL) and related batch-processing frameworks. Rather than querying the underlying transactional table PAY_BATCH_HEADERS directly, the view normalizes certain values, supplies null placeholders for non-applicable columns, and resolves lookup-driven batch type codes into their descriptive lookup codes.

The view plays a supporting role in payroll reporting and integration. It provides a stable column interface for concurrent programs, extracts, and third-party integrations that need batch-level information without depending on the raw base table layout. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying batch records at query time.

The user search term batch_type maps directly to the BATCH_TYPE column, which is a central attribute of this view and the primary means by which consumers classify batch records.

Underlying Base Objects

The view is defined over the following documented base objects:

• PAY_BATCH_HEADERS (SYNONYM) — the primary transactional source table holding payroll batch header records such as batch identifiers, status, reference, and audit columns. The ETRM metadata lists this as a synonym, resolving to the underlying APPS table.
• HR_LOOKUPS (VIEW) — the HR lookup view, joined to resolve batch type descriptions. The join is an outer join on PBH.COMMENTS = L.MEANING(+) with L.LOOKUP_TYPE(+) = 'PAY_PDT_BATCH_TYPES', meaning the batch type is derived from the lookup meaning stored in the batch header's COMMENTS column.
• HR_API (PACKAGE) — referenced as a base object, consistent with HR lookup access conventions used throughout Oracle HRMS and Payroll objects.

The view text applies a DECODE to translate stored status values: status 'P' is reported as 'H', 'U' as 'R', and all other statuses pass through unchanged. It also applies a filter restricting rows to batches where PBH.BATCH_NAME = 'BATCH '||TO_CHAR(PBH.BATCH_ID), effectively limiting the view to batches following the standard naming convention.

Key Columns

• BATCH_ID — Unique identifier for the batch header record; the primary key of the view.
• PAYROLL_ID — Returned as TO_NUMBER(NULL); a placeholder column, not populated from a physical source.
• BUSINESS_GROUP_ID — The business group (legislative/HR organization) to which the batch belongs.
• BATCH_STATUS — The decoded batch status, with 'P' shown as 'H' and 'U' shown as 'R'.
• BATCH_TYPE — Derived from HR_LOOKUPS.LOOKUP_CODE for lookup type PAY_PDT_BATCH_TYPES. This is the column most relevant to the "batch_type" search and indicates the classification of the batch.
• REFERENCE_NUM — The batch reference, sourced from PBH.BATCH_REFERENCE.
• LAST_PROCESSED_DATE — Returned as TO_DATE(NULL); a placeholder column.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard "who/when" tracking.

Common Use Cases and Queries

Typical usage involves extracting batch-level information for reconciliation, reporting, or troubleshooting, and filtering specifically by batch type or status. A representative query grouping batches by type is shown below.

SELECT BATCH_ID,
       BATCH_TYPE,
       BATCH_STATUS,
       REFERENCE_NUM,
       CREATION_DATE
FROM   APPS.PAY_PDT_BATCH_HEADERS
WHERE  BATCH_TYPE = '&batch_type'
ORDER  BY BATCH_ID;

Consumers may also join the view to other payroll objects on BATCH_ID or BUSINESS_GROUP_ID, filter by BATCH_STATUS to isolate in-progress versus completed batches, or use the audit columns for change tracking. Because PAYROLL_ID and LAST_PROCESSED_DATE are null placeholders, reports requiring payroll identification or processing timestamps must source those values elsewhere.