Search Results default_vendor_rcv_line

Overview

APPS.RCV_ROI_TRANSACTION is a PL/SQL package within the Oracle E-Business Suite Receiving (RCV) module, classified in the ETRM repository as an OTHER API rather than a public open interface. It serves as the core transaction-building and derivation engine for the Receiving Open Interface (ROI) flow. When inbound receiving data — such as Advance Shipment Notices (ASNs), internal requisitions, RMA returns, or internal organization transfers — arrives through the open interface tables, RCV_ROI_TRANSACTION is responsible for deriving, defaulting, and validating the attribute values required to construct valid RCV_TRANSACTIONS_INTERFACE records. In effect, it bridges loosely populated interface rows and the fully attributed transactions that the receiving transaction processor requires.

Key Procedures and Functions

The package exposes a large set of documented procedures and functions (79 in total), organized by derivation domain. These are grouped as follows:

• Vendor derivation and validation: DERIVE_VENDOR_RCV_LINE, DEFAULT_VENDOR_RCV_LINE, DERIVE_VENDOR_INFO, and DERIVE_VENDOR_SITE_INFO populate and validate supplier and supplier site context on the receiving line, while VALIDATE_VENDOR_RCV_LINE enforces consistency.
• Purchase order derivation: DERIVE_PO_HEADER_INFO, DERIVE_PO_LINE_INFO, and related logic resolve the correct PO header, line, and shipment references from the interface data.
• ASN and shipment derivation: DERIVE_ASN_HEADER_INFO, DERIVE_ROUTING_HEADER_INFO, DERIVE_ROUTING_STEP_INFO, DERIVE_FROM_ORG_INFO, and DERIVE_TRANSIT_ORG_INFO resolve shipment, routing, and organization context.
• Item derivation: DERIVE_ITEM_INFO and DERIVE_SUBSTITUTE_ITEM_INFO resolve the item and any approved substitute.
• Location and destination derivation: DERIVE_SHIP_TO_ORG_INFO, DERIVE_SHIP_TO_LOCATION_INFO, DERIVE_LOCATION_INFO, DERIVE_DELIVER_TO_PERSON_INFO, DERIVE_DELIVER_TO_LOC_INFO, and DERIVE_FROM_LOCATOR_ID determine ship-to, deliver-to, and locator values.

Collectively these routines derive defaults and validate values before the transaction is accepted for processing.

Tables Accessed

The package reads and writes through APPS synonyms. Core transactional interface tables include RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE, which hold the inbound receiving rows being built and validated. For source context it references RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and the RCV_SHIPMENT_LINE_SV security view, along with PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and PO_DISTRIBUTIONS to resolve purchasing references. Supporting lookups include AP_TAX_CODES, FINANCIALS_SYSTEM_PARAMETERS, FND_NEW_MESSAGES, HXC_TIME_BUILDING_BLOCKS, MTL_CLIENT_PARAMETERS, MTL_ITEM_LOCATIONS, and MTL_ITEM_LOC_DEFAULTS, which supply tax, system parameter, messaging, time, and inventory locator defaults.

Usage Notes

RCV_ROI_TRANSACTION is not typically called directly by end users or by standard concurrent programs; it is invoked internally. The ETRM dependency data shows it is referenced by RCV_ROI_PREPROCESSOR, RCV_RMA_TRANSACTIONS, RCV_INT_ORDER_PP_PVT, RCV_INT_ORG_TRANSFER, and RCV_ROI_RETURN, and it references RCV_ROI_PREPROCESSOR and RCV_SHIPMENT_LINE_SV. This positions it within the Receiving Open Interface processing chain, driven by the Receiving Open Interface concurrent program and related flows. Custom integrations should load data into the RCV interface tables and allow this package to derive and validate values rather than invoking it directly.