Results for “po_lines_draft_u1”

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

Overview

PO.PO_LINES_DRAFT_ALL is a transactional table in the Oracle Purchasing (PO) schema that stores draft or proposed changes to purchase order lines prior to buyer acceptance. Each row represents a proposed version of a corresponding record in the transaction table PO_LINES_ALL. Changes originating from the buyer are accepted automatically and never persist here, whereas changes proposed by suppliers or other external parties, such as through Oracle Sourcing or supplier portal flows, are held in this table until the buyer accepts or rejects them. Upon acceptance, the draft record's values are moved into PO_LINES_ALL. The table inherits its full 198-column structure from PO_LINES_ALL and adds draft-specific control columns. It resides in the APPS_TS_TX_DATA tablespace with PCT Free 10 and is defined in both Oracle EBS 12.1.1 and 12.2.2.

The ETRM metadata classifies this object heuristically as a link in Data Vault terms, reflecting its role as an associative structure joining draft identifiers (via DRAFT_ID and PO_DRAFTS) to underlying PO line entities (via PO_LINE_ID and PO_LINES_ALL). This classification is a modeling suggestion rather than a functional designation; operationally, the table behaves as a staging or pending-changes satellite to PO_LINES_ALL.

Key Information Stored

The table's surrogate primary key is defined by PO_LINES_DRAFT_PK, composed of PO_LINE_ID and DRAFT_ID. The unique index PO_LINES_DRAFT_U1 covers these same two columns (PO_LINE_ID, DRAFT_ID), making them the documented business-key candidate and the object referenced directly in the user's search. PO_LINE_ID links each draft row to the underlying line in PO_LINES_ALL, while DRAFT_ID identifies the parent draft batch and references PO_DRAFTS.

The most operationally significant columns include:

• PO_LINE_ID and DRAFT_ID — composite identifier tying a draft line to its draft and its transaction-line counterpart.
• CHANGE_ACCEPTED_FLAG — indicates whether the draft change has been accepted, governing the move into PO_LINES_ALL.
• DELETE_FLAG — signals that the corresponding PO_LINES_ALL record should be deleted when the draft is accepted.
• PO_HEADER_ID and LINE_NUM — parent header reference and line sequence, used in joins to PO_HEADERS_ALL.
• ITEM_ID, ITEM_DESCRIPTION, CATEGORY_ID, QUANTITY, UNIT_PRICE, UNIT_MEAS_LOOKUP_CODE — proposed item, pricing, and quantity values.
• DRAFT_LINE_STATUS and CHANGE_STATUS — status indicators for the draft workflow, unique to the draft context.
• MOD_DRAFT_ID, MOD_LINE_ID, OLD_QUANTITY, OLD_AMOUNT, OLD_UNIT_PRICE, OLD_UOM_LOOKUP_CODE — modification tracking fields preserving prior values for comparison.
• FROM_HEADER_ID and FROM_LINE_ID — references to source documents when the line is derived from another PO or agreement.

Common Use Cases and Queries

Typical uses center on retrieving pending supplier-proposed line changes, auditing draft-versus-accepted values, and monitoring drafts awaiting buyer action. A representative query retrieves all pending changes for a draft:

SELECT d.PO_LINE_ID, d.LINE_NUM, d.ITEM_DESCRIPTION, d.QUANTITY, d.OLD_QUANTITY, d.UNIT_PRICE, d.OLD_UNIT_PRICE, d.CHANGE_ACCEPTED_FLAG, d.DELETE_FLAG
FROM PO.PO_LINES_DRAFT_ALL d
WHERE d.DRAFT_ID = :draft_id
AND NVL(d.CHANGE_ACCEPTED_FLAG,'N') = 'N';

To reconcile draft lines against their transaction counterparts, analysts join on PO_LINE_ID. Reporting use cases include identifying lines flagged for deletion, tracking modification history through MOD_DRAFT_ID, and validating that proposed quantities and prices fall within tolerances before acceptance. Because PO_LINES_DRAFT_ALL shares all columns with PO_LINES_ALL, existing PO line reports can be redirected to this table to render a preview of pending changes.

Related Objects

The following objects are most significant to this table, drawn from documented foreign keys and key relationships:

• PO.PO_LINES_ALL — transaction table holding accepted lines; joined via FROM_LINE_ID and linked by PO_LINE_ID to the draft row.
• PO.PO_HEADERS_ALL — header table; joined via FROM_HEADER_ID (and PO_HEADER_ID at the header level).
• PO.PO_DRAFTS — parent draft; DRAFT_ID is a foreign key to this table.
• PO.PO_LINE_TYPES_B — line type reference via LINE_TYPE_ID.
• MTL_CATEGORIES_B — item category reference via CATEGORY_ID.
• PO.PO_UN_NUMBERS_B and PO.PO_HAZARD_CLASSES_B — regulatory references via UN_NUMBER_ID and HAZARD_CLASS_ID.
• PON_AUCTION_HEADERS_ALL — sourcing auction reference via AUCTION_HEADER_ID.

The unique index PO_LINES_DRAFT_U1 (PO_LINE_ID, DRAFT_ID) supports direct lookup of a single draft line and is the access path most commonly used by the Purchasing and Sourcing application forms.