Search Results po_line_locations_xml




Overview
Explore in AI Chat

Overview

PO_LINE_LOCATIONS_XML is a reporting and integration view owned by the APPS schema within the Oracle Purchasing (PO) module. It presents shipment-level scheduling data from purchase order lines, exposing rows from the PO_LINE_LOCATIONS_ALL base table in a form oriented toward XML generation, outbound messaging, and external interface consumption. In Oracle EBS 12.1.1 and 12.2.2, the view is registered as VALID in the ETRM data dictionary. Its principal design characteristic is the pre-formatting of date and currency columns as character strings, so downstream XML publishers and communication programs receive display-ready values without applying their own format masks. This makes the view particularly relevant to the Purchasing document communication framework, where purchase orders are rendered into XML payloads for supplier delivery.

Underlying Base Objects

The view is defined over a small set of documented objects. The primary source is PO_LINE_LOCATIONS_ALL, accessed through a synonym, which supplies every shipment (line location) attribute projected by the view. PO_LINES_ALL and PO_CORE_S provide the line and core document context referenced by the projected identifiers. PO_COMMUNICATION_PVT is invoked as a package function, PO_COMMUNICATION_PVT.GETFORMATMASK, to derive the numeric format mask applied to the PRICE_OVERRIDE column, ensuring price values conform to the formatting conventions used by Purchasing communication output. PO_COMMUNICATION_GT, MTL_UNITS_OF_MEASURE_TL, and additional synonyms complete the documented reference set. The view is therefore a lightweight projection rather than a join-heavy construct, and its row cardinality mirrors the shipments held against purchase order lines, releases, and blanket agreements.

Key Columns

The view exposes the shipment identifiers SHIPMENT_NUM, PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, and PO_RELEASE_ID, which together form the document hierarchy used by callers. Scheduling information is carried in DUE_DATE, derived from NVL(NEED_BY_DATE, PROMISED_DATE) and formatted as DD-MON-YYYY HH24:MI:SS, alongside START_DATE and END_DATE for service and rate-based shipments. Quantity and pricing data appear as QUANTITY and PRICE_OVERRIDE. Cancellation and closure state is represented by QUANTITY_CANCELLED, CANCEL_FLAG, CANCEL_DATE, CANCEL_REASON, CLOSED_CODE, CLOSED_REASON, CLOSED_DATE, and CLOSED_BY.

Receiving and invoicing controls include RECEIPT_REQUIRED_FLAG, INSPECTION_REQUIRED_FLAG, ACCRUE_ON_RECEIPT_FLAG, ALLOW_SUBSTITUTE_RECEIPTS_FLAG, QTY_RCV_TOLERANCE, QTY_RCV_EXCEPTION_CODE, ENFORCE_SHIP_TO_LOCATION_CODE, RECEIPT_DAYS_EXCEPTION_CODE, INVOICE_CLOSE_TOLERANCE, and RECEIVE_CLOSE_TOLERANCE. The SHIPMENT_TYPE column applies a DECODE that normalises stored values into BLANKET, RELEASE, STANDARD, or PLANNED. Fifteen descriptive flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15), TAXABLE_FLAG, CONSIGNED_FLAG, ENCUMBERED_FLAG, USSGL_TRANSACTION_CODE, GOVERNMENT_CONTEXT, ORG_ID, and the standard concurrent program audit columns complete the projection.

Common Use Cases and Queries

Typical usage includes retrieving formatted shipment schedules for a given purchase order, extracting receipt and inspection control settings for interface validation, and supplying XML communication processes with display-formatted due dates and prices.

  • Listing shipments for a header: SELECT SHIPMENT_NUM, DUE_DATE, QUANTITY, PRICE_OVERRIDE, SHIPMENT_TYPE FROM PO_LINE_LOCATIONS_XML WHERE PO_HEADER_ID = :p_header_id ORDER BY PO_LINE_ID, SHIPMENT_NUM;
  • Identifying open receipt-controlled shipments: SELECT LINE_LOCATION_ID, DUE_DATE, QUANTITY, QTY_RCV_TOLERANCE FROM PO_LINE_LOCATIONS_XML WHERE RECEIPT_REQUIRED_FLAG = 'Y' AND CLOSED_CODE IS NULL AND ORG_ID = :p_org_id;
  • Reporting cancellations: SELECT PO_LINE_ID, SHIPMENT_NUM, QUANTITY_CANCELLED, CANCEL_DATE, CANCEL_REASON FROM PO_LINE_LOCATIONS_XML WHERE CANCEL_FLAG = 'Y';

Because date and price columns are returned as formatted character strings, consumers should avoid direct arithmetic or date comparison on DUE_DATE, START_DATE, END_DATE, CANCEL_DATE, and CLOSED_DATE. For computational or bulk extraction requirements, querying PO_LINE_LOCATIONS_ALL directly is preferable, reserving PO_LINE_LOCATIONS_XML for communication-oriented and display-oriented output.