PO_DISTRIBUTIONS_ALL
Schema: POtransactionOU-striped (ORG_ID)PO accounting distributions — how each shipment schedule's quantity charges out: destination type, receiving inventory org and subinventory, charge account (CCID), and the requisition distribution it fulfills
Accounting grain — a shipment can split across several distributions, so joining lines to distributions multiplies quantities
CODE_COMBINATION_ID is the charge account and joins the GL code combinations table; DESTINATION_ORGANIZATION_ID is an inventory org.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
16 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PO_DISTRIBUTION_ID | Surrogate key of the distribution | NUMBER | Key |
| 2 | LINE_LOCATION_ID | The shipment schedule being distributed — a shipment can split across distributions | NUMBER | |
| 3 | PO_LINE_ID | The document line (denormalized) | NUMBER | |
| 4 | PO_HEADER_ID | The document header (denormalized) | NUMBER | |
| 5 | ORG_ID | Operating unit | NUMBER | |
| 6 | DISTRIBUTION_NUM | Distribution number within the shipment | NUMBER | |
| 7 | DESTINATION_TYPE_CODE | Where the goods charge to — inventory, expense, or shop floor | VARCHAR2 | |
| 8 | DESTINATION_ORGANIZATION_ID | The receiving inventory org for the distribution | NUMBER | |
| 9 | DESTINATION_SUBINVENTORY | Default putaway subinventory | VARCHAR2 | |
| 10 | CODE_COMBINATION_ID | The charge account (CCID) — the P2P tie to the general ledger | NUMBER | |
| 11 | ACCRUAL_ACCOUNT_ID | The accrual account (CCID) | NUMBER | |
| 12 | QUANTITY_ORDERED | Quantity on the distribution | NUMBER | |
| 13 | QUANTITY_DELIVERED | Running total delivered against the distribution | NUMBER | |
| 14 | QUANTITY_BILLED | Running total billed against the distribution | NUMBER | |
| 15 | REQ_DISTRIBUTION_ID | The requisition distribution this fulfills — the req-to-PO accounting thread | NUMBER | |
| 16 | WIP_ENTITY_ID | The WIP job an outside-processing distribution charges — the P2P tie to the shop floor | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading PO_DISTRIBUTIONS_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : PO_DISTRIBUTIONS_ALL — PO accounting distributions — how each shipment schedule's quantity charges out: destination type, receiving inventory org and subinventory, charge account (CCID), and the requisition distribution it fulfills
-- Purpose: Column-selected read of PO_DISTRIBUTIONS_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + PO_DISTRIBUTION_ID
-- Caution: Accounting grain — a shipment can split across several distributions, so joining lines to distributions multiplies quantities
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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 "The shipment schedule being distributed — a shipment can split across distributions",
t.PO_LINE_ID AS "The document line (denormalized)",
t.PO_HEADER_ID AS "The document header (denormalized)",
t.ORG_ID AS "Operating unit",
t.DISTRIBUTION_NUM AS "Distribution number within the shipment",
t.DESTINATION_TYPE_CODE AS "Where the goods charge to — inventory, expense, or shop floor",
t.DESTINATION_ORGANIZATION_ID AS "The receiving inventory org for the distribution",
t.DESTINATION_SUBINVENTORY AS "Default putaway subinventory",
t.CODE_COMBINATION_ID AS "The charge account (CCID) — the P2P tie to the general ledger",
t.ACCRUAL_ACCOUNT_ID AS "The accrual account (CCID)",
t.QUANTITY_ORDERED AS "Quantity on the distribution",
t.QUANTITY_DELIVERED AS "Running total delivered against the distribution",
t.QUANTITY_BILLED AS "Running total billed against the distribution",
t.REQ_DISTRIBUTION_ID AS "The requisition distribution this fulfills — the req-to-PO accounting thread",
t.WIP_ENTITY_ID AS "The WIP job an outside-processing distribution charges — the P2P tie to the shop floor"
FROM <catalog>.<schema>.PO_DISTRIBUTIONS_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.PO_DISTRIBUTION_ID = <PO_DISTRIBUTION_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.PO_DISTRIBUTION_ID;5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <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
ON PO_DISTRIBUTIONS_ALL.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID AND PO_DISTRIBUTIONS_ALL.ORG_ID = PO_LINE_LOCATIONS_ALL.ORG_IDON PO_DISTRIBUTIONS_ALL.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON RCV_TRANSACTIONS.PO_DISTRIBUTION_ID = PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_IDON PO_DISTRIBUTIONS_ALL.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_ID