AP_INVOICE_DISTRIBUTIONS_ALL
Product: APtransactionBU-striped (ORG_ID)Payables invoice distributions — the accounting grain under each line: one row per charged GL account with the amount, accounting date, period, and posted state; where AP spend meets the ledger
Accounting grain — a line can split across several distributions, so joining lines to distributions multiplies line amounts
DIST_CODE_COMBINATION_ID is the charged account (documented FK to the code-combinations master). The parent-line link is composite: INVOICE_ID + INVOICE_LINE_NUMBER. POSTED_FLAG is a documented Y/N. Reversals and cancellations stay as paired rows (REVERSAL_FLAG / CANCELLATION_FLAG) — net, don't count.
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
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.InvoiceDistributionExtractPVOOTBI: Payables Invoices - Transactions Real Time
Invoice Distributions data store — keyed on ApInvoiceDistributionsInvoiceDistributionId.
Oracle data-store documentation (opens in new tab)
Fields
16 fields · 1 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVOICE_DISTRIBUTION_ID | Surrogate key of the distribution | NUMBER | Key |
| 2 | INVOICE_ID | The invoice | NUMBER | |
| 3 | INVOICE_LINE_NUMBER | The invoice line — pairs with INVOICE_ID for the composite line join | NUMBER | |
| 4 | ORG_ID | The business unit owning the distribution | NUMBER | |
| 5 | DISTRIBUTION_LINE_NUMBER | Distribution number within the invoice | NUMBER | |
| 6 | LINE_TYPE_LOOKUP_CODE | Distribution type | VARCHAR2 | INVOICE DISTRIBUTION TYPE |
| 7 | DIST_CODE_COMBINATION_ID | The charged GL account (CCID) | NUMBER | |
| 8 | ACCOUNTING_DATE | Date the distribution is accounted | DATE | Filter date |
| 9 | PERIOD_NAME | Accounting period | VARCHAR2 | |
| 10 | AMOUNT | Distribution amount in invoice currency | NUMBER | |
| 11 | BASE_AMOUNT | Amount in ledger currency, for foreign-currency invoices | NUMBER | |
| 12 | POSTED_FLAG | Y accounted, N not — page-documented | VARCHAR2 | |
| 13 | REVERSAL_FLAG | Part of a reversal pair — net, don't count | VARCHAR2 | |
| 14 | PO_DISTRIBUTION_ID | Matched PO distribution | NUMBER | |
| 15 | RCV_TRANSACTION_ID | Matched receiving transaction | NUMBER | |
| 16 | SET_OF_BOOKS_ID | The LEDGER — legacy column name, required here | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of AP_INVOICE_DISTRIBUTIONS_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_DISTRIBUTION_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : AP_INVOICE_DISTRIBUTIONS_ALL — Payables invoice distributions — the accounting grain under each line: one row per charged GL account with the amount, accounting date, period, and posted state; where AP spend meets the ledger
-- Purpose: Column-selected read of AP_INVOICE_DISTRIBUTIONS_ALL — auto-generated from field metadata
-- Grain : One row per business unit (ORG_ID) + INVOICE_DISTRIBUTION_ID
-- Caution: Accounting grain — a line can split across several distributions, so joining lines to distributions multiplies line amounts
-- 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_DISTRIBUTION_ID AS "Surrogate key of the distribution",
t.INVOICE_ID AS "The invoice",
t.INVOICE_LINE_NUMBER AS "The invoice line — pairs with INVOICE_ID for the composite line join",
t.ORG_ID AS "The business unit owning the distribution",
t.DISTRIBUTION_LINE_NUMBER AS "Distribution number within the invoice",
t.LINE_TYPE_LOOKUP_CODE AS "Distribution type", -- decode t.LINE_TYPE_LOOKUP_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'INVOICE DISTRIBUTION TYPE', LANGUAGE-filtered)
t.DIST_CODE_COMBINATION_ID AS "The charged GL account (CCID)",
t.ACCOUNTING_DATE AS "Date the distribution is accounted",
t.PERIOD_NAME AS "Accounting period",
t.AMOUNT AS "Distribution amount in invoice currency",
t.BASE_AMOUNT AS "Amount in ledger currency, for foreign-currency invoices",
t.POSTED_FLAG AS "Y accounted, N not — page-documented",
t.REVERSAL_FLAG AS "Part of a reversal pair — net, don't count",
t.PO_DISTRIBUTION_ID AS "Matched PO distribution",
t.RCV_TRANSACTION_ID AS "Matched receiving transaction",
t.SET_OF_BOOKS_ID AS "The LEDGER — legacy column name, required here"
FROM <catalog>.<schema>.AP_INVOICE_DISTRIBUTIONS_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_DISTRIBUTION_ID = <INVOICE_DISTRIBUTION_ID>
-- AND t.ACCOUNTING_DATE >= DATE '<DATE_FROM>'
-- AND t.ACCOUNTING_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.INVOICE_DISTRIBUTION_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.
Join details
ON AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID = AP_INVOICES_ALL.INVOICE_ID AND AP_INVOICE_DISTRIBUTIONS_ALL.ORG_ID = AP_INVOICES_ALL.ORG_IDON AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_LINE_NUMBER = AP_INVOICE_LINES_ALL.LINE_NUMBER AND AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID = AP_INVOICE_LINES_ALL.INVOICE_ID AND AP_INVOICE_DISTRIBUTIONS_ALL.ORG_ID = AP_INVOICE_LINES_ALL.ORG_IDON AP_INVOICE_DISTRIBUTIONS_ALL.LINE_TYPE_LOOKUP_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'INVOICE DISTRIBUTION TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'ON AP_INVOICE_DISTRIBUTIONS_ALL.DIST_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON AP_INVOICE_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID = PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_IDON AP_INVOICE_DISTRIBUTIONS_ALL.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID
More Financials tables
- AP_INVOICE_LINES_ALLPayables invoice lines — the goods/services, freight, tax, and prepayment rows under each invoice, carrying the amount, quantity, and the PO/receipt match pointers
- AP_INVOICES_ALLPayables 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
- 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