Results for “po_ship_rcv_supply_view”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_SHIP_RCV_SUPPLY_VIEW is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Shipment receipts supply," and its role is to present a consolidated, report-ready picture of supply records that originate from receiving transactions. The view draws from the MTL_SUPPLY table but filters strictly to rows where SUPPLY_TYPE_CODE = 'RECEIVING', so it exposes only the supply generated by receiving activity rather than the full range of supply types stored in the base table.

Because it is a view and not a table, PO_SHIP_RCV_SUPPLY_VIEW carries no data of its own. It is used for reporting and integration scenarios in which receipt-driven supply must be reconciled with shipment, requisition, and unit-of-measure information. The view also contributes indirectly to the ETRM ("shipment_line_num") search context through its exposure of SHIPMENT_LINE_ID, SHIPMENT_HEADER_ID, and SHIPMENT_NUM columns, which are the keys that link back to the underlying shipment line numbering on RCV_SHIPMENT_LINES.

Underlying Base Objects

The ETRM metadata identifies the following referenced objects, all accessed through synonyms except for the package:

The view therefore joins receiving shipment data to inventory supply and optional requisition data, applying an outer join so that supply records without a requisition line are still returned.

Key Columns

Documented columns include ITEM_ID, TO_ORGANIZATION_ID, FROM_ORGANIZATION_ID, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, SHIPMENT_NUM, LINE_NUM, and TRANSACTION_DATE, which together identify the item, the shipment line receiving it, and when the transaction occurred. Quantity columns — QUANTITY, TO_ORG_PRIMARY_QUANTITY, MRP_PRIMARY_QUANTITY — are conditionally scaled by the ratio PD.REQ_LINE_QUANTITY / PL.QUANTITY when a requisition line exists, so quantities are expressed in the requisition's terms. UOM columns (UOM_CODE, TO_ORG_PRIMARY_UOM, MRP_PRIMARY_UOM) describe the relevant units, while DESTINATION_TYPE_CODE, TO_SUBINVENTORY, MRP_DESTINATION_TYPE_CODE, MRP_TO_ORGANIZATION_ID, and MRP_TO_SUBINVENTORY define where the supply is destined. ITEM_REVISION, EXPECTED_DELIVERY_DATE, and MRP_EXPECTED_DELIVERY_DATE support planning and revision-specific reporting, and PROJECT_ID, TASK_ID, and END_ITEM_UNIT_NUMBER carry project and unit-number context.

Common Use Cases and Queries

Typical uses include reconciling receiving supply against shipments, reporting expected versus actual receipt supply by organization or subinventory, and feeding planning or project reporting with requisition-adjusted quantities. A representative query joining back to the shipment line numbering is:

  • SELECT shipment_num, shipment_line_id, line_num, item_id, transaction_date, quantity, uom_code FROM po_ship_rcv_supply_view WHERE shipment_num = :p_shipment_num;
  • SELECT ms.item_id, ms.to_organization_id, ms.quantity, ms.to_org_primary_quantity FROM po_ship_rcv_supply_view ms WHERE ms.shipment_line_id = :p_shipment_line_id;
  • SELECT destination_type_code, to_subinventory, SUM(quantity) FROM po_ship_rcv_supply_view GROUP BY destination_type_code, to_subinventory;

Because the view restricts to RECEIVING supply and to rows with a null PO distribution, results represent receipt-generated supply only; queries seeking other supply types must use MTL_SUPPLY directly.