Search Results control_invoice_count

Overview

AP_BATCHES_V is a Payables reporting view owned by the APPS schema in Oracle E-Business Suite. It exposes invoice batch header information from the AP_BATCHES_ALL table, enriched with descriptive values resolved from supporting lookup and reference objects. In the EBS data model, an invoice batch is a grouping mechanism used during high-volume invoice entry and validation; each batch carries control totals (a manually entered expected invoice count and amount) that are reconciled against the actual invoices processed within the batch. AP_BATCHES_V is the primary reporting vehicle for that batch-level reconciliation.

The view is documented as a Release 10SC artifact, and its definition continues to be valid and referenced in Release 12.1.1 and 12.2.2. It is not an interface or a base table for data entry; it is a read-only projection intended for inquiry screens, concurrent-program reports, and custom SQL. Because it references MO_GLOBAL.CHECK_ACCESS in its WHERE clause, the view returns only batches whose operating unit is accessible to the current user session, which makes it a natural fit for multi-org-aware reporting.

Underlying Base Objects

The view is defined over four objects with outer-join dependencies, plus two packages used to derive calculated values and enforce security.

• AP_BATCHES_ALL — the primary source and the alias AB. All column-level data on the batch header (batch name, batch date, control totals, currency codes, and the descriptive flexfield columns) originates here.
• AP_TERMS (alias AT) — outer-joined on TERM_ID to supply the payment terms name.
• FND_DOC_SEQUENCE_CATEGORIES (alias FDSC) — outer-joined on APPLICATION_ID = 200 and CODE = DOC_CATEGORY_CODE to resolve the document category description.
• AP_LOOKUP_CODES (alias ALC2) — outer-joined on LOOKUP_TYPE = 'HOLD CODE' and LOOKUP_CODE = HOLD_LOOKUP_CODE to resolve the hold name shown to users.
• AP_BATCHES_PKG — supplies two scalar functions, GET_ACTUAL_INV_COUNT and GET_ACTUAL_INV_AMOUNT, invoked per batch to compute actual invoice counts and amounts.
• MO_GLOBAL — supplies CHECK_ACCESS(ORG_ID), which filters rows by the operating units the current user may access.

Because the outer joins use the (+) operator, a batch lacking a matching term, document category, or hold code still appears in the result set, with the corresponding descriptive column null.

Key Columns

The view projects the full AP_BATCHES_ALL column list. The most significant columns include BATCH_ID, the primary key; BATCH_NAME and BATCH_DATE, the user-facing batch identifier and creation date; and the control columns CONTROL_INVOICE_COUNT and CONTROL_INVOICE_TOTAL, which hold the operator-entered expected values.

Two derived columns, ACTUAL_INVOICE_COUNT and ACTUAL_INVOICE_TOTAL, are computed by AP_BATCHES_PKG and represent the true populated values, enabling variance reporting between control and actual. Descriptive columns include PAYMENT_TERMS_NAME, DOCUMENT_CATEGORY, and HOLD_NAME, each resolved through the respective outer join. Currency context is provided by INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE. The ORG_ID column identifies the operating unit and is the column evaluated by MO_GLOBAL.CHECK_ACCESS. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present, as are the fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY for descriptive flexfield data. PAY_GROUP_LOOKUP_CODE, PAYMENT_PRIORITY, GL_DATE, and HOLD_REASON support payment grouping, disbursement sequencing, accounting date, and hold analysis respectively.

Common Use Cases and Queries

AP_BATCHES_V is most often queried to reconcile control totals against actual activity, to list batches that remain on hold or unposted, and to drive custom batch-status reports. Queries joining to AP_INVOICES_ALL via BATCH_ID are common when per-invoice detail is required.

• Listing batches by pay group: SELECT batch_name, batch_date, actual_invoice_count, actual_invoice_total FROM ap_batches_v WHERE pay_group_lookup_code = :p_pay_group ORDER BY batch_date;
• Control-to-actual variance: SELECT batch_id, batch_name, control_invoice_count, actual_invoice_count, control_invoice_total, actual_invoice_total FROM ap_batches_v WHERE NVL(control_invoice_total,0) <> NVL(actual_invoice_total,0);
• Open held batches: SELECT batch_name, hold_name, hold_reason FROM ap_batches_v WHERE hold_lookup_code IS NOT NULL;

Note that PAY_GROUP_LOOKUP_CODE is not translated to a display value by this view; users generally join to FND_LOOKUP_VALUES with LOOKUP_TYPE = 'PAY GROUP' to obtain the meaningful pay group name. The pay group column is a key filter for payables clerks preparing payment runs, which is why the search term "pay_group_lookup_code" is frequently associated with this object. All queries return only operating-unit-accessible rows unless the session is configured otherwise.