Search Results default_po_info




Overview

RCV_ROI_RETURN is a PL/SQL package owned by the APPS schema that forms part of the Receiving Open Interface (ROI) processing infrastructure in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to derive, default, and validate the attribute values required to construct and process return transactions — most notably Return to Vendor (RTV) and RMA-related return receipts — before they are inserted into the receiving transactions interface. The package acts as a rules engine: for each inbound return record, it determines the source document, item, quantity, destination, and organization context, then populates the RCV_TRANSACTIONS_INTERFACE table so that the standard receiving transaction processor can consume the data.

Within the ROI architecture, RCV_ROI_RETURN is one of a family of transaction-type-specific packages (alongside transaction, transfer, and preprocessor modules). It is referenced by RCV_ROI_PREPROCESSOR, RCV_ROI_TRANSACTION, RCV_RMA_TRANSACTIONS, RCV_INT_ORDER_PP_PVT, and RCV_INT_ORG_TRANSFER, indicating it is invoked during interface preprocessing and return-specific derivation logic. The package status is VALID in the documented environment.

Key Procedures and Functions

The documented interface exposes 22 procedures and functions, organized around derivation and defaulting of return line attributes:

Source-specific defaulting routines include DEFAULT_PO_INFO, DEFAULT_SHIPMENT_INFO, DEFAULT_WIP_INFO, DEFAULT_OE_INFO, DEFAULT_VENDOR_INFO, DEFAULT_CUSTOMER_INFO, DEFAULT_ITEM_INFO, DEFAULT_SOURCE_INFO, DEFAULT_DESTINATION_INFO, DEFAULT_DELIVER_TO_INFO, DEFAULT_LOCATION_INFO, DEFAULT_CURRENCY_INFO, DEFAULT_MOVEMENT_ID, and DEFAULT_BOM_RESOURCE_ID. Together these resolve the document type behind a return and default the corresponding attributes.

Tables Accessed

The package reads and writes receiving and order data through APPS synonyms. It references RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES to identify the original shipment, RCV_SUPPLY for supply source resolution, RCV_TRANSACTIONS for historical transaction context, and RCV_TRANSACTIONS_INTERFACE as the primary staging table it populates. Master data comes from MTL_PARAMETERS, MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, and MTL_TRANSACTION_LOTS_INTERFACE (lot handling). Purchasing data is drawn from PO_HEADERS_ALL, PO_LINES, and PO_LINE_LOCATIONS for RTV scenarios. PO_INTERFACE_ERRORS captures validation failures, and PLITBLM is used for RTV processing. These dependencies confirm the package bridges Purchasing, Inventory, and Order Management data to produce valid receiving transactions.

Usage Notes

RCV_ROI_RETURN is not typically called directly by end users. It is invoked internally by ROI preprocessing and return-transaction packages when records are submitted to the Receiving Open Interface, either through the Receiving Transactions form-adjacent flows, concurrent programs that consume interface records, or custom integration code that inserts into RCV_TRANSACTIONS_INTERFACE. Customizations should treat it as a supporting derivation layer rather than a public API: callers populate source identifiers, and the package derives and defaults the remainder. Because it is referenced by five other packages, changes to its behavior can affect RMA, internal order, and organization transfer flows. In 12.2.2 the documented interface remains stable relative to 12.1.1, and the package should be treated as internal infrastructure when designing interfaces.