Search Results rcv_trx_interface_insert_pkg




Overview
Explore in AI Chat

Overview

RCV_TRX_INTERFACE_INSERT_PKG is an Oracle E-Business Suite Receiving (RCV) package owned by the APPS schema and classified as an OTHER API in ETRM documentation. It provides the low-level insertion and maintenance routines used to stage receiving transactions in the RCV_TRANSACTIONS_INTERFACE table before they are processed by the Receiving Transaction Processor. Its primary business function is to accept transaction data sourced from receiving forms, inspection flows, integration points, and warehouse management routines, and to persist that data in the interface table so that validation and final posting to inventory can occur asynchronously.

The package appears in both EBS 12.1.1 and 12.2.2 as a VALID, available object. It is a supporting component rather than a public-facing API, and ETRM records indicate it is referenced by five other packages, confirming its role as a shared internal service within the Receiving application family.

Key Procedures and Functions

ETRM documents two callable subprograms for this package:

  • INSERT_ROW — Inserts a new record into the receiving transactions interface structure. This is the core routine invoked by upstream callers to stage a receipt, delivery, inspection, return, or transfer transaction for downstream processing.
  • UPDATE_SITE_ID — Updates the site identifier associated with an interface record. This supports correction or enrichment of location data affiliated with a staged receiving transaction.

Per the documented metadata, these are the only two procedures/functions exposed by the package. No parameter lists are recorded in the ETRM extract; callers should inspect the package specification or dependent code for exact signatures.

Tables Accessed

The package operates against the following documented tables, referenced through APPS synonyms:

  • RCV_TRANSACTIONS_INTERFACE — The primary staging table for receiving transactions. INSERT_ROW writes here; UPDATE_SITE_ID modifies rows already staged.
  • RCV_TRANSACTIONS_INTERFACE_S — The sequence used to generate unique interface identifiers for newly staged rows.
  • RCV_SHIPMENT_HEADERS — Read to validate or derive shipment-level context for the incoming transaction.
  • MO_GLOB_ORG_ACCESS_TMP — A global temporary table providing organization access context, ensuring the transaction is staged against an authorized inventory organization.

Usage Notes

RCV_TRX_INTERFACE_INSERT_PKG is not intended for direct invocation by end users or by arbitrary custom code. Within Oracle EBS, it is called indirectly. The documented dependent packages — INV_RCV_INTEGRATION_PVT, RCV_INSPECTION_GRP, RCV_TRX_INTERFACE_TRX_INS_PKG, and WMS_PUTAWAY_UTILS — are the typical drivers. This indicates the package is exercised by:

  • The Receiving Open Interface / integration layer (INV_RCV_INTEGRATION_PVT).
  • The inspection handling group (RCV_INSPECTION_GRP) when inspection results are converted into receiving transactions.
  • The dedicated interface transaction insert package (RCV_TRX_INTERFACE_TRX_INS_PKG), which orchestrates bulk staging.
  • Warehouse Management putaway utilities (WMS_PUTAWAY_UTILS), which stage putaway-related transactions.

Note that RCV_TRX_INTERFACE_INSERT_PKG also appears in its own "referenced by" list, indicating recursion or self-invocation for certain code paths. Customers who need to stage receiving transactions programmatically should use the supported Receiving Open Interface (ROI) rather than calling this package directly, because the correct sequence of dependent validations across these companion packages must be preserved. Because the object is delivered as a VALID APPS-owned package, modifications are not supported and are overwritten during patching. Any custom integration should treat this package as an internal implementation detail of the Receiving transaction interface workflow.