Search Results delivered_by




Overview
Explore in AI Chat

Overview

APPS.RCV_DISTRIBUTIONS_PRINT_REQ is an internal Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data under the product short name PO (design data key PO.RCV_DISTRIBUTIONS_PRINT_REQ). It is an internal view type referenced by Oracle Applications programs that produce receiving distribution printing and requisition-based delivery output. The view consolidates receiving transaction distribution information into a report-oriented shape, joining purchase requisition, receiving, and warehouse management data so that delivered quantities, destinations, and license plate identifiers can be presented together on a single row. In Oracle EBS 12.1.1 and 12.2.2 the object retains a VALID status.

The view is documented with an explicit Oracle Internal Use Only warning. 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 an implementation detail of the receiving print/distribution reports rather than as a supported public interface.

Underlying Base Objects

The view is defined over a documented set of synonyms, tables, and one package, reflecting the breadth of the receiving and requisition data model:

The view therefore unifies requisition distribution demand with receiving execution detail, including the WIP and BOM reference columns (WIP_ENTITY_ID, WIP_LINE_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, WIP_REPETITIVE_SCHEDULE_ID, BOM_RESOURCE_ID) that tie a distribution to a manufacturing work order or resource.

Key Columns

The most operationally significant columns include ORGANIZATION_ID, which anchors every row to an inventory organization, and DESTINATION_TYPE with DESTINATION, which classify and name the receiving destination. DOCUMENT_NUM, DELIVER_UNIT_OF_MEASURE, OUTSTANDING_QUANTITY, and QUANTITY_DELIVERED express the requisition document, its unit of measure, the balance still outstanding, and what has been delivered. DELIVERY_DATE, DELIVERED_BY, DELIVER_TRANSACTION_TYPE, and TRANSACTION_ID identify the receiving event and its actor.

DISTRIBUTION_ID links the row to the underlying requisition distribution, while FROM_INTERFACE indicates whether the row originated in RCV_TRANSACTIONS_INTERFACE. Delivery addressing is carried by DELIVER_TO_PERSON, DELIVER_TO_LOCATION, DELIVER_TO_ORG, DESTINATION_SUBINVENTORY, and LOCATOR_ID.

The columns most relevant to the searched term are LICENSE_PLATE_NUMBER (VARCHAR2(30)), documented as the license plate number in which the material was received or delivered, and TRANSFER_LICENSE_PLATE_NUMBER (VARCHAR2(30)), documented as the transfer license plate number in which the material was received or delivered. Both are sourced from the WMS license plate infrastructure and are exposed here to support print output that must identify the physical handling unit moved between receiving locations. PLL_NOTE_TO_DELIVER and NOTE_TO_DELIVER carry delivery instructions.

Common Use Cases and Queries

Typical usage is diagnostic in nature, since the view is internal: tracing which license plate carried a delivery, reconciling requisition distributions against received quantities, or confirming whether a row has been posted or remains in the interface. A representative query for license plate tracing is:

  • SELECT DISTRIBUTION_ID, DOCUMENT_NUM, DESTINATION, LICENSE_PLATE_NUMBER, TRANSFER_LICENSE_PLATE_NUMBER, QUANTITY_DELIVERED, DELIVERY_DATE FROM APPS.RCV_DISTRIBUTIONS_PRINT_REQ WHERE ORGANIZATION_ID = :org_id AND (LICENSE_PLATE_NUMBER = :lpn OR TRANSFER_LICENSE_PLATE_NUMBER = :lpn);
  • SELECT DOCUMENT_NUM, OUTSTANDING_QUANTITY, QUANTITY_DELIVERED, FROM_INTERFACE FROM APPS.RCV_DISTRIBUTIONS_PRINT_REQ WHERE ORGANIZATION_ID = :org_id ORDER BY DOCUMENT_NUM;
  • SELECT DELIVER_TO_PERSON, DELIVER_TO_LOCATION, DESTINATION_SUBINVENTORY, LOCATOR_ID FROM APPS.RCV_DISTRIBUTIONS_PRINT_REQ WHERE TRANSACTION_ID = :transaction_id;

Because the object is unsupported for direct customer access, these queries should be confined to troubleshooting and reporting research, with supported receiving reports and APIs preferred for production integrations.