Results for “batch_date”

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

Overview

AP_BATCHES_ALL is a Payables (AP) table that stores summary invoice batch information. In Oracle E-Business Suite 12.1.1 and 12.2.2, an "invoice batch" is an optional grouping construct used when Payables is configured to require batch control (the Use Batch Control profile option). A batch provides a named, dated container into which invoices are entered before they are validated, accounted, and paid, and it aggregates control totals that can be compared against the actual totals of the invoices and distributions associated with it. The table is the master header record for that grouping.

From a dimensional-modelling perspective, the mined ETRM relationship data classifies AP_BATCHES_ALL as hub-leaning. This is a modelling suggestion rather than an EBS constraint: the table holds a stable, uniquely identified business entity (a batch) whose surrogate key is referenced by several dependent transactional tables. Treating BATCH_ID as a hub key is a reasonable starting point for a data-vault or warehouse design, with the dependent invoice, distribution, schedule, and recurring-payment rows modelled as links or satellites.

Key Information Stored

The table contains 40 documented columns. The most significant are:

• BATCH_ID — the surrogate primary key (AP_BATCHES_PK) and the single-column unique index AP_BATCHES_U1. This is the value propagated to every dependent table.
• BATCH_NAME and BATCH_DATE — the user-visible batch identifier. Together with ORG_ID they form the business-key unique index AP_BATCHES_U2.
• CONTROL_INVOICE_COUNT and CONTROL_INVOICE_TOTAL — the operator-entered expected count and amount for the batch, used as the control figures.
• ACTUAL_INVOICE_COUNT and ACTUAL_INVOICE_TOTAL — the system-maintained actual values, compared against the control figures to determine whether a batch balances.
• INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE — foreign keys to FND_CURRENCIES governing the batch's invoice and payment currencies.
• BATCH_CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS, supplying the default accounting flexfield for the batch.
• TERMS_ID, PAY_GROUP_LOOKUP_CODE, PAYMENT_PRIORITY, and GL_DATE — payment terms and payment attributes defaulted to invoices in the batch.
• INVOICE_TYPE_LOOKUP_CODE, DOC_CATEGORY_CODE, HOLD_LOOKUP_CODE, and HOLD_REASON — invoice type, document category, and batch-level hold information.
• ORG_ID — the operating unit, a key partitioning column in multi-org environments.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield storage.
• Standard WHO columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting includes batch control reconciliation, batch ageing, and batch-level audit trails. A common pattern selects unbalanced batches:

• SELECT batch_id, batch_name, batch_date, control_invoice_total, actual_invoice_total FROM ap.ap_batches_all WHERE org_id = :org_id AND NVL(control_invoice_total,0) <> NVL(actual_invoice_total,0);
• Counting invoices per batch by joining to AP_INVOICES_ALL on BATCH_ID and grouping by batch.
• Listing batches by currency using a join to FND_CURRENCIES on INVOICE_CURRENCY_CODE or PAYMENT_CURRENCY_CODE.
• Batch ageing using BATCH_DATE against current date, filtered by ORG_ID for operating-unit security.

Because ORG_ID participates in the business-key unique index, all queries should be constrained by operating unit to avoid cross-org leakage.

Related Objects

AP_BATCHES_ALL sits at the head of a one-to-many hierarchy. The following objects reference it via BATCH_ID and are the most significant for joins and impact analysis:

• AP_INVOICES_ALL (BATCH_ID) — the invoices assigned to the batch.
• AP_INVOICE_DISTRIBUTIONS_ALL (BATCH_ID) — distribution lines carried by the batch.
• AP_PAYMENT_SCHEDULES_ALL (BATCH_ID) — scheduled payment rows.
• AP_RECURRING_PAYMENTS_ALL (BATCH_ID) — recurring payment templates entered within a batch.

Upstream reference objects are FND_CURRENCIES (via INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE) and GL_CODE_COMBINATIONS (via BATCH_CODE_COMBINATION_ID). These joins resolve currency and accounting-flexfield descriptions for batch reporting. When deleting or purging batches, all four dependent AP tables must be considered, since they carry the BATCH_ID foreign key.