Search Results po_lines_pk

Overview

PO_LINES_ALL is the core transactional table in the Oracle Purchasing (PO) module of Oracle E-Business Suite, holding one row per line of every purchasing document: standard purchase orders, blanket and contract purchase agreements, quotations, and RFQs (requests for quotation). It is owned by the PO schema and resides in the PO product, and is one of the most heavily referenced tables in the entire EBS data model because virtually every downstream procurement, receiving, invoicing, projects, and manufacturing process traces back to a purchase order line.

Each row is keyed by the surrogate primary key PO_LINE_ID, and the table is partitioned logically by document through PO_HEADER_ID and ORG_ID (operating unit). The ETRM heuristic Data Vault classification for this object is hub, which suggests modeling PO_LINE_ID as a durable business key hub with associated descriptive satellites for the many attributes carried on the line.

Key Information Stored

The table contains 186 documented columns spanning document structure, pricing, quantities, sourcing, contract terms, and descriptive flexfields. The most operationally significant columns are:

• PO_LINE_ID — surrogate primary key (PO_LINES_PK) and the anchor for nearly all downstream foreign keys.
• PO_HEADER_ID — foreign key back to PO_HEADERS_ALL, tying the line to its parent document.
• LINE_NUM — the visible line number on the document; together with PO_HEADER_ID it forms the unique business key PO_LINES_U2.
• LINE_TYPE_ID — references PO_LINE_TYPES_B and determines how the line behaves (goods, services, fixed price, etc.).
• ITEM_ID and ITEM_REVISION — the inventory item and revision referenced on the line.
• ITEM_DESCRIPTION and CATEGORY_ID — line text and purchasing category (CATEGORY_ID references MTL_CATEGORIES_B).
• QUANTITY, UNIT_PRICE, UNIT_MEAS_LOOKUP_CODE, and AMOUNT — the ordered quantity, negotiated price, unit of measure, and extended amount.
• QUANTITY_COMMITTED and COMMITTED_AMOUNT — used for agreement and release tracking.
• FROM_HEADER_ID and FROM_LINE_ID — self-referencing or cross-referencing links showing the source document (e.g., a release referencing its blanket agreement).
• CLOSED_FLAG, CANCEL_FLAG, CLOSED_CODE, and USER_HOLD_FLAG — lifecycle status indicators.
• ORG_ID — the operating unit that owns the line, essential for multi-org security.
• CONTRACT_NUM, CONTRACT_ID, START_DATE, and EXPIRATION_DATE — agreement and contract control attributes.
• ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–20 — descriptive and global flexfield columns for customer extensions.
• TAXABLE_FLAG, TAX_NAME, and TAX_CODE_ID — taxability information carried from the header.

Common Use Cases and Queries

Typical reporting scenarios include open PO line analysis, price and quantity committed on agreements, spend analysis by category and supplier, and on-time / quantity variance tracking. A basic query to list open lines for a given operating unit might read:

SELECT pl.po_header_id, pl.line_num, pl.item_description,
       pl.quantity, pl.unit_price, pl.amount, pl.closed_code
FROM   po_lines_all pl
WHERE  pl.org_id = :org_id
AND    pl.closed_code <> 'FINALLY CLOSED'
AND    pl.cancel_flag = 'N';

Joining to PO_HEADERS_ALL supplies vendor and buyer context, while joining PO_LINE_LOCATIONS_ALL drills down to shipment and distribution detail. Sourcing and release analysis commonly uses the FROM_HEADER_ID / FROM_LINE_ID self-reference to connect a release line to the blanket agreement line that authorized it. Because ORG_ID governs multi-org access, list-of-values and reports should always filter on a valid operating unit.

Related Objects

PO_LINES_ALL sits at the center of a large dependency graph. The most significant related objects are:

• PO_HEADERS_ALL — joined on PO_HEADER_ID; the parent document header.
• PO_LINE_LOCATIONS_ALL — joined on PO_LINE_ID; shipments, distributions and receipt tolerances.
• PO_DISTRIBUTIONS_ALL — joined on PO_LINE_ID; accounting distributions for the line.
• RCV_SHIPMENT_LINES and RCV_TRANSACTIONS — joined on PO_LINE_ID; receiving and inspection activity.
• MTL_SUPPLY — joined on PO_LINE_ID; supply/demand planning records.
• PO_LINES_ALL (self) — joined on FROM_LINE_ID; source document linkage for releases and quotations.
• PO_LINE_TYPES_B and MTL_CATEGORIES_B — joined on LINE_TYPE_ID and CATEGORY_ID for classification and reporting.
• PA_TRANSACTION_INTERFACE_ALL and PA_EXPENDITURE_ITEMS_AR — joined on PO_LINE_ID; projects commitment and expenditure flows.
• PO_LINES_ARCHIVE_ALL — joined on PO_LINE_ID and FROM_LINE_ID; archival history.
• PO_AUTOSOURCE_DOCUMENTS_ALL — joined on DOCUMENT_LINE_ID; autosource and sourcing rules.

In addition to direct table joins, the line data is surfaced through the standard Purchasing application programming interfaces and public views such as PO_LINES_VIEW and the PO_LINES_ALL_V variant, which apply operating unit security and may omit sensitive columns.