Results for “po_line_locations_draft_all”

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

Overview

PO_LINE_LOCATIONS_DRAFT_ALL is a draft (staging) table in the Oracle Purchasing (PO) module that holds uncommitted, in-progress versions of purchase order shipment and distribution records. It is the draft counterpart of PO_LINE_LOCATIONS_ALL, which stores the approved, transactional shipment lines that drive receiving, invoicing, and encumbrance activity. When a buyer creates or modifies a purchase order through the Draft-enabled Purchasing UI in Oracle E-Business Suite 12.1.1 or 12.2.2, changes are initially written to the draft tables rather than directly to the base purchasing tables. The draft is associated with a record in PO_DRAFTS and is only promoted into PO_LINE_LOCATIONS_ALL when the document is submitted, approved, or otherwise committed.

The table is owned by the PO schema and contains 182 documented columns. Because it is a draft-layer object, its role is intermediate and transient: it supports the modern PO approval workflow, document versioning, and change-tracking that were introduced with the Draft feature in Release 12. From a Data Vault modeling perspective, the metadata's heuristic classification is link, suggesting this table is best modeled as a relationship/association entity connecting draft headers, lines, shipments, and their source transaction references. This classification is a modeling suggestion only and should be validated against the access patterns of the consuming data mart.

Key Information Stored

The primary key of the table is PO_LINE_LOCATIONS_DRAFT_PK, composed of LINE_LOCATION_ID and DRAFT_ID. A second unique index, PO_LINE_LOCATIONS_DRAFT_U1, covers the same column pair (LINE_LOCATION_ID, DRAFT_ID) and is the documented business-key candidate. The third unique index, PO_LINE_LOCATIONS_DRAFT_UK1, spans DRAFT_ID, PO_LINE_ID, and SHIPMENT_NUM, enforcing that a shipment number is unique per draft line.

The most significant columns include:

• DRAFT_ID — foreign key to PO_DRAFTS; identifies the draft batch to which the shipment belongs.
• LINE_LOCATION_ID — the shipment identifier; part of the primary key and unique key.
• PO_HEADER_ID and PO_LINE_ID — foreign keys to PO_HEADERS_ALL and PO_LINES_ALL, anchoring the shipment in the document hierarchy.
• SHIPMENT_NUM — the sequential shipment number on the line.
• QUANTITY, QUANTITY_ACCEPTED, QUANTITY_RECEIVED, QUANTITY_BILLED, QUANTITY_CANCELLED — the core quantity lifecycle columns mirrored from the base table.
• SHIP_TO_LOCATION_ID — foreign key to HR_LOCATIONS_ALL, defining the delivery destination.
• NEED_BY_DATE and PROMISED_DATE — scheduling dates used in planning and expediting reports.
• FROM_HEADER_ID, FROM_LINE_ID, FROM_LINE_LOCATION_ID — source references supporting copy, change-order, and re-sourcing scenarios.
• SOURCE_SHIPMENT_ID — foreign key back to PO_LINE_LOCATIONS_ALL, linking the draft to the original committed shipment.
• PO_RELEASE_ID — foreign key to PO_RELEASES_ALL for release-linked shipments.
• TAX_CODE_ID — foreign key to AP_TAX_CODES_ALL; TAX_NAME and CALCULATE_TAX_FLAG carry related tax attributes.
• SHIP_TO_ORGANIZATION_ID, ORG_ID — the destination and owning operating unit.
• APPROVED_FLAG, CANCEL_FLAG, CLOSED_FLAG, DELETE_FLAG, CHANGE_STATUS — status and workflow control flags.
• BID_PAYMENT_ID — foreign key to PON_BID_PAYMENTS_SHIPMENTS, relevant to sourcing and bid payment flows.

Common Use Cases and Queries

The principal use case is inspecting pending or unapproved shipments before they become permanent. A typical query joins the draft shipment to the draft header and line to display in-progress documents:

• Pending drafts per buyer: SELECT d.DRAFT_ID, l.PO_HEADER_ID, l.PO_LINE_ID, l.SHIPMENT_NUM, l.QUANTITY FROM PO_LINE_LOCATIONS_DRAFT_ALL l JOIN PO_DRAFTS d ON d.DRAFT_ID = l.DRAFT_ID WHERE l.DELETE_FLAG = 'N';
• Comparing draft versus committed quantities by joining SOURCE_SHIPMENT_ID to PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID.
• Identifying drafts that reference tax codes, releases, or source shipments via PO_RELEASE_ID, TAX_CODE_ID, and SOURCE_SHIPMENT_ID.
• Reconciliation and audit reporting: draft rows that were staged but never promoted into PO_LINE_LOCATIONS_ALL indicate rejected or abandoned change requests.
• Custom reporting on change activity using CHANGE_STATUS, CHANGE_ACCEPTED_FLAG, and REVISION_NUM.

Because draft rows are transient, queries should always filter on DRAFT_ID or join to PO_DRAFTS to avoid scanning stale or orphaned records.

Related Objects

The table participates in a dense network of foreign-key relationships, the most significant of which are:

• PO_DRAFTS — joined on DRAFT_ID; governs the draft lifecycle.
• PO_LINE_LOCATIONS_ALL — the committed base table; linked via SOURCE_SHIPMENT_ID and FROM_LINE_LOCATION_ID.
• PO_LINES_ALL — linked via PO_LINE_ID and FROM_LINE_ID.
• PO_HEADERS_ALL — linked via PO_HEADER_ID and FROM_HEADER_ID.
• PO_RELEASES_ALL — linked via PO_RELEASE_ID.
• HR_LOCATIONS_ALL — linked via SHIP_TO_LOCATION_ID.
• AP_TAX_CODES_ALL — linked via TAX_CODE_ID.
• PON_BID_PAYMENTS_SHIPMENTS — linked via BID_PAYMENT_ID.

These relationships confirm that PO_LINE_LOCATIONS_DRAFT_ALL functions as the anchor point between draft workflow records and the master purchasing, tax, and location entities in the E-Business Suite data model.