Search Results rcv_trx_uom_code

Overview

PO_RCV_SUPPLY_VIEW is a seeded APPS schema view in the Oracle E-Business Suite Purchasing (PO) module, documented with the description "Receiving supply." It exposes the portion of the MTL_SUPPLY table whose SUPPLY_TYPE_CODE equals 'RECEIVING', enriching each supply row with the associated purchasing, receipt, and unit-of-measure context. In effect, the view answers the question: "What incoming material do we expect or have we recorded as a receiving transaction, and against which purchase document?"

Because receiving supply records bridge Purchasing, Receiving, Inventory, and Planning, the view serves as a convenient denormalised source for reporting, data extraction, and integration. Developers and analysts use it to avoid writing the multi-table join manually. It is read-only and carries no DML of its own; it inherits the APPS data model and standard security considerations.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms: MTL_SUPPLY, MTL_UNITS_OF_MEASURE, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, RCV_SHIPMENT_HEADERS, and RCV_TRANSACTIONS.

The driving table is MTL_SUPPLY, filtered to SUPPLY_TYPE_CODE = 'RECEIVING'. It joins to PO_HEADERS_ALL on PO_HEADER_ID, to PO_LINES_ALL on PO_LINE_ID, to PO_LINE_LOCATIONS_ALL on PO_LINE_LOCATION_ID, to PO_DISTRIBUTIONS_ALL on PO_DISTRIBUTION_ID, and to RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS via the shipment header and receipt transaction identifiers. PO_RELEASES_ALL is an outer join (PR.PO_RELEASE_ID(+) = MS.PO_RELEASE_ID), so blanket-release details are optional. MTL_UNITS_OF_MEASURE supplies the UOM_CODE. These relationships confirm the view is a purchasing-and-receiving composite over inventory supply.

Key Columns

The projected columns cover identification, quantities, and planning attributes:

• ITEM_ID, PO_HEADER_ID, PO_LINE_ID, VENDOR_ID, VENDOR_SITE_ID — core entity keys linking the supply to the item and purchasing document.
• PO_NUMBER — derived from PO_HEADERS_ALL.SEGMENT1; when a release exists, the release number is appended in parentheses.
• RCV_TRX_QUANTITY, RCV_TRX_UOM_CODE — receiving transaction quantity and its unit of measure.
• PRIMARY_UOM_QUANTITY, PRIMARY_UOM — quantity and UOM expressed in the destination organisation's primary UOM.
• MRP_EXPECTED_DELIVERY_DATE, EXPECTED_DELIVERY_DATE, DOCK_DATE — planned and transactional dates used by planning and receiving.
• MRP_PRIMARY_QUANTITY, MRP_PRIMARY_UOM, MRP_DESTINATION_TYPE_CODE, MRP_TO_ORGANIZATION_ID, MRP_TO_SUBINVENTORY — MRP-oriented destination and quantity attributes.
• DESTINATION_TYPE_CODE, TO_ORGANIZATION_ID, TO_SUBINVENTORY, FROM_ORGANIZATION_ID — routing of the supply.
• LINE_NUM, PO_REVISION_NUM, RECEIVING_DOCUMENT_DESIGNATOR, ITEM_REVISION, UNIT_PRICE — document and pricing detail.
• PROJECT_ID, TASK_ID, END_ITEM_UNIT_NUMBER — project and end-item references from PO_DISTRIBUTIONS_ALL.

Common Use Cases and Queries

Typical scenarios include open receiving supply reporting, reconciliation of expected receipts against purchase orders, MRP supply feeds, and destination/subinventory analysis. A representative query lists incoming supply for a given organisation:

• SELECT po_number, item_id, rcv_trx_quantity, rcv_trx_uom_code, mrp_expected_delivery_date, mrp_to_subinventory FROM apps.po_rcv_supply_view WHERE mrp_to_organization_id = :org_id ORDER BY mrp_expected_delivery_date;
• Filter by po_header_id or po_line_id to reconcile a specific order line against its receipts.
• Aggregate mrp_primary_quantity by mrp_to_subinventory to review planned inbound inventory.

Because the view exposes only 'RECEIVING' supply rows and relies on inner joins for most purchasing and receipt tables, records missing an associated receipt transaction or distribution are excluded. Consumers should therefore treat it as a targeted reporting view rather than a complete inventory picture.