Search Results po_distributions_draft_pk

Overview

The PO_DISTRIBUTIONS_DRAFT_ALL table is a core transactional table within the Oracle E-Business Suite Purchasing (PO) module, specifically for releases 12.1.1 and 12.2.2. It functions as a staging or draft area for purchase order distribution data during the requisition and purchase order creation and modification processes. This table is integral to the draft functionality, which allows users to save incomplete work. It stores temporary distribution details—such as accounting, project, and inventory information—for purchase order lines before the final submission and approval that would populate the corresponding live table, PO_DISTRIBUTIONS_ALL. Its multi-org structure, indicated by the "_ALL" suffix, supports data across multiple operating units.

Key Information Stored

The table holds draft distribution records linked to a specific draft session and purchase order document. Key columns include DRAFT_ID, which ties all draft records for a session together, and PO_DISTRIBUTION_ID for unique identification. It references the parent document via PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID. Critical accounting columns are CODE_COMBINATION_ID for the charge account, and BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, and VARIANCE_ACCOUNT_ID for specific accounting purposes. For project and inventory tracking, it stores TASK_ID, DESTINATION_ORGANIZATION_ID, and DESTINATION_SUBINVENTORY. The table is governed by two primary keys: a system-generated primary key (PO_DISTRIBUTIONS_DRAFT_PK) and a unique key (PO_DISTRIBUTIONS_DRAFT_UK1) that enforces business rule uniqueness for a draft distribution number within a specific document line, shipment, and draft.

Common Use Cases and Queries

This table is primarily accessed for troubleshooting draft purchase orders and for reporting on in-progress procurement transactions. Common scenarios include identifying incomplete distributions stuck in a draft state or analyzing pending accounting charges. A typical query joins to the PO_DRAFTS table to find drafts by a specific user or creation date. For example:

• SELECT pdda.* FROM po_distributions_draft_all pdda, po_drafts pd WHERE pdda.draft_id = pd.draft_id AND pd.created_by = :user_id AND pd.status = 'INCOMPLETE';

Another frequent use case is comparing draft distributions against their finalized counterparts in PO_DISTRIBUTIONS_ALL to validate data before submission, often joining on PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID.

Related Objects

PO_DISTRIBUTIONS_DRAFT_ALL has extensive relationships with other EBS entities, as evidenced by its foreign keys. It is a child of the PO_DRAFTS table, which controls the draft lifecycle. Its primary parent transactional tables are PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL. For accounting integration, it references GL_CODE_COMBINATIONS multiple times and GL_SETS_OF_BOOKS_11I. For project and inventory integration, it links to PA_TASKS, MTL_SECONDARY_INVENTORIES, and BOM_RESOURCES. It also maintains relationships with PO_RELEASES_ALL for blanket agreements and PO_REQ_DISTRIBUTIONS_ALL for requisition sourcing. The corresponding live table is PO_DISTRIBUTIONS_ALL.