Search Results po_line_locations_draft_all




Overview
Explore in AI Chat

Overview

The PO_LINE_LOCATIONS_DRAFT_ALL table is a core transactional staging table within the Oracle E-Business Suite Purchasing (PO) module, specifically for releases 12.1.1 and 12.2.2. As a draft table, its primary role is to temporarily hold proposed changes to purchase order shipment schedules during the requisition-to-purchase order conversion process or the amendment of existing purchase orders. It acts as a working copy of the PO_LINE_LOCATIONS_ALL table, allowing users to prepare and review modifications before they are finalized and committed to the primary transactional tables. This draft mechanism is essential for supporting complex procurement workflows, ensuring data integrity, and preventing incomplete or erroneous updates from affecting live purchasing documents.

Key Information Stored

The table stores draft versions of shipment schedule lines, which detail delivery quantities, dates, and locations for specific purchase order lines. Its structure is defined by a composite primary key consisting of LINE_LOCATION_ID and DRAFT_ID. The DRAFT_ID column is a critical foreign key linking each draft record to a master draft header in the PO_DRAFTS table. Other significant foreign keys include PO_LINE_ID (linking to the draft purchase order line in PO_LINES_DRAFT_ALL), PO_HEADER_ID, and SHIP_TO_LOCATION_ID. The table also contains columns to manage the relationship with the source transactional data, such as FROM_LINE_LOCATION_ID and SOURCE_SHIPMENT_ID, which reference the original shipment in PO_LINE_LOCATIONS_ALL that is being modified. Additional columns would typically store shipment quantities, promised and expected delivery dates, prices, and tax information (via TAX_CODE_ID).

Common Use Cases and Queries

The primary use case involves querying draft shipments for a specific purchase order amendment or requisition conversion batch. A common reporting need is to identify all pending draft shipment changes associated with a particular draft document or user. Sample SQL to retrieve this information would join to the PO_DRAFTS and PO_HEADERS_DRAFT_ALL tables.

  • Find Draft Shipments for a Specific Draft: SELECT * FROM po_line_locations_draft_all plld WHERE plld.draft_id = :draft_id ORDER BY shipment_num;
  • Compare Draft vs. Approved Shipments: Queries often join PO_LINE_LOCATIONS_DRAFT_ALL with PO_LINE_LOCATIONS_ALL on the FROM_LINE_LOCATION_ID to highlight differences in quantity, date, or price before final submission.
  • Data Validation: Scripts may check for data consistency within a draft, such as ensuring the sum of draft shipment quantities does not exceed the related draft line quantity.

Related Objects

This table is centrally connected to several key Purchasing tables. It is a direct child of the PO_DRAFTS table, which controls the draft lifecycle. Its data is sourced from and intended to update the PO_LINE_LOCATIONS_ALL table. It maintains relationships with draft header and line tables (PO_HEADERS_DRAFT_ALL, PO_LINES_DRAFT_ALL) and references master data tables like HR_LOCATIONS_ALL for ship-to addresses and AP_TAX_CODES_ALL for tax details. For blanket purchase agreements, it links to PO_RELEASES_ALL. The existence of a unique key (DRAFT_ID, PO_LINE_ID, SHIPMENT_NUM) ensures shipment numbering remains consistent within the context of a draft line.