Search Results po_lines_draft_all

Overview

The PO_LINES_DRAFT_ALL table is a core transactional object within the Oracle E-Business Suite Purchasing (PO) module, specifically for versions 12.1.1 and 12.2.2. It functions as a draft or staging table for purchase document line data during the creation and modification process. This table temporarily holds line-level information for purchase orders, purchase agreements, quotations, and requests for quotation (RFQs) before the data is finalized and committed to the corresponding base transaction table, PO_LINES_ALL. Its primary role is to support the draft capabilities of the Purchasing document interface, allowing users to save incomplete work and manage concurrent edits without impacting live transactional data.

Key Information Stored

The table stores a comprehensive set of attributes for a draft purchase line. Each record is uniquely identified by the composite primary key on PO_LINE_ID and DRAFT_ID. The DRAFT_ID column is critical, linking the line to its associated draft header in PO_HEADERS_DRAFT_ALL. Other essential columns include PO_HEADER_ID and LINE_NUM, which together with DRAFT_ID form a unique key (PO_LINES_DRAFT_UK1) to maintain line numbering within a draft document. Key data points stored encompass item details (ITEM_ID, ITEM_REVISION, UNIT_MEAS_LOOKUP_CODE), quantities (QUANTITY, QUANTITY_CANCELLED), pricing (UNIT_PRICE), and descriptive information (ITEM_DESCRIPTION). The table also includes referential columns like CATEGORY_ID, LINE_TYPE_ID, and sourcing references (FROM_HEADER_ID, FROM_LINE_ID) to copy from existing documents.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting draft purchasing documents. For instance, identifying all draft lines for a specific draft document or user session. A common reporting need is to analyze pending changes before final submission.

• Finding all draft lines for a specific draft identifier: SELECT * FROM PO_LINES_DRAFT_ALL WHERE DRAFT_ID = :draft_id ORDER BY LINE_NUM;
• Comparing draft lines against their source lines from an existing document: SELECT d.line_num, d.quantity AS draft_qty, l.quantity AS committed_qty FROM po_lines_draft_all d, po_lines_all l WHERE d.from_line_id = l.po_line_id AND d.draft_id = :draft_id;
• Identifying incomplete draft lines missing critical data before submission: SELECT draft_id, po_line_id, line_num FROM po_lines_draft_all WHERE item_id IS NULL AND category_id IS NULL;

Related Objects

PO_LINES_DRAFT_ALL has integral relationships with several key Purchasing tables, as documented by its foreign key constraints.

• PO_HEADERS_DRAFT_ALL: The parent draft header table, linked via PO_HEADER_ID and DRAFT_ID.
• PO_LINES_ALL: The base transaction table; linked via FROM_LINE_ID for copied lines.
• PO_HEADERS_ALL: The base header table; linked via FROM_HEADER_ID for copied documents.
• MTL_CATEGORIES_B: For item category validation (CATEGORY_ID).
• PO_LINE_TYPES_B: For line type validation (LINE_TYPE_ID).
• PO_UN_NUMBERS_B & PO_HAZARD_CLASSES_B: For regulatory and safety data on shipped items (UN_NUMBER_ID, HAZARD_CLASS_ID).