Search Results gml_rcv_txn_interface




Overview
Explore in AI Chat

Overview

GML_RCV_TXN_INTERFACE is an APPS-owned PL/SQL package body classified under Oracle E-Business Suite as an "OTHER" API type, functioning primarily within the Process Manufacturing (OPM) receiving flow. Its central responsibility is to support the interface between mobile or external receipt capture and the standard Oracle Purchasing and Receiving tables. In EBS 12.1.1 and 12.2.2, receiving transactions commonly originate through Oracle Mobile Supply Chain Applications (MSCA) or OPM mobile receiving, where users scan LPNs, lots, and purchase order references. This package coordinates the matching of inbound receipt data against open purchase order distributions and shipment lines, then stages records into the receiving interface tables so the standard receiving transaction processor can validate and post inventory. The dependencies list confirms its role as a bridge between the mobile receipt layer (GML_MOBILE_RECEIPT), the receiving interface infrastructure (RCV_TRANSACTIONS_INTERFACE), and purchasing reference data. It also uses the FND_API and FND_MSG_PUB error-handling framework, indicating conformance with the EBS API standard for returning success, error, and message stack information.

Key Procedures and Functions

The ETRM metadata documents a single procedure or function for this package:

  • MATCHING_LOGIC — This routine encapsulates the core matching behavior of the package. Its purpose is to associate inbound receipt transaction data with the correct purchasing and receiving records, determining how scanned quantities and identified items align with open purchase order distributions, lines, and shipment references. Rather than performing the final inventory update, MATCHING_LOGIC prepares or resolves the transactional linkage needed before insert into the receiving interface. No parameter list or signature is assumed or inferred from the available metadata.

The package also invokes internal procedures (shown in metadata as a self-reference to GML_RCV_TXN_INTERFACE) and relies on the standard FND_API and FND_MSG_PUB framework for standardized API return status and message propagation.

Tables Accessed

The package reads and writes across purchasing, receiving, inventory, and logistics tables, accessed through APPS synonyms:

Usage Notes

GML_RCV_TXN_INTERFACE is not a public, directly-called business API. It is invoked indirectly through Oracle Mobile Supply Chain Applications and OPM mobile receiving functionality, where the GML_MOBILE_RECEIPT package and related flows drive receipt capture. Customers and integrators typically encounter it only through standard receiving screens or when diagnosing interface processing. Because the metadata shows the package is referenced by two other objects but does not reference any calling application directly, custom code should not invoke it in isolation; instead, custom integrations should populate RCV_TRANSACTIONS_INTERFACE or use supported receiving APIs. The presence of FND_MSG_PUB confirms that error conditions surface through the standard EBS message stack, so debugging generally involves reviewing interface errors and message logs rather than returning custom exception codes. The package remained VALID at documentation time in both 12.1.1 and 12.2.2, and its dependency on RCV_TRANSACTIONS_INTERFACE_SV ties it to the standard receiving transaction validation and processing engine.