Search Results inv_rcv_txn_interface




Overview
Explore in AI Chat

Overview

INV_RCV_TXN_INTERFACE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the receiving transaction interface and matching logic used during the inbound receipt and delivery cycle. In Oracle EBS 12.1.1 and 12.2.2, receipt processing flows through the RCV open interface before records are validated and transferred into the base receiving tables. INV_RCV_TXN_INTERFACE provides a shared entry point for that validation and matching activity, enabling standard receiving APIs and concurrent processes to apply consistent business rules when interpreting receipt transactions that arrive through the interface.

Based on associated metadata, the package is classified as an OTHER-type API and exposes a single documented procedure, MATCHING_LOGIC. It is also referenced by several other packages, including INV_RCV_DIR_RCPT_APIS (direct receipt), INV_RCV_STD_DELIVER_APIS (standard delivery), INV_RCV_STD_RCPT_APIS (standard receipt), INV_RCV_TXN_MATCH, and, recursively, INV_RCV_TXN_INTERFACE itself. This dependency pattern confirms its role as a common utility underpinning the receiving API stack rather than a standalone user-facing program.

Key Procedures and Functions

  • MATCHING_LOGIC — The sole documented program unit in this package. Its purpose is to perform the matching and validation logic required when processing receiving transactions at the interface stage, so that receipt lines can be reconciled against expected supply and downstream processing can proceed. The metadata does not expose parameter lists for this procedure, and no parameter detail is asserted here.

No additional procedures or functions are documented for this object. The package depends on INV_RCV_COMMON_APIS and the SYS.STANDARD package, indicating that it leverages shared receiving utilities and standard PL/SQL constructs.

Tables Accessed

Documented table references (accessed through APPS synonyms) include:

Usage Notes

INV_RCV_TXN_INTERFACE is typically invoked indirectly rather than called directly by end users. Standard receiving packages such as INV_RCV_STD_RCPT_APIS, INV_RCV_STD_DELIVER_APIS, and INV_RCV_DIR_RCPT_APIS reference it while processing transactions, meaning it is exercised whenever receipts are entered through the Receiving forms, processed by the Receiving Transaction Processor concurrent program, or submitted through standard APIs. Custom extensions that call these receiving APIs may therefore trigger INV_RCV_TXN_INTERFACE transitively. Direct invocation should be avoided; developers should instead rely on the documented parent APIs. Customizations should be validated against both 12.1.1 and 12.2.2, as online patching and code line differences in 12.2.2 may alter the package body even though the object name and ownership remain APPS.