Search Results rcv_online_request




Overview
Explore in AI Chat

Overview

INV_RCV_MOBILE_PROCESS_TXN is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports mobile receiving transactions within the Oracle Inventory and Oracle Purchasing receiving flow. Its principal business function is to accept receiving data captured through a mobile or wireless device session, validate that data against the Receiving Open Interface (ROI), and convert the captured rows into standard receipt transactions that can be processed and posted by the receiving engine. The package is classified as an OTHER API rather than a public, externally supported interface, which indicates it is intended primarily for internal use by the mobile receiving application layer and related concurrent processing rather than for direct customer invocation.

The header reference INVRCVPB.pls, version 120.6.12010000.1, confirms the package is part of the core Inventory receiving codebase consolidated in the 12.1.1 release and carried forward into 12.2.2. The package interacts closely with the Receiving Open Interface staging tables and temporary inventory tables, and it relies on profile options such as INV_DEBUG_TRACE for diagnostic tracing through INV_MOBILE_HELPER_FUNCTIONS.

Key Procedures and Functions

  • RCV_PROCESS_RECEIVE_TXN — The primary driver procedure. It processes a mobile receive transaction submitted through the receiving interface, validating and converting the staged data into inventory and receiving records. This is the entry point most relevant to callers searching on rcv_online_request, since the online receiving request flow invokes processing logic of this nature to convert interface rows into posted receipt transactions.
  • LOT_UOM_CONVERSION — Handles unit of measure conversion specifically for lot-controlled items, ensuring that quantities captured in a mobile transaction are expressed in the correct inventory or primary UOM before lot assignment and transaction insertion. This matters where the transaction UOM differs from the lot's primary UOM.
  • CHECK_EXISTING_LOT — Determines whether a specified lot already exists in inventory, allowing the mobile process either to reuse the existing lot number or to trigger creation of a new lot record. This is an essential validation step in mobile receiving, where lot entry is often operator-driven and prone to duplication.

In addition, the package body contains internal helper routines such as PRINT_DEBUG and CHECK_GROUP_ID. The CHECK_GROUP_ID function queries RCV_TRANSACTIONS_INTERFACE by group identifier to confirm that a submitted group of interface rows exists before processing proceeds, returning a Boolean result. PRINT_DEBUG conditionally writes trace messages to the log when the INV_DEBUG_TRACE profile option is enabled.

Tables Accessed

  • RCV_TRANSACTIONS_INTERFACE and RCV_HEADERS_INTERFACE — The Receiving Open Interface staging tables. The package reads and updates these to validate group membership, extract transaction and header attributes, and mark rows as processed.
  • MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_TRANSACTION_LOTS_TEMP — Temporary transaction and lot tables used to stage inventory transactions, including lot and UOM details, prior to validation and final posting.
  • MTL_LOT_NUMBERS — The lot master, read and potentially written when new lot numbers are received through mobile entry.
  • MTL_LOT_UOM_CLASS_CONVERSIONS — Conversion factors supporting LOT_UOM_CONVERSION logic for lot-based UOM handling.
  • MTL_UNITS_OF_MEASURE — UOM definitions used to validate and resolve the units of measure attached to incoming transactions.
  • DUAL — Used for scalar evaluations and constant returns within the procedural logic.

Usage Notes

INV_RCV_MOBILE_PROCESS_TXN is not a published, supported public API. It is invoked indirectly by the mobile receiving application and by the online receiving request processing path, and it is referenced by six other packages within the Inventory and Receiving codebase. Developers and support analysts should treat it as internal implementation logic; direct calls from custom code carry upgrade and support risk because the package is not covered by Oracle's external API compatibility guarantees.

Because the package writes to Receiving Open Interface and temporary inventory tables, it must execute within the standard receiving transaction processing context, including correct organization and user context initialization. Debugging is best performed by enabling the INV_DEBUG_TRACE profile option and reviewing the trace output routed through INV_MOBILE_HELPER_FUNCTIONS.TRACELOG. The behavior of the package is consistent across 12.1.1 and 12.2.2, as reflected by the shared file version lineage.