Skip to content
Fusion Reference

AP_INVOICES_ALL

Product: APtransactionBU-striped (ORG_ID)

Payables invoice headers — one row per supplier invoice, prepayment, or credit/debit memo, with the supplier, invoice number, amounts, payment status, and approval state; business-unit striped

Notes

SET_OF_BOOKS_ID survives in Fusion AP as the LEDGER id (documented FK to GL_LEDGERS) — the legacy name, re-pointed. INVOICE_NUM uniqueness is database-enforced per supplier + BU (+ party) in Fusion — join on INVOICE_ID anyway. VENDOR_SITE_ID carries NO documented FK (the supplier-site table is never named on the page), so no site edge ships — only VENDOR_ID → the supplier master. PAYMENT_STATUS_FLAG is a documented Y/N/P trio.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

Header & line

AP_INVOICES_ALL is the header for its lines in AP_INVOICE_LINES_ALL.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.FinExtractAM.ApBiccExtractAM.InvoiceHeaderExtractPVO
    OTBI: Payables Invoices - Transactions Real Time

    Payables Invoices (header) data store — keyed on ApInvoicesInvoiceId. The subject-area prefix is "Payables Invoices", not "Payables".

    Oracle data-store documentation →

Fields

18 fields · 1 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1INVOICE_IDSurrogate key of the invoice — the join column, not the invoice numberNUMBER
Key
2ORG_IDThe business unit owning the invoiceNUMBER
3INVOICE_NUMSupplier invoice number — unique per supplier + BU (+ party), database-enforced in FusionVARCHAR2
4INVOICE_DATEInvoice dateDATE
Filter date
5VENDOR_IDSupplierNUMBER
6VENDOR_SITE_IDSupplier site — carries no documented FK in the dictionary, so no site edge shipsNUMBER
7PARTY_IDThe invoicing TCA partyNUMBER
8INVOICE_TYPE_LOOKUP_CODEInvoice category (standard, credit memo, prepayment…) — no value list in the dictionaryVARCHAR2
9SOURCEThe feeder system the invoice arrived fromVARCHAR2
10INVOICE_AMOUNTInvoice amount in transaction currencyNUMBER
11AMOUNT_PAIDAmount paid against the invoiceNUMBER
12INVOICE_CURRENCY_CODEInvoice currencyVARCHAR2
13PAYMENT_STATUS_FLAGY paid, N unpaid, P partially paid — page-documented trioVARCHAR2
14WFAPPROVAL_STATUSInvoice approval-workflow status — values not enumerated in the dictionaryVARCHAR2
15GL_DATEAccounting date defaulted to the distributionsDATE
16TERMS_IDPayment termsNUMBER
17ACCTS_PAY_CODE_COMBINATION_IDThe AP liability account (CCID)NUMBER
18SET_OF_BOOKS_IDThe LEDGER — the legacy column name survives in Fusion AP, re-pointed at the ledger masterNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of AP_INVOICES_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : AP_INVOICES_ALL — Payables invoice headers — one row per supplier invoice, prepayment, or credit/debit memo, with the supplier, invoice number, amounts, payment status, and approval state; business-unit striped
-- Purpose: Column-selected read of AP_INVOICES_ALL — auto-generated from field metadata
-- Grain  : One row per business unit (ORG_ID) + INVOICE_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.INVOICE_ID AS "Surrogate key of the invoice — the join column, not the invoice number",
  t.ORG_ID AS "The business unit owning the invoice",
  t.INVOICE_NUM AS "Supplier invoice number — unique per supplier + BU (+ party), database-enforced in Fusion",
  t.INVOICE_DATE AS "Invoice date",
  t.VENDOR_ID AS "Supplier",
  t.VENDOR_SITE_ID AS "Supplier site — carries no documented FK in the dictionary, so no site edge ships",
  t.PARTY_ID AS "The invoicing TCA party",
  t.INVOICE_TYPE_LOOKUP_CODE AS "Invoice category (standard, credit memo, prepayment…) — no value list in the dictionary",
  t.SOURCE AS "The feeder system the invoice arrived from",
  t.INVOICE_AMOUNT AS "Invoice amount in transaction currency",
  t.AMOUNT_PAID AS "Amount paid against the invoice",
  t.INVOICE_CURRENCY_CODE AS "Invoice currency",
  t.PAYMENT_STATUS_FLAG AS "Y paid, N unpaid, P partially paid — page-documented trio",
  t.WFAPPROVAL_STATUS AS "Invoice approval-workflow status — values not enumerated in the dictionary",
  t.GL_DATE AS "Accounting date defaulted to the distributions",
  t.TERMS_ID AS "Payment terms",
  t.ACCTS_PAY_CODE_COMBINATION_ID AS "The AP liability account (CCID)",
  t.SET_OF_BOOKS_ID AS "The LEDGER — the legacy column name survives in Fusion AP, re-pointed at the ledger master"
FROM <catalog>.<schema>.AP_INVOICES_ALL t
WHERE
  t.ORG_ID = <business_unit_id>  -- business unit — Fusion _ALL means BU, not the EBS operating unit; see quirks guide #all-means-bu
  -- AND t.INVOICE_ID = <INVOICE_ID>
  -- AND t.INVOICE_DATE >= DATE '<DATE_FROM>'
  -- AND t.INVOICE_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.INVOICE_ID;

7 parameters not filled: <catalog>, <schema>, <business_unit_id>, <INVOICE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • AP_INVOICES_ALLAP_INVOICE_LINES_ALLheader line · 1:N
    ON AP_INVOICES_ALL.INVOICE_ID = AP_INVOICE_LINES_ALL.INVOICE_ID AND AP_INVOICES_ALL.ORG_ID = AP_INVOICE_LINES_ALL.ORG_ID
  • AP_INVOICE_DISTRIBUTIONS_ALLAP_INVOICES_ALLforeign key · N:1
    ON AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID = AP_INVOICES_ALL.INVOICE_ID AND AP_INVOICE_DISTRIBUTIONS_ALL.ORG_ID = AP_INVOICES_ALL.ORG_ID
  • AP_INVOICES_ALLPOZ_SUPPLIERSforeign key · N:1
    ON AP_INVOICES_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
  • AP_INVOICES_ALLHZ_PARTIESforeign key · N:1
    ON AP_INVOICES_ALL.PARTY_ID = HZ_PARTIES.PARTY_ID
  • AP_INVOICES_ALLGL_CODE_COMBINATIONSforeign key · N:1
    ON AP_INVOICES_ALL.ACCTS_PAY_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
  • AP_INVOICES_ALLGL_LEDGERSforeign key · N:1
    ON AP_INVOICES_ALL.SET_OF_BOOKS_ID = GL_LEDGERS.LEDGER_ID
  • AP_INVOICES_ALLFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON AP_INVOICES_ALL.ORG_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID

Browse more Financialstables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.