Search Results ap_pbatch_sets_v

Overview

AP_PBATCH_SETS_V is a reporting view in the Oracle E-Business Suite Payables (AP) module, owned by the APPS schema and documented as VALID in ETRM for releases 12.1.1 and 12.2.2. It exposes the batch set definitions maintained by Oracle Payables, providing a stable, read-oriented projection over the underlying payment batch set table. A "batch set" is the grouping construct used in Payables to define how multiple payment batches are assembled and processed together, typically for scheduled or automated payment runs. Because the view is a thin, unjoined projection of its base table, it carries the same row cardinality as the base table and imposes no filtering, aggregation, or business logic of its own. Its role in EBS reporting and integration is therefore that of a named, APPS-owned interface that external programs, custom concurrent programs, and reporting tools can query without referencing the raw table directly. The view includes the ROWID pseudo-column exposed as ROW_ID, which allows downstream PL/SQL or integration code to address individual rows for update or lock processing through the view definition.

Underlying Base Objects

The view is defined over a single base object, documented in ETRM as the synonym AP_PBATCH_SETS, resolving to the underlying APPS-owned table of the same name. The view text is a straightforward SELECT over that table, listing ROWID and the batch set columns with no joins, unions, or subqueries. This one-to-one relationship means that any column present in the base table that is not listed in the view text is unavailable through the view, and no denormalized or derived attributes are introduced. Because the view is owned by APPS and exposed publicly, it functions as part of the supported Payables data access surface, while the base table retains all write activity performed by the Payables payment batch programs.

Key Columns

• ROW_ID — the ROWID of the underlying base table row, exposed for row-level addressing.
• BATCH_SET_ID — the unique identifier of the payment batch set; the primary key for joining to batch set related objects.
• BATCH_SET_NAME — the user-defined name of the batch set as displayed in Payables setup and selection windows.
• ORG_ID — the operating unit identifier, enabling Multi-Org filtered queries.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification, the user, and the login session.
• CREATION_DATE, CREATED_BY — creation audit columns recording when and by whom the batch set record was inserted.
• INACTIVE_DATE — the date on which the batch set was inactivated; a null value indicates an active batch set, while a populated value indicates the set is no longer available for use.

Common Use Cases and Queries

Typical usage centers on validating batch set configuration before payment processing, auditing batch set maintenance activity, and feeding batch set definitions into custom reports. Because the view is filtered by operating unit, Multi-Org views or explicit ORG_ID predicates should be applied in a multi-organization environment. The following query lists active batch sets for an operating unit:

SELECT batch_set_id, batch_set_name, org_id, creation_date
FROM apps.ap_pbatch_sets_v
WHERE org_id = :p_org_id
AND inactive_date IS NULL
ORDER BY batch_set_name;

Auditing recently modified definitions is equally common:

SELECT batch_set_name, last_update_date, last_updated_by
FROM apps.ap_pbatch_sets_v
WHERE last_update_date >= :p_since_date;

Joins to batch-related objects are keyed on BATCH_SET_ID, and the exposed ROW_ID supports row-level processing in integration code. Because no filtering is applied by the view itself, callers must supply their own predicates, particularly for INACTIVE_DATE and ORG_ID, to obtain the intended result set.