Search Results po_line_locations_all




Overview
Explore in AI Chat

Overview

PO_LINE_LOCATIONS_ALL is the transactional table in the Oracle Purchasing (PO) schema that stores document shipment schedules for purchase orders, purchase agreements, quotations, and RFQs. It resides in the PO schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. Each row represents a single shipment schedule tied to a purchase order line, capturing delivery, quantity, pricing, receiving, invoicing, and tax attributes for that shipment. Because a single PO line may have multiple shipments (staggered deliveries, multiple ship-to locations, or split quantities), this table functions as the operational unit against which receiving, matching, and invoicing transactions are recorded.

From a dimensional modeling perspective, the ETRM Data Vault classification for this object is hub-leaning. This is a modeling suggestion: LINE_LOCATION_ID behaves as a durable business key that anchors inbound references from numerous downstream transactional tables, making it a strong hub candidate. Its foreign keys to header, line, release, location, and routing entities position it as a central junction linking purchasing structure to logistics and financial execution.

Key Information Stored

The primary key is LINE_LOCATION_ID, enforced through PO_LINE_LOCATIONS_PK and backed by unique index PO_LINE_LOCATIONS_U1. The business-key candidate PO_LINE_LOCATIONS_UK1 is composed of PO_LINE_ID and SHIPMENT_NUM, ensuring a shipment number is unique within its parent line. The most significant columns include:

Common Use Cases and Queries

Typical reporting covers open shipments by need-by date, receipt status, and invoice matching. A representative query retrieves open shipments for a buyer:

  • Join PO_LINE_LOCATIONS_ALL to PO_HEADERS_ALL and PO_LINES_ALL on PO_HEADER_ID and PO_LINE_ID to obtain buyer, supplier, and item context.
  • Filter on CLOSED_CODE and CANCEL_FLAG to isolate outstanding deliveries.
  • Compute open quantity as QUANTITY less QUANTITY_RECEIVED less QUANTITY_CANCELLED.
  • Join to RCV_SHIPMENT_LINES on PO_LINE_LOCATION_ID to trace receipt activity, or to AP_INVOICE_LINES_ALL on PO_LINE_LOCATION_ID for invoice matching.
  • Use NEED_BY_DATE range filters for expediting and delivery performance reporting by SHIP_TO_ORGANIZATION_ID.

Related Objects

The following objects are most significant to PO_LINE_LOCATIONS_ALL:

  • PO_HEADERS_ALL — referenced via PO_HEADER_ID and FROM_HEADER_ID.
  • PO_LINES_ALL — referenced via PO_LINE_ID and FROM_LINE_ID.
  • PO_RELEASES_ALL — referenced via PO_RELEASE_ID.
  • HR_LOCATIONS_ALL — referenced via SHIP_TO_LOCATION_ID.
  • RCV_ROUTING_HEADERS — referenced via RECEIVING_ROUTING_ID.
  • PO_DISTRIBUTIONS_ALL — references this table via LINE_LOCATION_ID.
  • RCV_SHIPMENT_LINES / RCV_TRANSACTIONS — reference this table via PO_LINE_LOCATION_ID.
  • AP_INVOICE_LINES_ALL / AP_HOLDS_ALL — reference this table via PO_LINE_LOCATION_ID and LINE_LOCATION_ID respectively.
  • PO_LINE_LOCATIONS_ALL — self-references via FROM_LINE_LOCATION_ID and SOURCE_SHIPMENT_ID.

Correct interpretation of this table is essential for procurement, receiving, and payables reporting across the EBS suite.