Search Results dist_qty_ordered

Overview

APPS.PO_PURCHASE_ORDER_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and registered under FND Design Data as PO.PO_PURCHASE_ORDER_V. It presents a flattened, denormalized projection of purchasing document data, joining header-level, line-level, release-level, shipment-level, and distribution-level attributes into a single row-per-line construct. The view exposes the purchase order number, buyer and vendor names, document type, currency, line item description, unit price, ordered quantity, and the critical quantity tracking columns QTY_CANCELLED, QTY_RECEIVED, and QTY_BILLED. In Oracle EBS 12.1.1 and 12.2.2 it is most commonly accessed for operational reporting, custom concurrent programs, and integration extracts where a business user requires a readable purchasing summary without navigating Oracle Purchasing forms.

The object carries the warning "Oracle Internal Use Only," meaning Oracle Corporation does not support direct access except from standard Oracle Applications programs. Customers may still query it for reporting, but should recognize that the view definition is not part of the supported public interface and may change without notice between point releases.

Underlying Base Objects

The view is constructed over a combination of purchasing base tables, HR security and name-resolution objects, and vendor data. Documented dependencies in 12.2.2 include PO_HEADERS and PO_HEADERS_ALL (header attributes such as PO_NO, PO_DATE, REVISION_NO, PO_TYPE, CURRENCY, and ORG_ID), PO_LINES_ALL (LINE_NO, ITEM_DESCRIPTION, UNIT_OF_MEASURE, UNIT_PRICE, QUANTITY), and PO_LINE_LOCATIONS_ALL (shipment-level SHIP_TO_LOCATION, QTY_RECEIVED, QTY_CANCELLED). Distribution-level quantities DIST_QTY_ORDERED and DIST_QTY_CANCELLED are sourced from PO_DISTRIBUTIONS_ALL. Release information (RELEASE_NO) is drawn from PO_RELEASES and PO_RELEASES_ALL.

Buyer and vendor display values are resolved through HR and supplier objects: PER_PEOPLE_F, HR_PERSON_NAME (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), HR_LOCATIONS (VIEW), and PO_VENDORS (VIEW). The inclusion of HR_SECURITY indicates the view applies Oracle HR organization security when resolving personnel data, which is relevant when the view is queried in multi-organization environments.

Key Columns

• PO_NO / RELEASE_NO / REVISION_NO — Purchasing document identity and revision tracking.
• PO_DATE, BUYER_NAME, VENDOR_NAME, PO_TYPE, CURRENCY — Header context used for filtering and grouping.
• LINE_NO, ITEM_DESCRIPTION, UNIT_OF_MEASURE, UNIT_PRICE — Line-level detail for the ordered item.
• QUANTITY — Quantity ordered (or break quantity for blanket purchase orders, RFQs, and quotations).
• QTY_CANCELLED — Quantity cancelled against the line or shipment. This is the column surfaced by the search term and is central to open-order and short-close analysis.
• QTY_RECEIVED — Quantity received to date, used for receipt matching and three-way match monitoring.
• QTY_BILLED — Quantity invoiced to date by Oracle Payables.
• SHIP_TO_LOCATION, DIST_QTY_ORDERED, DIST_QTY_CANCELLED, ORG_ID — Shipment and distribution detail plus the operating unit / organization context for multi-org reporting.

Common Use Cases and Queries

The view is typically used to produce open purchase order reports, track delivery performance, reconcile received versus billed quantities, and extract cancellation history. A frequent pattern compares ordered, received, cancelled, and billed quantities to detect lines with outstanding commitments.

• Open order analysis: SELECT po_no, line_no, quantity, qty_received, qty_cancelled, quantity - NVL(qty_received,0) - NVL(qty_cancelled,0) outstanding FROM apps.po_purchase_order_v WHERE org_id = :p_org_id;
• Cancellation tracking: SELECT po_no, line_no, item_description, quantity, qty_cancelled FROM apps.po_purchase_order_v WHERE qty_cancelled > 0 ORDER BY po_no, line_no;
• Three-way match exceptions: compare QTY_RECEIVED against QTY_BILLED to identify uninvoiced receipts.
• Supplier and buyer rollups: group by VENDOR_NAME and BUYER_NAME with SUM(QUANTITY) and SUM(QTY_CANCELLED).

Because the view aggregates header, release, line, shipment, and distribution data, row counts can multiply when multiple shipments or distributions exist per line. Consumers should apply appropriate filters, such as ORG_ID and PO_TYPE, to avoid overstated quantities in aggregated reports.