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
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. The dictionary lists VENDOR_SITE_ID in its foreign-key rows but names no target table or column, so no supplier-site edge ships; only VENDOR_ID → the supplier master is drawn. PAYMENT_STATUS_FLAG is a documented Y/N/P trio.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.InvoiceHeaderExtractPVOOTBI: 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 (opens in new tab)
Fields
18 fields · 1 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVOICE_ID | Surrogate key of the invoice — the join column, not the invoice number | NUMBER | Key |
| 2 | ORG_ID | The business unit owning the invoice | NUMBER | |
| 3 | INVOICE_NUM | Supplier invoice number — unique per supplier + BU (+ party), database-enforced in Fusion | VARCHAR2 | |
| 4 | INVOICE_DATE | Invoice date | DATE | Filter date |
| 5 | VENDOR_ID | Supplier | NUMBER | |
| 6 | VENDOR_SITE_ID | Supplier site — carries no documented FK in the dictionary, so no site edge ships | NUMBER | |
| 7 | PARTY_ID | The invoicing TCA party | NUMBER | |
| 8 | INVOICE_TYPE_LOOKUP_CODE | Invoice category (standard, credit memo, prepayment…) — no value list in the dictionary | VARCHAR2 | |
| 9 | SOURCE | The feeder system the invoice arrived from | VARCHAR2 | |
| 10 | INVOICE_AMOUNT | Invoice amount in transaction currency | NUMBER | |
| 11 | AMOUNT_PAID | Amount paid against the invoice | NUMBER | |
| 12 | INVOICE_CURRENCY_CODE | Invoice currency | VARCHAR2 | |
| 13 | PAYMENT_STATUS_FLAG | Y paid, N unpaid, P partially paid — page-documented trio | VARCHAR2 | |
| 14 | WFAPPROVAL_STATUS | Invoice approval-workflow status — values not enumerated in the dictionary | VARCHAR2 | |
| 15 | GL_DATE | Accounting date defaulted to the distributions | DATE | |
| 16 | TERMS_ID | Payment terms | NUMBER | |
| 17 | ACCTS_PAY_CODE_COMBINATION_ID | The AP liability account (CCID) | NUMBER | |
| 18 | SET_OF_BOOKS_ID | The LEDGER — the legacy column name survives in Fusion AP, re-pointed at the ledger master | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of AP_INVOICES_ALL on 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.
7 parameters not filled: <catalog>, <schema>, <business_unit_id>, <INVOICE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- 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;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Loading relationship diagram…
Join details
ON AP_INVOICES_ALL.INVOICE_ID = AP_INVOICE_LINES_ALL.INVOICE_ID AND AP_INVOICES_ALL.ORG_ID = AP_INVOICE_LINES_ALL.ORG_IDON AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID = AP_INVOICES_ALL.INVOICE_ID AND AP_INVOICE_DISTRIBUTIONS_ALL.ORG_ID = AP_INVOICES_ALL.ORG_IDON AP_INVOICES_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_IDON AP_INVOICES_ALL.PARTY_ID = HZ_PARTIES.PARTY_IDON AP_INVOICES_ALL.ACCTS_PAY_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON AP_INVOICES_ALL.SET_OF_BOOKS_ID = GL_LEDGERS.LEDGER_IDON AP_INVOICES_ALL.ORG_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
More Financials tables
- AR_CASH_RECEIPTS_ALLCash receipts — one row per receipt entered, with receipt number, date, amount, status, and the paying customer account; the cash side that payment schedules apply against
- AR_PAYMENT_SCHEDULES_ALLThe open-receivables ledger — one row per installment of every transaction and receipt, restated as amounts due, applied, and remaining; the table AR aging actually reads
- GL_JE_HEADERSGeneral ledger journal headers — one row per journal within a batch, with the ledger, category, source, period, currency, posting status, and running debit/credit totals
- GL_JE_LINESGeneral ledger journal lines — the debit/credit grain: one row per line with the account combination, entered and accounted amounts, effective date, and the drill-back link to subledger accounting
- RA_CUSTOMER_TRX_ALLReceivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit striped
- RA_CUSTOMER_TRX_LINES_ALLReceivables transaction lines — mixed row kinds under each transaction: LINE rows carry the goods/services amounts, TAX and FREIGHT rows attach to their parent line, CB rows carry chargebacks