Search Results fetch_material_transactions

Overview

GME_MOBILE_TXN is a PL/SQL package owned by the APPS schema that provides the server-side transaction layer for the Oracle Process Manufacturing (OPM/GME) mobile material transaction application. As stated in its header comment, it is a "PL/SQL Package to support the (Java) GME Mobile Application" and "Contains PL/SQL procedures used by mobile to transact material." The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the package owner, which is consistent with an API layer that inherits invoker security context.

The package abstracts the complexity of OPM batch, lot, and material transaction processing so that the Java-based mobile client can drive shop-floor transactions — material issues, returns, product and byproduct completions, backflush, resource usage, and label printing — without directly manipulating base OPM and Oracle Inventory tables. Internal constants define the transaction type codes used by the mobile application (for example source type 5, issue 35, return 43, product completion 44, product return 17, byproduct completion 1002, and byproduct return 1003), aligning the PL/SQL layer with the enumerated transaction types declared in the companion Java class MaterialTransaction.java.

Key Procedures and Functions

The package exposes 56 documented procedures and functions. Principal entries include:

• CREATE_MATERIAL_TXN — Primary entry point for material transactions; processes reservation and, since Bug 9483781, LPN (license plate number) details associated with a reservation.
• CREATE_LOT_TXN, CREATE_LOT, GENERATE_LOT_NUMBER, VALIDATE_CHILD_LOT, VALIDATE_INDIV_LOT_TXN — Lot creation, numbering, and validation for lot-controlled transactions.
• FETCH_MATERIAL_TRANSACTIONS, FETCH_LOT_TRANSACTIONS, FETCH_AGGREGATED_LOT_TXNS, FETCH_AGGREGATED_REV_TXNS, FETCH_AGGREGATED_TXNS, FETCH_PRODUCT_PENDING_LOTS — Retrieval of transaction, lot, and pending-product data for display in the mobile UI.
• PROCESS_INTERFACE_TXN — Moves staged interface records into the transaction tables.
• VALIDATE_TXN_DATE, VALIDATE_BATCH_FOR_IB, VALIDATE_ITEM_FOR_IB, IS_MATERIAL_STATUS_APPLICABLE — Validation of transaction dates, batch and item eligibility for inventory/backflush processing, and material status applicability.
• BACKFLUSH_MATERIAL, SAVE_RESOURCE_USAGE — Backflush consumption and resource usage recording for batch steps.
• GET_STACKED_MESSAGES, print_label (added per Bug 9367054 for product transaction labels) — Message retrieval and label output.

Tables Accessed

Through APPS synonyms the package reads and writes core OPM batch tables and Oracle Inventory transaction tables. GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ITEMS, and GME_BATCH_STEP_RESOURCES supply batch, step, item, and resource context. GME_MATERIAL_DETAILS, GME_MATERIAL_DISPENSING_GTMP, and GMO_MATERIAL_DISPENSES hold material requirement, dispensing, and dispense data. GME_PENDING_PRODUCT_LOTS and GME_RESOURCE_TXNS support pending product lot and resource transaction processing. On the Inventory side, MTL_MATERIAL_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS_TEMP receive transaction records, MTL_LOT_NUMBERS manages lot numbers, MTL_RESERVATIONS supports reservation and LPN processing, MTL_ITEM_SUB_INVENTORIES validates item/subinventory combinations, and MTL_PARAMETERS supplies inventory organization defaults.

Usage Notes

GME_MOBILE_TXN is invoked by the Java GME Mobile Application through the EBS database connection, and is referenced by one other package within the application. It is not a user-facing form or concurrent program interface itself; instead it functions as an internal API for mobile material transactions. Customizations and integrations should call the documented public procedures rather than modifying base tables, and should respect the reservation, lot, and LPN parameters introduced by the referenced bug fixes. Because the package is AUTHID CURRENT_USER, callers must be granted the necessary privileges on the underlying OPM and Inventory objects.