Search Results po_lines_u2

Overview

PO.PO_LINES_ALL is the core transactional table in the Oracle Purchasing (PO) schema that stores current information about every line attached to a purchasing document. In Oracle EBS 12.1.1 and 12.2.2, one row exists for each line on an RFQ, quotation, standard purchase order, blanket purchase order, or planned purchase order. Each row captures the line number, item and category, unit of measure, price, tax details, matching attributes, and ordered quantity. Oracle Purchasing uses this information to record and update item and price data across the procurement lifecycle. The table is owned by the PO schema, carries FND Design Data registration as PO.PO_LINES_ALL, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. From a modeling perspective, the mined Data Vault classification places this table as a hub, reflecting its role as the system of record for purchase order line identity. Its primary key is PO_LINES_PK on PO_LINE_ID, and the documented physical schema contains 186 columns.

Key Information Stored

The most significant columns include:

• PO_LINE_ID — the system-generated surrogate primary key, unique and invisible to the user.
• PO_HEADER_ID — foreign key linking the line to its parent document in PO_HEADERS_ALL.
• LINE_NUM — the user-visible line number on the purchase order. Together with PO_HEADER_ID it forms the second unique business-key candidate, PO_LINES_U2 (PO_HEADER_ID, LINE_NUM).
• LINE_TYPE_ID — references PO_LINE_TYPES_B, distinguishing goods versus services and other classifications.
• ITEM_ID and CATEGORY_ID — the inventory item and purchasing category for the line.
• ITEM_DESCRIPTION — free-text description, indexed by the function-based index PO_LINES_F1 on UPPER("ITEM_DESCRIPTION").
• UNIT_PRICE, LIST_PRICE_PER_UNIT, and NOT_TO_EXCEED_PRICE — pricing attributes.
• QUANTITY — the total quantity across all shipment lines held in PO_LINE_LOCATIONS_ALL.
• QUANTITY_COMMITTED, COMMITTED_AMOUNT, ALLOW_PRICE_OVERRIDE_FLAG, and MIN_RELEASE_AMOUNT — used specifically for blanket and planned purchase order lines.
• CONTRACT_ID and FROM_HEADER_ID/FROM_LINE_ID — reference a contract purchase order and the source document from which the line was copied.
• ORG_ID — operating unit identifier supporting multi-org security.
• CANCEL_FLAG, CLOSED_FLAG, USER_HOLD_FLAG, and UNORDERED_FLAG — status flags governing line behavior.

The distinction between PO_LINE_ID (surrogate key) and LINE_NUM (business identifier) is central to correct querying. The table also carries a standardized ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–20 descriptor flexfield set, plus CLM_* columns supporting contract terms and award management.

Common Use Cases and Queries

Typical reporting scenarios include listing all lines for a given purchase order, joining lines to shipments, and reconciling receipts against ordered quantities. A representative query retrieves lines for a header:

• SELECT l.po_line_id, l.line_num, l.item_description, l.quantity, l.unit_price FROM po_po_lines_all l WHERE l.po_header_id = :header_id ORDER BY l.line_num;
• Joining to PO_LINE_LOCATIONS_ALL via PO_LINE_ID to obtain shipment schedules and receipt tolerances.
• Joining to PO_DISTRIBUTIONS_ALL via PO_LINE_ID for accounting distribution analysis.
• Querying by CONTRACT_ID to review blanket agreement lines or by FROM_LINE_ID to trace copied or referenced lines.
• Utilizing PO_LINES_N10 (LAST_UPDATE_DATE) or PO_LINES_N2 (CREATION_DATE) for incremental data extraction and interface processing.

Related Objects

The table participates in an extensive foreign-key web:

• PO_HEADERS_ALL — parent document, joined via PO_HEADER_ID.
• PO_LINE_LOCATIONS_ALL — shipment schedules, joined via PO_LINE_ID; the sum of these quantities populates PO_LINES_ALL.QUANTITY.
• PO_DISTRIBUTIONS_ALL — accounting distributions, joined via PO_LINE_ID.
• RCV_SHIPMENT_LINES and RCV_TRANSACTIONS — receiving activity referencing PO_LINE_ID.
• MTL_SUPPLY — supply/demand records referencing PO_LINE_ID for planning.
• PO_LINES_ARCHIVE_ALL — archival counterpart, linked via PO_LINE_ID and FROM_LINE_ID.
• PO_LINE_TYPES_B, MTL_CATEGORIES_B, and PO_HAZARD_CLASSES_B — reference/lookup tables resolving LINE_TYPE_ID, CATEGORY_ID, and HAZARD_CLASS_ID.
• PO_REQEXPRESS_LINES_ALL and PO_ACCRUAL_WRITE_OFFS_ALL — dependent purchasing objects joined via PO_LINE_ID.
• OE_DROP_SHIP_SOURCES and SO_DROP_SHIP_SOURCES — order management integrations referencing PO_LINE_ID.

These relationships confirm PO_LINES_ALL as a central hub within the procurement and supply-chain data model.