Skip to content
Fusion Reference

PO_DISTRIBUTIONS_ALL

Product: POtransaction

PO accounting distributions — how each schedule's quantity charges out: destination type and org, deliver-to, the GL charge account, project costing columns, and the requisition distribution it fulfills

Grain note

Accounting grain — a schedule can split across several distributions, so joining schedules to distributions multiplies quantities

Notes

The only PO level carrying GL accounts (CODE_COMBINATION_ID plus budget/accrual/variance accounts) — spend-to-GL joins happen here. Project columns wear the PJC_ prefix (PJC_PROJECT_ID, not PROJECT_ID). REQ_DISTRIBUTION_ID is the system link back to the requisition.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.

Fields

17 fields · 1 key

17 fields.

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1PO_DISTRIBUTION_IDSurrogate key of the distributionNUMBER
Key
2LINE_LOCATION_IDParent scheduleNUMBER
3PO_LINE_IDParent line (denormalized)NUMBER
4PO_HEADER_IDParent header (denormalized)NUMBER
5DISTRIBUTION_NUMVisible distribution numberNUMBER
6QUANTITY_ORDEREDQuantity allocated to this distributionNUMBER
7QUANTITY_DELIVEREDQuantity delivered against itNUMBER
8QUANTITY_BILLEDQuantity invoiced against itNUMBER
9QUANTITY_CANCELLEDQuantity cancelledNUMBER
10DESTINATION_TYPE_CODEInventory vs expense destinationVARCHAR2
11DESTINATION_ORGANIZATION_IDFinal destination organization — resolves through the HR org masterNUMBER
12DESTINATION_SUBINVENTORYTarget subinventory for inventory destinationsVARCHAR2
13DELIVER_TO_PERSON_IDThe requester the goods are delivered toNUMBER
14CODE_COMBINATION_IDGL charge account — the only PO level carrying GL accountsNUMBER
15REQ_DISTRIBUTION_IDSource requisition distribution — the system link back to the requisitionNUMBER
16PJC_PROJECT_IDProject-costing project — note the PJC_ prefixNUMBER
17RATECurrency conversion rateNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of PO_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.

Query parameters

4 parameters not filled: <catalog>, <schema>, <PO_DISTRIBUTION_ID>, <watermark>

-- ============================================================
-- Table  : PO_DISTRIBUTIONS_ALL — PO accounting distributions — how each schedule's quantity charges out: destination type and org, deliver-to, the GL charge account, project costing columns, and the requisition distribution it fulfills
-- Purpose: Column-selected read of PO_DISTRIBUTIONS_ALL — auto-generated from field metadata
-- Grain  : One row per PO_DISTRIBUTION_ID
-- Caution: Accounting grain — a schedule can split across several distributions, so joining schedules to distributions multiplies quantities
-- 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.PO_DISTRIBUTION_ID AS "Surrogate key of the distribution",
  t.LINE_LOCATION_ID AS "Parent schedule",
  t.PO_LINE_ID AS "Parent line (denormalized)",
  t.PO_HEADER_ID AS "Parent header (denormalized)",
  t.DISTRIBUTION_NUM AS "Visible distribution number",
  t.QUANTITY_ORDERED AS "Quantity allocated to this distribution",
  t.QUANTITY_DELIVERED AS "Quantity delivered against it",
  t.QUANTITY_BILLED AS "Quantity invoiced against it",
  t.QUANTITY_CANCELLED AS "Quantity cancelled",
  t.DESTINATION_TYPE_CODE AS "Inventory vs expense destination",
  t.DESTINATION_ORGANIZATION_ID AS "Final destination organization — resolves through the HR org master",
  t.DESTINATION_SUBINVENTORY AS "Target subinventory for inventory destinations",
  t.DELIVER_TO_PERSON_ID AS "The requester the goods are delivered to",
  t.CODE_COMBINATION_ID AS "GL charge account — the only PO level carrying GL accounts",
  t.REQ_DISTRIBUTION_ID AS "Source requisition distribution — the system link back to the requisition",
  t.PJC_PROJECT_ID AS "Project-costing project — note the PJC_ prefix",
  t.RATE AS "Currency conversion rate"
FROM <catalog>.<schema>.PO_DISTRIBUTIONS_ALL t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.PO_DISTRIBUTION_ID = <PO_DISTRIBUTION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.PO_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

  • PO_DISTRIBUTIONS_ALLPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON PO_DISTRIBUTIONS_ALL.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID
  • PO_DISTRIBUTIONS_ALLGL_CODE_COMBINATIONSforeign key · N:1
    ON PO_DISTRIBUTIONS_ALL.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
  • PO_DISTRIBUTIONS_ALLHR_ALL_ORGANIZATION_UNITS_Fforeign key · N:1
    ON PO_DISTRIBUTIONS_ALL.DESTINATION_ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_ID AND CURRENT_DATE BETWEEN HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_START_DATE AND HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (HR_ALL_ORGANIZATION_UNITS_F) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.
  • AP_INVOICE_LINES_ALLPO_DISTRIBUTIONS_ALLforeign key · N:1
    ON AP_INVOICE_LINES_ALL.PO_DISTRIBUTION_ID = PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID
  • AP_INVOICE_DISTRIBUTIONS_ALLPO_DISTRIBUTIONS_ALLforeign key · N:1
    ON AP_INVOICE_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID = PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_ID

Browse more Procurement tables

More Procurement tables

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.