Search Results PO_LINE_LOCATIONS_ALL




Overview
Explore in AI Chat

Overview

The PO_LINE_LOCATIONS_ALL table is a core transactional entity within Oracle E-Business Suite Purchasing (PO) module, applicable to versions 12.1.1 and 12.2.2. It serves as the primary repository for shipment schedule information, also known as distributions or shipments, associated with purchasing documents. As indicated by its description, it documents shipment schedules for purchase orders, purchase agreements, quotations, and requests for quotation (RFQs). Each record represents a distinct delivery schedule for a specific quantity of an item or service on a purchase order line, enabling detailed control over delivery dates, quantities, locations, and receiving instructions. Its role is critical for the procure-to-pay cycle, linking purchasing documents to receiving and accounts payable processes.

Key Information Stored

The table stores detailed attributes for each shipment schedule. Its primary key is the unique identifier LINE_LOCATION_ID. A unique key constraint on PO_LINE_ID and SHIPMENT_NUM ensures each shipment number is unique per purchase order line. Key foreign key columns define its relationships within the purchasing schema: PO_HEADER_ID and PO_LINE_ID link to the parent document header and line (PO_HEADERS_ALL and PO_LINES_ALL). SHIP_TO_LOCATION_ID references HR_LOCATIONS_ALL to specify the delivery destination. RECEIVING_ROUTING_ID links to RCV_ROUTING_HEADERS to define the inspection and receiving workflow. TAX_CODE_ID references AP_TAX_CODES_ALL for tax calculations. Additional columns track quantities (QUANTITY, QUANTITY_RECEIVED, QUANTITY_BILLED), dates (PROMISED_DATE, NEED_BY_DATE), prices (UNIT_PRICE), and flags for closed, canceled, or approved statuses, providing a complete audit trail for each scheduled delivery.

Common Use Cases and Queries

This table is central to operational reporting and process integration. Common use cases include generating delivery schedules for suppliers, reconciling received quantities against ordered quantities, and matching invoices to specific shipments. A typical query retrieves all open shipments for a purchase order to track delivery performance:

  • SELECT pll.shipment_num, pll.quantity, pll.quantity_received, pll.promised_date FROM po_line_locations_all pll JOIN po_lines_all pl ON pll.po_line_id = pl.po_line_id WHERE pl.po_header_id = <header_id> AND pll.closed_code IS NULL;

Another frequent pattern involves joining with PO_HEADERS_ALL and PO_LINES_ALL to create comprehensive purchase order detail reports that break down totals by shipment. Integration points include creating receipts in the RCV_SHIPMENT_LINES table based on these schedules and providing the PO_LINE_LOCATION_ID for invoice matching in AP_INVOICE_LINES_ALL.

Related Objects

PO_LINE_LOCATIONS_ALL has extensive relationships within and beyond the Purchasing module. Its primary parent tables are PO_HEADERS_ALL and PO_LINES_ALL. It also self-references via FROM_LINE_LOCATION_ID and SOURCE_SHIPMENT_ID for document copying and blanket agreement releases. Crucially, it is referenced by key transactional tables in other modules, establishing its central role. As per the metadata, AP_INVOICE_LINES_ALL references it for invoice matching, and AP_HOLDS_ALL can place holds on specific shipments. Within receiving, tables like RCV_SHIPMENT_LINES are populated based on its schedules. The listed references to JAI_* tables indicate integrations with localized tax and regulatory solutions, such as those for India.