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
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.

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.PrcExtractAM.PoBiccExtractAM.PurchasingDocumentDistributionExtractPVO
    OTBI: Procurement - Purchasing Real Time

    Purchasing Document Distributions data store — keyed on PoDistributionId.

    Oracle data-store documentation →

Fields

17 fields · 1 key

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_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  : 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 partition column 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;

4 parameters not filled: <catalog>, <schema>, <PO_DISTRIBUTION_ID>, <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

  • 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

Browse more Procurementtables →

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.