Search Results is_mmtt_record_present




Overview
Explore in AI Chat

Overview

GME_LPN_MOBILE_TXN is a PL/SQL package body owned by the APPS schema that supports the Oracle Process Manufacturing (OPM/GME) Java-based mobile application. Its purpose is to provide server-side transactional logic that a wireless or handheld mobile client can invoke when processing material movements against License Plate Numbers (LPNs). Version 120.2 of the source header is dated December 4, 2005, indicating that the package originates from the earlier GME mobile framework that remains present in EBS 12.1.1 and 12.2.2. The package is classified as OTHER in the ETRM repository, meaning it is not published as a formal public API but is a supporting internal package. It is not referenced by any other database package, so it is consumed directly by the mobile application layer or by custom extensions rather than by inter-package calls.

Key Procedures and Functions

The documented unit exposes eight procedures and functions:

  • NAVIN_DEBUG — a diagnostic helper retained in the source (largely commented out) used to write trace messages during development and troubleshooting.
  • IS_MMTT_RECORD_PRESENT — a Boolean function that determines whether a transaction staging record already exists in MTL_MATERIAL_TRANSACTIONS_TEMP for a given license plate. It joins MTL_MATERIAL_TRANSACTIONS_TEMP to MTL_TXN_REQUEST_LINES and returns the transaction header and temporary identifiers through OUT parameters. It returns FALSE on NO_DATA_FOUND, TOO_MANY_ROWS, or any other exception, making it a defensive existence check before a move order line is transacted.
  • LPN_LOV — supplies the list of values of license plates available to the mobile user, driven from WMS_LICENSE_PLATE_NUMBERS.
  • UPDATE_MO_LINE — updates the move order line (MTL_TXN_REQUEST_LINES) associated with the scanned LPN, typically to reflect quantity, status, or location changes captured on the device.
  • CREATE_MATERIAL_TXN — creates the material transaction, writing into the interface or transaction tables to record the actual inventory movement performed from the handheld.
  • PROCESS_INTERFACE_TXN — submits or processes records held in MTL_TRANSACTIONS_INTERFACE so that staged mobile transactions are validated and posted into inventory.
  • GET_PROD_COUNT — returns a count of production or batch-related records, used by the mobile screens to display available production quantities, referencing GME_BATCH_HEADER and GME_MATERIAL_DETAILS.
  • GET_SUBINV_LOC — returns the subinventory and locator defaults for the mobile session, using item information from MTL_SYSTEM_ITEMS_KFV.

Tables Accessed

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

  • GME_BATCH_HEADER and GME_MATERIAL_DETAILS — process manufacturing batch and material detail data, used to compute production counts and validate batch material movements.
  • MTL_SYSTEM_ITEMS_KFV — the item key flexfield view, used to resolve and display item identifiers for mobile screens.
  • MTL_TRANSACTIONS_INTERFACE — the inventory transactions interface, where mobile-created transactions are staged for validation and processing.
  • MTL_TXN_REQUEST_LINES — move order lines, which are updated and queried to link an LPN to its pending move order line.
  • MTL_MATERIAL_TRANSACTIONS_TEMP — the temporary transaction table queried by IS_MMTT_RECORD_PRESENT to detect an existing staged record.
  • WMS_LICENSE_PLATE_NUMBERS — the license plate master, used to drive the LPN list of values and to validate scanned plates.

Usage Notes

GME_LPN_MOBILE_TXN is invoked from the OPM mobile application rather than from standard EBS forms or concurrent programs. The Java mobile client calls these procedures to render LPN lists of values, validate that a transaction has not already been staged for a plate, update move order lines, and create and process inventory transactions. Because IS_MMTT_RECORD_PRESENT is deliberately defensive — returning FALSE on NO_DATA_FOUND, TOO_MANY_ROWS, and OTHERS — custom code that depends on it should treat a FALSE result as "no reliably single matching staging record" and, where multiple rows are possible, perform additional reconciliation. As the package is not referenced by any other database package, modifications to its logic carry limited blast radius but can directly affect mobile transaction integrity, so changes should be tested against move order and transactions interface processing in both 12.1.1 and 12.2.2 environments.