Results for “rcv_distributions_print”

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

Overview

RCV_DISTRIBUTIONS_PRINT is an APPS-owned, VALID database view in the Oracle E-Business Suite Receiving (RCV) schema that belongs to the PO — Purchasing product family. The ETRM metadata documents the object as "Retrofitted," indicating that it was introduced or recreated to extend the standard receiving print and reporting logic to accommodate additional data sets — notably Return to Vendor (RTV) and inter-organization transfer flows — alongside the classic purchase order receipt path. Its principal role is to present a denormalized, human-readable row image of receiving distribution data: supplier or transfer source, destination location, subinventory, item, quantity, and license plate information, combined into a single concatenated address/identification string.

Underlying Base Objects

The view is defined over a substantial join of receiving, purchasing, human resources, and warehouse management tables. Documented referenced objects include:

• Receiving: RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, RCV_TRANSACTIONS_INTERFACE
• Purchasing: PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS, PO_DISTRIBUTIONS_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS_ALL
• Order Entry (for cross-document sourcing): OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_ALL, OE_TRANSACTION_TYPES_TL
• Human Resources / Parties: HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, PER_ALL_PEOPLE_F
• Inventory / WMS: MTL_SUPPLY, MTL_UNITS_OF_MEASURE_TL, WMS_LICENSE_PLATE_NUMBERS
• Lookups and utilities: PO_LOOKUP_CODES, FND_GLOBAL

The view text joined these primarily via shipment line, shipment header, PO line, line location, PO header, and distribution keys, with outer joins on HR organizations and locations filtered by USERENV('LANG') and FND_GLOBAL for multi-language display names.

Key Columns

The view exposes columns that mirror the receipt creation and printing workflow: ORGANIZATION_ID, TRANSACTION_ID, TRANSACTION_DATE, and QUANTITY for the receipt transaction itself; SEGMENT1 (PO number), UNIT_MEAS_LOOKUP_CODE, NOTE_TO_RECEIVER, and the computed open-quantity expression (QUANTITY_ORDERED − QUANTITY_CANCELLED − QUANTITY_DELIVERED); PO_DISTRIBUTION_ID, DESTINATION_SUBINVENTORY, LOCATOR_ID, and the WIP-related columns (WIP_ENTITY_ID, WIP_LINE_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, WIP_REPETITIVE_SCHEDULE_ID, BOM_RESOURCE_ID) for shop-floor receipts. The concatenated display string is built from the FULL_NAME of PER_ALL_PEOPLE_F (the "full_name" search term maps directly to this column), LOCATION_CODE from HR_LOCATIONS_ALL_TL, the destination organization NAME, and the effective subinventory. LICENSE_PLATE_NUMBER and TRANSFER_LICENSE_PLATE_NUMBER are supplied by WMS_LICENSE_PLATE_NUMBERS aliases WLPN1 and WLPN2.

Common Use Cases and Queries

RCV_DISTRIBUTIONS_PRINT supports receiving print reports, distribution listings, and reconciliation of goods received to PO distributions. A typical query is:

SELECT transaction_id, full_name, segment1, quantity, transaction_date
FROM apps.rcv_distributions_print
WHERE organization_id = :p_org_id
AND transaction_date BETWEEN :p_from AND :p_to;

Because the view already performs the FULL_NAME and location resolution, it is frequently used in lieu of writing custom joins to PER_ALL_PEOPLE_F and HR_LOCATIONS_ALL_TL. Analysts should note that the view is retrofitted and may reflect a superset of columns beyond the excerpted text, so column-level verification against the deployed 12.1.1 or 12.2.2 instance is advisable before dependency in custom code.