Search Results rcv_trx_uom_code




Overview
Explore in AI Chat

Overview

APPS.PO_SHIP_RCV_SUPPLY_VIEW is an Oracle E-Business Suite internal database view owned by the APPS schema. It consolidates shipment, receiving transaction, and supply/demand information into a single reporting structure, joining receiving records from the RCV schema with supply records from MTL_SUPPLY and requisition data from the PO schema. The view presents, for each shipment line, the receipt transaction quantity, the unit of measure (UOM) associated with that transaction, and the equivalent quantity expressed in the item's primary UOM. This enables reconciliation between the UOM in which material was physically received and the primary inventory UOM of the item.

The object carries a status of VALID and is classified as an internal view (View Type: Internal). Oracle explicitly marks it with the warning "Oracle Internal Use Only," meaning Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Consequently, it should be treated as a dependency-resolution and reporting reference rather than a public API surface. Its presence in ETRM allows consultants to trace column lineage when troubleshooting seeded reports and concurrent programs that reference RCV_TRX_UOM_CODE.

Underlying Base Objects

The documented base objects underlying this view span three product schemas:

  • RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — supply the shipment header, line identifiers, shipment number, expected and dock dates, and destination attributes.
  • RCV_TRANSACTIONS — supplies the receiving transaction quantity and the transaction UOM code, which is the column most frequently searched in relation to this view.
  • MTL_SUPPLY — contributes supply and demand records, including MRP-processed quantities, MRP primary quantity, MRP destination type, and MRP destination organization/subinventory.
  • MTL_UNITS_OF_MEASURE — provides UOM definitions used to resolve the primary UOM and transaction UOM codes.
  • PO_REQUISITION_LINES_ALL and PO_REQ_DISTRIBUTIONS_ALL — contribute requisition and distribution context such as project and task identifiers.
  • PO_UNITEFF_PKG — a PL/SQL package referenced for unit-of-measure conversion logic used to derive primary UOM quantities.

Because the view is defined over synonyms in the APPS schema that resolve to these base tables, it acts as a denormalized projection of receiving and planning supply data.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling receiving UOM against primary UOM, analyzing MRP supply versus actual receipts, and tracing shipment destination data. A representative query isolating the searched column is:

  • SELECT SHIPMENT_NUM, SHIPMENT_LINE_NUM, ITEM_ID, ORGANIZATION_ID, RCV_TRX_QUANTITY, RCV_TRX_UOM_CODE, PRIMARY_UOM_QUANTITY, PRIMARY_UOM FROM APPS.PO_SHIP_RCV_SUPPLY_VIEW WHERE RCV_TRX_UOM_CODE IS NOT NULL;
  • Filter by ORGANIZATION_ID and DOCK_DATE to reconcile receipts within a period.
  • Compare RCV_TRX_QUANTITY against MRP_PRIMARY_QUANTITY where the UOM codes differ to detect conversion issues.

Given the Oracle Internal Use Only designation, any such query should be confined to diagnostic or reporting scenarios and not embedded in custom application logic.