Search Results rcv_distributions_print_req




Overview

The APPS.RCV_DISTRIBUTIONS_PRINT_REQ view is a reporting construct within the Oracle E-Business Suite Purchasing (PO) module that presents receipt transaction distribution detail specifically for requisition-sourced internal order receipts. The view is documented in the ETRM repository as a retrofitted object with a status of VALID, indicating that it has been adapted across releases—most notably between Oracle EBS 12.1.1 and 12.2.2—to accommodate schema and table changes in the Receiving (RCV) and Purchasing data model. Its name reflects its purpose: it feeds distribution-level print and inquiry output for receipts tied to internal requisitions.

Functionally, the view joins receipt transaction lines back to their originating requisition lines and distributions, resolving the descriptive attributes (requester name, deliver-to location, destination organization, subinventory, and license plate numbers) that a receipt traveler or distribution report requires. Because it is a view rather than a table, it stores no data of its own and incurs no maintenance cost; all values are derived at query time from the underlying transactional and master tables.

Underlying Base Objects

The view is defined over a broad set of base objects, joined primarily on the shipment line, requisition line, and distribution keys:

The join predicates restrict the output to transactions where SOURCE_DOCUMENT_CODE = 'REQ' and the receipt header carries RECEIPT_SOURCE_CODE = 'INTERNAL ORDER', so only internal requisition receipts are returned.

Key Columns

  • ORGANIZATION_ID — the inventory organization of the receipt transaction.
  • TRANSACTION_ID, QUANTITY, TRANSACTION_DATE — the receipt transaction identity, quantity, and posting date.
  • SEGMENT1 — the requisition number from PO_REQUISITION_HEADERS.
  • UNIT_MEAS_LOOKUP_CODE — the unit of measure for the requisition line.
  • Open quantity expressionQUANTITY - QUANTITY_CANCELLED - QUANTITY_DELIVERED, the outstanding quantity yet to be delivered.
  • NOTE_TO_RECEIVER — the instruction text carried on the requisition line.
  • Requester / deliver-to composite — a concatenation of the person full name, location code, organization name, and the target subinventory (NVL(RSL.TO_SUBINVENTORY, RCT.SUBINVENTORY)).
  • DISTRIBUTION_ID — the requisition distribution identifier.
  • LOCATOR_ID — the inventory locator associated with the receipt.
  • LICENSE_PLATE_NUMBER and TRANSFER_LICENSE_PLATE_NUMBER — LPN detail for WMS-enabled flows.
  • Several positional TO_NUMBER(NULL) and empty-string placeholders exist to preserve a fixed report layout, plus the literal 'REQ' as the source document code indicator.

Common Use Cases and Queries

This view is typically consumed by receipt printing and requisition receipt inquiry reports. A basic query filters by transaction to retrieve distribution print detail:

  • Receipt traveler printing — retrieve requester, deliver-to location, subinventory, and open quantity for a given TRANSACTION_ID.
  • Internal requisition receipt inquiry — list all distributions for a requisition identified by SEGMENT1.
  • Delivery reconciliation — compare received QUANTITY against the open quantity expression to identify short or pending deliveries.

Example: SELECT transaction_id, segment1, quantity, note_to_receiver FROM apps.rcv_distributions_print_req WHERE transaction_id = :txn_id;

Because the view enforces the internal-order and requisition filters internally, callers do not need to reapply those predicates, though additional organization or date restrictions improve performance on large receipt volumes.