Search Results ap_batches_all

Overview

The AP_BATCHES_ALL table is a core data structure within the Oracle E-Business Suite Payables (AP) module. It serves as the master repository for summary-level information pertaining to invoice batches. An invoice batch is a logical grouping mechanism used to consolidate multiple supplier invoices for streamlined entry, validation, and posting. This table's primary role is to maintain batch-level attributes, such as name, date, and control totals, which govern the processing of all invoices assigned to it. The inclusion of "_ALL" in the table name signifies it is a multi-organization table, storing data for all operating units defined within the instance, with access controlled by the MOAC (Multi-Org Access Control) security model.

Key Information Stored

The table stores essential batch header information. The primary key is BATCH_ID, a unique system-generated identifier. The BATCH_NAME and BATCH_DATE columns form a unique key (AP_BATCHES_UK1), enforcing business-level uniqueness for a batch. Key columns include control totals like BATCH_AMOUNT (the sum of invoice amounts) and BATCH_COUNT (the number of invoices), which are compared to the sum of its child invoices for validation. Currency information is stored in INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE, linked to FND_CURRENCIES. The BATCH_CODE_COMBINATION_ID links to GL_CODE_COMBINATIONS, defining the default accounting flexfield for the batch. Status is tracked via columns such as BATCH_STATUS and POSTING_STATUS.

Common Use Cases and Queries

This table is central for batch control reporting, reconciliation, and audit inquiries. Common operational queries involve listing batches for a specific period or operating unit, identifying batches with mismatched control totals, or finding invoices within a problematic batch. A typical query to review batch summary information would be:

• SELECT batch_name, batch_date, batch_amount, batch_count, posting_status FROM ap_batches_all WHERE org_id = :org_id AND TRUNC(batch_date) BETWEEN :start_date AND :end_date ORDER BY batch_date DESC;

For reconciliation, a query might join to AP_INVOICES_ALL to compare batch totals against the sum of its constituent invoices. Technical support often queries this table to trace the source of posting errors or to investigate issues during the Invoice Validation or Payment processes that are batch-specific.

Related Objects

AP_BATCHES_ALL has critical relationships with several key Payables tables, as indicated by its foreign keys. It is the parent table for AP_INVOICES_ALL via the BATCH_ID column, forming the core batch-invoice hierarchy. This relationship extends to invoice distributions (AP_INVOICE_DISTRIBUTIONS_ALL) and payment schedules (AP_PAYMENT_SCHEDULES_ALL). It also relates to AP_RECURRING_PAYMENTS_ALL. For currency validation, it references FND_CURRENCIES twice. The default accounting link is to GL_CODE_COMBINATIONS. Standard EBS views like AP_BATCHES (a single-org view filtered by MOAC) are built upon this base table for reporting and application logic.