Search Results rcv_trx_interface_trx_ins_pkg

Overview

APPS.RCV_TRX_INTERFACE_TRX_INS_PKG is a low-level PL/SQL package in Oracle E-Business Suite that supports the Receiving open interface. Its business function is to insert transaction records into the RCV_TRANSACTIONS_INTERFACE staging table, which serves as the inbound interface between external or internal source systems and the Receiving transaction processing engine. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges and schema context of the calling user rather than the package owner. This is significant because invocation is typically required from a context that already holds the appropriate grants on the RCV_TRANSACTIONS_INTERFACE synonym and related Receiving objects.

The package is documented with the API classification OTHER, indicating that it is not a formally published public API such as the Receiving Transaction Processor, but rather an internal helper used by higher-level interface loading logic. It is a narrow, single-purpose package: its only documented capability is the insertion of a row into the interface table. In EBS 12.1.1 and 12.2.2, the underlying table and Receiving open interface architecture are consistent; the package header carries a legacy CVS identifier (RCVTIR5S.pls, version 115.1), reflecting an older but stable code line that remains available across both releases.

Key Procedures and Functions

The package exposes exactly one documented procedure:

• INSERT_RCV_TRANSACTION — Inserts a single transaction record into the Receiving transactions interface table. The procedure accepts the transaction data through an IN OUT NOCOPY parameter typed as RCV_TRANSACTIONS_INTERFACE%ROWTYPE, allowing the caller to pass a fully populated interface row and to receive back any modifications the routine makes to that row (for example, system-generated or defaulted column values). NOCOPY avoids the overhead of copying the large record structure by reference. Because the metadata does not document an explicit parameter list beyond the rowtype parameter, consumers should treat the interface table structure itself as the contract for the input.

No functions or additional procedures are documented. The package does not perform transaction processing, validation, or submission to the Receiving Transaction Processor; it is strictly an insertion utility.

Tables Accessed

The only documented table referenced by this package, via an APPS synonym, is:

• RCV_TRANSACTIONS_INTERFACE — The Receiving transactions open interface table. The package writes new rows into this table. Each row represents a pending receiving transaction (for example, a receipt, delivery, return, or correction) that will later be consumed by the Receiving Transaction Processor, which validates the data and creates the corresponding records in RCV_TRANSACTIONS and downstream inventory and accounting tables.

No other tables are documented as being accessed. Any defaulting or derivation logic performed by the procedure would rely solely on the values supplied in the rowtype parameter and the structure of the target interface table.

Usage Notes

This package is an internal interface insertion helper rather than an end-user or partner-facing API. It is typically invoked programmatically rather than from a standard concurrent program or form. Practical usage patterns include:

• Custom PL/SQL code or interface loaders that populate the Receiving open interface and need a controlled, packaged insertion point instead of direct INSERT statements.
• Higher-level Receiving interface loading routines that stage rows before the Receiving Transaction Processor is run.
• Conversion or integration scripts migrating receipt data from legacy systems into EBS.

Because the package is classified OTHER and is not documented as referenced by any other package, Oracle does not present it as a supported public API. Customers should generally prefer the documented Receiving open interface tables and the standard Receiving Transaction Processor concurrent program for supported integrations. Direct use of this package should be limited to controlled, well-tested code, with attention to the AUTHID CURRENT_USER behavior, appropriate grants, and correct population of all mandatory columns in RCV_TRANSACTIONS_INTERFACE. Behavior is consistent across 12.1.1 and 12.2.2, as the Receiving open interface model is unchanged between the two releases.