Search Results PO_LINES_ALL




Overview
Explore in AI Chat

Overview

The PO_LINES_ALL table is a core transactional entity within the Oracle E-Business Suite Purchasing (PO) module, specifically in releases 12.1.1 and 12.2.2. It serves as the master repository for all line-level information across various purchasing documents. As indicated by its description, it stores data for lines belonging to purchase orders, purchase agreements (blanket and contract), quotations, and requests for quotation (RFQs). The table's "ALL" suffix signifies it is a multi-organization table, containing data for all operating units accessible to a user based on their security profile. Each record is uniquely identified by PO_LINE_ID and is logically grouped under a specific document header via PO_HEADER_ID, with LINE_NUM defining its sequence within that document.

Key Information Stored

The table's structure captures the essential attributes of a procurement line item. While the provided metadata highlights key relationships, the critical columns typically include PO_LINE_ID (primary key), PO_HEADER_ID (link to PO_HEADERS_ALL), and LINE_NUM (forming a unique key with the header ID). Other significant foreign keys define item and transactional characteristics: CATEGORY_ID links to MTL_CATEGORIES_B for item categorization, LINE_TYPE_ID to PO_LINE_TYPES_B to define the line's purpose (e.g., Goods, Services, Freight), and FROM_HEADER_ID/FROM_LINE_ID support document copying and sourcing from other purchase documents. The table also holds columns for item description, quantity, unit of measure, price, and need-by date, forming the complete business definition of the requested good or service.

Common Use Cases and Queries

This table is central to procurement reporting, data validation, and integration workflows. Common use cases include generating detailed purchase order line reports, analyzing item or category spending, and tracing the sourcing lineage of a line item. A fundamental query to retrieve all lines for a specific purchase order header would join PO_HEADERS_ALL with PO_LINES_ALL on PO_HEADER_ID. For performance and compliance reporting, analysts often join with MTL_CATEGORIES_B via CATEGORY_ID and PO_LINE_TYPES_B via LINE_TYPE_ID. Another critical pattern involves using the FROM_HEADER_ID and FROM_LINE_ID to trace a line back to its source quotation or blanket agreement, supporting audit trails. Data fixes or updates to line attributes, though typically performed via standard APIs, may require direct queries against this table for analysis.

Related Objects

PO_LINES_ALL has extensive relationships within and beyond the Purchasing module, as evidenced by its foreign key constraints. Its primary parent is PO_HEADERS_ALL. Key child tables include PO_LINE_LOCATIONS_ALL (for shipment and receipt details) and PO_DISTRIBUTIONS_ALL (for accounting distributions). The metadata also shows crucial relationships with inventory (MTL_CATEGORIES_B), receiving (CST_RCV_ACQ_COST_DETAILS), and external systems like iProcurement (ICX_SHOPPING_CART_LINES). Furthermore, it is referenced by numerous country-specific extensions (tables prefixed with JAI_), highlighting its importance for localized tax and regulatory compliance. For programmatic interaction, developers should utilize the standard PO_PDOI and POXPOEPO APIs rather than direct DML on this table.