Search Results create_material_txn

Overview

GME_LPN_MOBILE_TXN is a PL/SQL package owned by APPS in the Oracle E-Business Suite, classified under the ETRM taxonomy as an OTHER API. The package was authored in 2005 (header revision 120.1, dated 11-Nov-2005 by Navin Sinhi, marked noship) and its stated purpose is to support the Java-based GME Mobile Application. Specifically, it exposes PL/SQL procedures that a mobile client calls to transact material against Oracle Process Manufacturing batches — issuing, returning, and completing material — using License Plate Numbers (LPNs) as the mobile-facing handle for inventory.

The package declares a set of transaction-type constants that mirror the corresponding constants defined in the Java class MaterialTransaction.java, establishing the numeric contract between the mobile layer and the database layer: g_txn_source_type (5), g_ing_issue (35), g_ing_return (43), g_prod_completion (44), g_prod_return (17), g_byprod_completion (1002), and g_byprod_return (1003). These values drive the transaction semantics applied when material movements are created. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling session rather than the definer.

Key Procedures and Functions

• NAVIN_DEBUG — A diagnostic procedure that writes a supplied message, used for tracing activity during mobile transactions. It appears in the source as a commented-out declaration, indicating it was available for development-time debugging rather than production business logic.
• IS_MMTT_RECORD_PRESENT — A Boolean function that determines whether an existing material transaction record exists for a given LPN identifier, returning the associated transaction header identifier and temporary identifier through output parameters. Also present in the source as a commented-out declaration.
• LPN_LOV — Supplies the mobile application's list of values for license plate numbers. It returns a reference cursor (t_genref, a weakly typed REF CURSOR) of LPNs filtered by organization and, optionally, by a supplied LPN number, allowing the mobile UI to present valid plates for the operator's organization.
• UPDATE_MO_LINE — Updates the process manufacturing (MO) line associated with a given LPN identifier and WMS process flag, returning a status string. This maintains the linkage between the mobile transaction and the batch line being consumed or produced.
• CREATE_MATERIAL_TXN — The principal transaction routine. It constructs a material transaction from the mobile-supplied context: organization, batch, material detail line, item, revision, subinventory, locator, transaction quantity and unit of measure, plus secondary quantity/UOM and the item's primary UOM.
• PROCESS_INTERFACE_TXN — Processes the staged rows that CREATE_MATERIAL_TXN places in the transaction interface, moving them into the inventory transaction tables.
• GET_PROD_COUNT — Returns production/batch count information used by the mobile screens.
• GET_SUBINV_LOC — Retrieves valid subinventory and locator combinations for the organization, supporting mobile data entry validation.

Tables Accessed

• GME_BATCH_HEADER — The process batch definition; supplies the batch context for completions, returns, and material consumption.
• GME_MATERIAL_DETAILS — Batch material requirement/detail lines; identifies which line a mobile transaction applies to and is the target of UPDATE_MO_LINE.
• MTL_SYSTEM_ITEMS_KFV — The key-flexfield item view; used to resolve and validate item attributes such as primary UOM and revision control.
• MTL_TRANSACTIONS_INTERFACE — The staging table into which CREATE_MATERIAL_TXN inserts and from which PROCESS_INTERFACE_TXN pushes rows to inventory.
• MTL_TXN_REQUEST_LINES — Move-order lines, referenced to support material movement requests associated with the mobile transaction.
• WMS_LICENSE_PLATE_NUMBERS — The Warehouse Management license plate master; the source for LPN_LOV and the key to resolving LPN identifiers supplied by the mobile device.

Usage Notes

GME_LPN_MOBILE_TXN is not invoked by other PL/SQL packages; the metadata records zero referencing packages. Its callers are external — the Java GME Mobile Application, which connects as APPS and invokes these procedures over the database session. Because the package is AUTHID CURRENT_USER and classified as OTHER rather than a published open interface, it should be treated as an internal, mobile-only integration point. Customizations should avoid calling it directly where a supported OPM or inventory API exists. The transaction-type constants must remain synchronized with MaterialTransaction.java, since any divergence in the numeric codes would silently misclassify mobile transactions. The package predates 12.1.1 and 12.2.2 and remains unchanged in both releases, so behavior is consistent across those versions.