Search Results ap_invoices_all




Overview
Explore in AI Chat

Overview

AP_INVOICES_ALL is the central transaction table in the Oracle Payables (AP) module, storing one row for every invoice, credit memo, debit memo, prepayment, and expense report advance processed by the application. Living in the AP schema, it holds the header-level information that drives invoice validation, approval, accounting, and payment. Each record represents the supplier-facing document before its distribution lines, payment schedules, holds, and matches are resolved. AP_INVOICES_ALL is distinct from AP_INVOICE_LINES_ALL, which stores line detail; the header table carries amounts, currency, terms, supplier, and status attributes for the invoice as a whole.

In Oracle EBS 12.1.1 and 12.2.2 the table is a partitioned, multi-organization-aware object, with ORG_ID controlling operating unit access and SET_OF_BOOKS_ID anchoring the ledger. Because virtually every downstream Payables process — validation, accounting, withholding, payments, and accrual reconciliation — refers back to INVOICE_ID, this object behaves as a natural hub in a dimensional or Data Vault model. The metadata's heuristic classification of hub is consistent with that role: the table holds the durable business key of the invoice and the descriptive context for the transaction event.

Key Information Stored

With 191 documented columns, AP_INVOICES_ALL is broad, but a smaller set carries most of its meaning. The surrogate primary key is INVOICE_ID (enforced by AP_INVOICES_PK and the unique index AP_INVOICES_U1), and it is the column to which nearly every child table joins. Business-key candidates documented via unique indexes include DOC_SEQUENCE_ID combined with DOC_SEQUENCE_VALUE (AP_INVOICES_U3), which captures the supplier-facing document sequence number, and the natural identifying combination of VENDOR_ID, INVOICE_NUM, and SET_OF_BOOKS_ID commonly used to detect duplicates.

Common Use Cases and Queries

Reporting and reconciliation against AP_INVOICES_ALL is routine in Payables and subledger accounting. A typical query joins header to lines and distributions to produce an invoice-level summary. For example, open invoices awaiting payment:

  • Filter on PAYMENT_STATUS_FLAG = 'N' and APPROVAL_STATUS = 'A' to list unpaid, approved invoices by supplier.
  • Match to PO_HEADERS_ALL via PO_HEADER_ID to compare invoiced versus ordered quantities.
  • Aggregate INVOICE_AMOUNT and BASE_AMOUNT by SET_OF_BOOKS_ID and GL_DATE for period close.
  • Join AP_PAYMENT_SCHEDULES_ALL.INVOICE_ID = AP_INVOICES_ALL.INVOICE_ID to derive aging and due dates.
  • Query AP_HOLDS_ALL by INVOICE_ID to report invoices blocked from payment.

A representative pattern is: SELECT i.INVOICE_NUM, i.INVOICE_DATE, i.INVOICE_AMOUNT FROM AP.AP_INVOICES_ALL i WHERE i.ORG_ID = :org AND i.PAYMENT_STATUS_FLAG = 'N' ORDER BY i.INVOICE_DATE;. Duplicate detection uses VENDOR_ID plus INVOICE_NUM.

Related Objects

AP_INVOICES_ALL sits at the center of a dense foreign-key graph. The most significant dependents and references include:

  • AP_INVOICE_LINES_ALL — joins on INVOICE_ID; stores the line-level detail beneath the header.
  • AP_INVOICE_DISTRIBUTIONS_ALL — joins on INVOICE_ID; the accounting distributions that post to the GL.
  • AP_PAYMENT_SCHEDULES_ALL — joins on INVOICE_ID; defines due dates and payment amounts.
  • AP_HOLDS_ALL — joins on INVOICE_ID; records validation and matching holds.
  • AP_INVOICE_PAYMENTS_ALL — joins on INVOICE_ID; links invoices to the payments settling them.
  • AP_BATCHES_ALL — referenced via BATCH_ID for invoice batching.
  • PO_HEADERS_ALL — referenced via PO_HEADER_ID for matched purchase orders.
  • PO_VENDORS / AP_SUPPLIER_SITES_ALL — supplier and supplier site master data referenced by VENDOR_ID and VENDOR_SITE_ID.
  • GL_CODE_COMBINATIONS — referenced via ACCTS_PAY_CODE_COMBINATION_ID and PA_DEFAULT_DIST_CCID.
  • AP_INVOICE_PREPAYS_ALL and FV_INVOICE_RETURNS_ALL — public-sector and prepayment application tables joining on INVOICE_ID.

Together these relationships make AP_INVOICES_ALL the hub through which Payables header data is extended into lines, distributions, payments, and holds.