Search Results po_uom_code

Overview

PO_PO_SUPPLY_VIEW is an APPS-owned database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 Purchasing (PO) module. It exposes purchasing supply records drawn from the planning supply repository and joins that supply data to the underlying purchasing documents that generated it. The view is defined with the description "Purchasing supply," reflecting its purpose: presenting the purchasing side of the supply/demand picture used by planning, procurement, and reporting processes.

Unlike transactional PO tables, which record document state, this view consolidates supply rows filtered to supply types of 'PO' and 'ASN' (advance ship notice). This means it returns only supply originating from purchase orders and ASNs, not from other supply sources such as requisitions or internal transfers. It is used for reporting on expected deliveries, comparison of ordered versus MRP quantities, and integration with planning and receiving logic.

Underlying Base Objects

The view is defined over the following documented base objects in the APPS schema:

• MTL_SUPPLY — the core supply repository; the driving source of rows.
• MTL_UNITS_OF_MEASURE — provides UOM codes, joined on UNIT_OF_MEASURE.
• PO_HEADERS_ALL — joined on PO_HEADER_ID for header-level attributes such as vendor and printed date.
• PO_LINES_ALL — joined on PO_LINE_ID for line-level details including line number and item revision.
• PO_LINE_LOCATIONS_ALL — joined on LINE_LOCATION_ID for shipment-level firm status and dates.
• PO_DISTRIBUTIONS_ALL — joined on PO_DISTRIBUTION_ID for project, task, and end-item information.
• PO_RELEASES_ALL — outer-joined on PO_RELEASE_ID to support releases against blanket agreements.

The header, release, line, and location joins are strict inner joins except for the release, which uses the outer join operator (+) because a supply row may or may not be tied to a release.

Key Columns

Important columns include ITEM_ID, the inventory item reference, and TO_ORGANIZATION_ID, denoting the destination organization. PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, and PO_DISTRIBUTION_ID provide the purchasing document keys.

VENDOR_ID and VENDOR_SITE_ID identify the supplier and site. QUANTITY reflects the supply quantity, while PO_UOM_CODE (derived from MTL_UNITS_OF_MEASURE.UOM_CODE) is the unit of measure for the purchasing quantity — the column most relevant to a search for "po_uom_code." TO_ORG_PRIMARY_QUANTITY and TO_ORG_PRIMARY_UOM express the quantity and UOM converted to the destination organization's primary UOM.

Dates include NEED_BY_DATE, EXPECTED_DELIVERY_DATE, and MRP_EXPECTED_DELIVERY_DATE. Firm status is computed with nested DECODE logic comparing firm dates to SYSDATE. Additional columns expose MRP destinations, DESTINATION_TYPE_CODE, TO_SUBINVENTORY, project and task data, and END_ITEM_UNIT_NUMBER.

Common Use Cases and Queries

Typical uses include expected-receipt reporting, supply/demand analysis, and reconciliation between purchasing documents and MRP figures. A basic query retrieving UOM and quantity per item is shown below.

SELECT item_id, po_header_id, quantity, po_uom_code, expected_delivery_date FROM apps.po_po_supply_view WHERE to_organization_id = :org_id;

Reports often join the view to PO_HEADERS_ALL via PO_HEADER_ID to display the PO number, or to MTL_SYSTEM_ITEMS to resolve item descriptions. Because the view already carries primary-UOM conversions, it is convenient for cross-organization comparisons without additional conversion logic.