Results for “batch_set_name”

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

Overview

AP_PBATCH_SETS_ALL is the Oracle Payables table that stores payment batch set definitions. A payment batch set is a named grouping construct used by the Automatic Payment Program to organize and process multiple payment batches as a logical unit within a single payment run. The table resides in the AP schema and is classified as VALID in the ETRM 12.2.2 metadata. Its role is fundamentally organizational: it provides the header-level identity to which selection criteria and individual batch lines are attached, enabling users to define reusable grouping rules for payment processing across operating units.

From a dimensional modeling perspective, the mined Data Vault classification of AP_PBATCH_SETS_ALL is hub-leaning. The metadata documentation notes that this classification is a heuristic derived from the foreign key structure rather than a formally published designation, and it should be treated as a modeling suggestion. Practically, this means the table behaves as a business entity registry — a hub keyed on the payment batch set — with descriptive satellite attributes (name, inactive date) and link-like dependencies to the selection criteria and batch line tables that reference it.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• BATCH_SET_ID — The surrogate primary key, enforced as AP_PBATCH_SETS_PK and reinforced by unique index AP_PBATCH_SETS_U1. It is the column propagated to all dependent tables as a foreign key.
• BATCH_SET_NAME — The user-facing name of the payment batch set. Together with ORG_ID it forms the business-key candidate captured in unique index AP_PBATCH_SETS_U2.
• ORG_ID — The operating unit identifier, providing the multi-org partitioning context that scopes batch set names within a legal entity or business unit.
• INACTIVE_DATE — The date on which the batch set was deactivated, supporting soft lifecycle management without physical deletion.
• LAST_UPDATE_DATE — The timestamp of the most recent modification, essential for incremental extraction and change-data-capture reporting.
• LAST_UPDATED_BY — The application user who performed the last update.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, useful for audit tracing.
• CREATION_DATE — The date the batch set record was first created.
• CREATED_BY — The application user who created the record.

The distinction between the surrogate key and the business key is important: BATCH_SET_ID is a system-generated identifier used for referential integrity, while BATCH_SET_NAME plus ORG_ID is the combination users recognize and query by. The standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present in full.

Common Use Cases and Queries

Payment batch sets are typically queried when administrators need to list, audit, or reconcile the grouping definitions used for payment runs. Typical patterns include listing active batch sets for an operating unit, and identifying sets that reference specific selection criteria. Examples:

• List active batch sets for the current operating unit: SELECT BATCH_SET_ID, BATCH_SET_NAME, CREATION_DATE FROM AP_PBATCH_SETS_ALL WHERE ORG_ID = :org_id AND (INACTIVE_DATE IS NULL OR INACTIVE_DATE > SYSDATE);
• Resolve a name to its surrogate key: SELECT BATCH_SET_ID FROM AP_PBATCH_SETS_ALL WHERE BATCH_SET_NAME = :name AND ORG_ID = :org_id;
• Find selection criteria attached to a batch set: join AP_INV_SELECTION_CRITERIA_ALL on BATCH_SET_ID.
• Incremental audit by last update: filter on LAST_UPDATE_DATE > :last_run for ETL or reconciliation extracts.

Related Objects

• AP_PBATCH_SET_LINES_ALL — References AP_PBATCH_SETS_ALL via BATCH_SET_ID; holds the individual batch lines within the set.
• AP_INV_SELECTION_CRITERIA_ALL — References AP_PBATCH_SETS_ALL via BATCH_SET_ID; stores the invoice selection criteria associated with the set.
• AP_PBATCH_SETS_PK / AP_PBATCH_SETS_U1 / AP_PBATCH_SETS_U2 — Primary key and unique indexes anchoring BATCH_SET_ID and the BATCH_SET_NAME/ORG_ID business key.
• AP_PAYMENT_SCHEDULES_ALL and related payment tables — Consumed downstream once batches within a set are processed by the payment program.
• AP_INVOICES_ALL — Invoices selected through the criteria chain ultimately flow into the payment batches grouped by these sets.