Search Results po_ship_supply_view




Overview
Explore in AI Chat

Overview

PO_SHIP_SUPPLY_VIEW is a Purchasing (PO) module database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its functional purpose is to expose purchasing shipment supply — that is, the supply records that represent inbound shipments against purchase orders and requisitions within the Oracle supply/demand engine. The view is built on top of MTL_SUPPLY, the central table that Oracle uses to store all supply and demand entries consumed by planning, ATP, and related supply-chain logic. By filtering MTL_SUPPLY to rows where SUPPLY_TYPE_CODE equals 'SHIPMENT' and where the PO_LINE_LOCATION_ID is null, the view isolates shipment-based supply tied to requisition activity rather than PO shipment schedules.

Because the view surfaces shipment supply in a denormalized, reporting-friendly form, it is used in EBS reporting, custom inquiry screens, and integrations that need visibility into expected receipts. It is documented as a VALID object in the ETRM 12.2.2 repository, and the same definition is preserved across the 12.1.1 and 12.2.2 releases, ensuring query compatibility across both environments.

Underlying Base Objects

The view is defined over a set of base tables and one PL/SQL package, accessed through APPS synonyms. The documented referenced objects are:

The structure is a UNION ALL of two queries: the first handles shipment supply where a requisition line reference exists (or is null), and the second handles the PO-linked branch. The outer joins on requisition and distribution tables mean the view returns supply rows even when no requisition distribution is present.

Key Columns

The view exposes the following significant columns:

Common Use Cases and Queries

The view is typically queried to reconcile inbound shipment supply against expected receipts, to feed planning or custom dashboards, and to join supply to items or organizations for reporting. A representative query follows:

  • SELECT item_id, to_organization_id, shipment_num, quantity, uom_code, receipt_date, expected_delivery_date, destination_type_code FROM po_ship_supply_view WHERE to_organization_id = :org_id AND expected_delivery_date BETWEEN :start_date AND :end_date;
  • Join to MTL_SYSTEM_ITEMS_VL on ITEM_ID to obtain item descriptions and to HR_OPERATING_UNITS on TO_ORGANIZATION_ID for organization names.
  • Aggregate QUANTITY by ITEM_ID and DESTINATION_TYPE_CODE to summarize incoming supply per destination.

Because the view already decodes requisition-based quantities and outer-joins the requisition and distribution tables, consumers avoid writing the complex proportioning and outer-join logic themselves, making the view a convenient foundation for shipment-supply reporting in both 12.1.1 and 12.2.2.