Search Results rcv_process_receive_txn

Overview

The APPS.INV_RCV_MOBILE_PROCESS_TXN package is a server-side PL/SQL API within Oracle E-Business Suite that supports mobile receiving transactions in the Oracle Inventory and Oracle Receiving modules. Its principal business function is to accept inbound receiving data captured through a mobile or handheld device and drive it through the standard EBS receiving interface, ultimately materializing inventory transactions such as receipts into stores. The package is classified under the ETRM "OTHER" API category, indicating it is an internal or utility package rather than a formally published open interface, and it is owned by the APPS schema. The header comment (INVRCVPS.pls 120.1.12010000.1, dated 2008) confirms its lineage as a Release 12 component maintained under the Inventory Receiving source module. Because mobile receiving bypasses several of the validation and defaulting paths available in the desktop Receiving forms, this package consolidates the lot validation, unit-of-measure conversion, and interface-population logic required to submit a reliable receipt through the Receiving open interface. It is referenced by six other packages in the ETRM repository, which reflects its role as a shared processing dependency for mobile receiving flows.

Key Procedures and Functions

ETRM documents three program units in this package:

• RCV_PROCESS_RECEIVE_TXN — The primary entry point for processing a mobile receipt transaction. It orchestrates the end-to-end receive operation, including validation and population of the receiving interface tables so the standard Receiving transaction processor can complete the receipt. It returns status and message data to the caller through its OUT parameters, enabling the calling mobile application to present success or error messages to the user.
• LOT_UOM_CONVERSION — Performs unit-of-measure conversion for lot-controlled items. Mobile devices frequently capture quantities in a secondary or alternate UOM, so this routine translates the entered quantity into the inventory primary UOM for correct lot quantity recording.
• CHECK_EXISTING_LOT — Validates whether a lot number already exists for the item, supporting lot validation, and preventing duplicate or inconsistent lot creation during mobile receiving.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE — the Receiving open interface tables populated with the receipt header and transaction lines that the Receiving Transaction Processor consumes.
• MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_TRANSACTION_LOTS_TEMP — temporary staging tables holding material transaction and lot transaction detail prior to final processing.
• MTL_LOT_NUMBERS — the master lot table, used by lot validation to confirm existing lots.
• MTL_LOT_UOM_CLASS_CONVERSIONS — lot-specific UOM conversion definitions used by the lot conversion routine.
• MTL_UNITS_OF_MEASURE — provides UOM definitions and conversion context.
• DUAL — used for single-row lookups and computational statements.

Usage Notes

This package is typically invoked programmatically rather than from an Oracle Forms window, since it is designed to serve mobile or handheld receiving clients. It may be called from custom PL/SQL code that wraps a mobile receiving front end, from other EBS packages (six packages reference it), or from a concurrent program that drives interface processing in batch. The calling program is expected to supply transaction context and consume the returned status and message outputs to determine whether the receipt succeeded. Because the package writes directly into the Receiving interface tables, callers should follow standard interface conventions: populate valid inventory item, organization, and UOM values, and ensure the Receiving Transaction Processor is subsequently run to convert interface rows into actual receipts. Being an undocumented or internal package, it is not formally supported as an open interface, and customizations should validate behavior against the target release (12.1.1 or 12.2.2) before deployment.