Search Results rcv_distributions_print_inv




Overview
Explore in AI Chat

Overview

RCV_DISTRIBUTIONS_PRINT_INV is an APPS-owned view in the Oracle E-Business Suite Receiving (RCV) schema, delivered under the Purchasing (PO) product family. As its name implies, the view supplies the distribution-level data set consumed by the receiving "Print Receipt" and inventory transfer report programs when the receipt source is internal — that is, receipts originating from an inventory or internal order shipment rather than from a supplier. The ETRM metadata classifies the object as VALID and marks its description as "Retrofitted," indicating that the view was re-engineered during the 12.1.1 to 12.2.2 upgrade cycle to remain compatible with the Online Patching (adop) and Editioning architecture introduced in Release 12.2.

Because the view is a read-only projection combining receiving transaction, shipment, and supply records, it plays no role in transaction entry. Its function is strictly declarative: it presents a stable, report-friendly shape over volatile RCV and MTL data so that concurrent programs and diagnostic queries can render in-transit and internal shipment distributions without re-deriving the join logic themselves.

Underlying Base Objects

The documented dependency list reflects the full join graph. Core transactional data comes from RCV_TRANSACTIONS (RCT), RCV_SHIPMENT_LINES (RSL), and RCV_SHIPMENT_HEADERS (RSH), joined on SHIPMENT_LINE_ID and SHIPMENT_HEADER_ID. Supply and in-transit quantities are drawn from MTL_SUPPLY (MS) and three aliased instances of RCV_TRANSACTIONS_INTERFACE (RTI1, RTI2, RTI3), whose signed quantities are summed to derive the in-transit balance. Descriptive attributes are resolved through HR_ALL_ORGANIZATION_UNITS_TL (OOD), HR_LOCATIONS_ALL_TL (HRL), and two instances of PER_ALL_PEOPLE_F (PPF, PPF1). Lookup decodes are supplied by PO_LOOKUP_CODES (PLC), and license plate references by two instances of WMS_LICENSE_PLATE_NUMBERS (WLPN1, WLPN2). The view also references FND_GLOBAL (package) for environment context such as language.

Key Columns

  • ORGANIZATION_ID — receiving organization context, taken from RCV_TRANSACTIONS.
  • TRANSACTION_ID, TRANSACTION_DATE, QUANTITY — the receiving transaction identity, date, and quantity.
  • SHIPMENT_NUM, SHIPMENT_LINE_ID — shipment header number and unique shipment line identifier.
  • DISPLAYED_FIELD (PLC) — decoded lookup text; the search term transaction_type resolves here, since PO_LOOKUP_CODES supplies the human-readable transaction type and related lookup meanings.
  • Literal 'IN TRANSIT' — a hard-coded status column identifying internal movement rows.
  • Destination columns — concatenated deliver-to person, location code, organization name, and destination subinventory (NVL(RSL.TO_SUBINVENTORY, RCT.SUBINVENTORY)).
  • LICENSE_PLATE_NUMBER / TRANSFER_LICENSE_PLATE_NUMBER — LPN context for WMS-enabled warehouses.

Common Use Cases and Queries

Typical usage is reporting on internal/inventory-origin receipts and reconciling in-transit quantities between organizations. A representative query filtering by transaction type is:

SELECT transaction_id, shipment_num, transaction_date, quantity, displayed_field
FROM apps.rcv_distributions_print_inv
WHERE organization_id = :org_id
AND displayed_field = 'TRANSFER'
ORDER BY transaction_date DESC;

Because several columns are literal placeholders returning NULL or empty strings, consumers should not assume every projected column is populated; validation against RCV_TRANSACTIONS remains advisable for audit-grade reporting.