Results for “po_distributions_draft_all”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_DISTRIBUTIONS_DRAFT_ALL is the draft (uncommitted) staging table for purchase order distributions in Oracle Purchasing (PO). It resides in the PO schema and mirrors the structure and behavior of PO_DISTRIBUTIONS_ALL, but its rows are associated with a change draft (identified by DRAFT_ID) rather than a live, approved purchase order. When a user modifies distribution-level attributes of an existing purchase order—such as accounting flexfields, quantities, delivery destinations, or project and task references—Oracle Purchasing can capture those changes as draft rows before they are validated and applied to the base tables. The table is therefore best understood as the "change capture" layer for PO distribution data, working in tandem with the PO_DRAFTS mechanism used across the purchasing document model.

Its role is transactional and workflow-oriented: it holds proposals, not commitments. A distribution draft is only promoted to the operational PO_DISTRIBUTIONS_ALL table when the governing draft is accepted and applied. Consequently, reporting that requires committed purchasing activity should read PO_DISTRIBUTIONS_ALL, while change-tracking, audit, and approval-cycle analysis should read this table.

Using Data Vault modeling heuristics derived from the foreign-key topology, this object classifies as a link table: it resolves relationships among drafts, purchase order headers, lines, line locations, releases, requisition distributions, accounting flexfields, inventory destinations, projects and tasks, and awards, while carrying descriptive measures as link-attached attributes.

Key Information Stored

The surrogate primary key is defined by PO_DISTRIBUTIONS_DRAFT_PK, composed of PO_DISTRIBUTION_ID and DRAFT_ID. A parallel unique index, PO_DISTRIBUTIONS_DRAFT_U1 (PO_DISTRIBUTION_ID, DRAFT_ID), serves as the business-key candidate, and a second unique key, PO_DISTRIBUTIONS_DRAFT_UK1, spans PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, DISTRIBUTION_NUM, and DRAFT_ID. Among the 132 documented columns, the most operationally significant are:

Common Use Cases and Queries

Typical uses include auditing pending changes to purchase order distributions, diagnosing why an approved draft has not reapplied to PO_DISTRIBUTIONS_ALL, extracting change history for SOX or internal-control reporting, and validating accounting flexfield or project references before commit.

A representative query listing pending distributions for a specific draft:

  • SELECT pd.po_distribution_id, pd.po_header_id, pd.po_line_id, pd.line_location_id, pd.distribution_num, pd.quantity_ordered, pd.amount_ordered FROM po.po_distributions_draft_all pd WHERE pd.draft_id = :draft_id AND pd.delete_flag = 'N';
  • Change-scope audit counting distributions per draft: SELECT draft_id, COUNT(*) FROM po.po_distributions_draft_all WHERE change_accepted_flag = 'Y' GROUP BY draft_id;
  • Reconciliation against the committed table, joining on PO_DISTRIBUTION_ID: SELECT d.po_distribution_id, d.quantity_ordered draft_qty, a.quantity_ordered base_qty FROM po.po_distributions_draft_all d, po.po_distributions_all a WHERE d.po_distribution_id = a.po_distribution_id AND d.draft_id = :draft_id;

Dashboards commonly group by DESTINATION_ORGANIZATION_ID or CODE_COMBINATION_ID to show the accounting impact of in-flight changes, and multi-org reports must always filter on ORG_ID.

Related Objects

The most significant related objects, with their documented join columns, are:

  • PO_DRAFTS on DRAFT_ID — parent draft record; defines the change set.
  • PO_HEADERS_ALL on PO_HEADER_ID — the purchase order header.
  • PO_LINES_ALL on PO_LINE_ID — the purchase order line.
  • PO_LINE_LOCATIONS_ALL on LINE_LOCATION_ID — the shipment or line location.
  • PO_RELEASES_ALL on PO_RELEASE_ID — releases against blanket agreements.
  • PO_REQ_DISTRIBUTIONS_ALL on REQ_DISTRIBUTION_ID — originating requisition distribution.
  • GL_CODE_COMBINATIONS on CODE_COMBINATION_ID, BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, and VARIANCE_ACCOUNT_ID — accounting flexfield validation.
  • GL_SETS_OF_BOOKS_11I on SET_OF_BOOKS_ID — ledger definition for encumbrance context.
  • MTL_SECONDARY_INVENTORIES on DESTINATION_ORGANIZATION_ID and DESTINATION_SUBINVENTORY — inventory destination.
  • PA_TASKS on TASK_ID — project task reference; plus BOM_RESOURCES on BOM_RESOURCE_ID and IGF_AW_AWARD_ALL on AWARD_ID for WIP and grants integration.