Search Results check_lot_status

Overview

GML_MOBILE_RECEIPT is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Process Manufacturing (OPM/GML) mobile receiving workflow. It provides the server-side logic required by mobile receiving forms and devices to validate lots, present list-of-values (LOV) queries, and stage receiving transactions for insertion into the receiving interface. The package is classified as an OTHER API in the ETRM repository, meaning it is not part of a formally published public API surface but is instead a supporting component used internally by mobile supply chain applications.

The package was originally authored against a GML (Process Manufacturing) codebase and carries a version header dated 2005. It remains present and callable in Oracle EBS 12.1.1 and 12.2.2 installations that include the Process Manufacturing modules. Its central responsibilities include lot and sublot validation, reason code and locator retrieval, unit of measure resolution, PO line and item LOV data retrieval, and the construction of receiving transaction rows.

Because the user query referenced get_po_line_item_num_lov, this package is the documented home of that procedure, which supplies the LOV data set used to select purchase order line and item numbers during mobile receiving.

Key Procedures and Functions

The package exposes twenty documented procedures and functions. The principal ones are described below.

• CHECK_LOT_STATUS — Validates a lot, sublot, item, organization, and locator combination, returning a status and error message to the caller.
• GET_LOT_LOV, GET_SUBLOT_LOV, GET_REASON_CODE_LOV, GET_LOCATION_LOV — Return reference cursors that populate mobile receiving LOVs for lots, sublots, reason codes, and inventory locations respectively.
• INSERT_LOT — Creates a new lot record and returns the generated transaction interface and product transaction identifiers along with status and message outputs.
• GET_PO_LINE_ITEM_NUM_LOV — The procedure directly associated with the user search. It returns a reference cursor of purchase order line and item number values filtered by organization, PO header, mobile form context, PO line number, and inventory item.
• GET_UOM_LOV_RCV and GET_UOM_CODE — Resolve and return valid units of measure for a given item, organization, and UOM type.
• RCV_CLEAR_GLOBAL and CLEAR_LOT_REC — Clear package-level global state and lot record caches between mobile receiving transactions.
• GET_STACKED_MESSAGES — Returns accumulated validation or error messages for display to the mobile user.
• GET_DOC_LOV, GET_ITEM_LOV_RECEIVING, GET_COUNTRY_LOV, GET_SUB_LOV_RCV — Additional LOV data providers for documents, receiving items, countries, and sub-inventories.
• CALCULATE_SECONDARY_QTY — Derives secondary quantity from primary quantity and item conversion data.
• GET_DYNAMIC_LOCATOR and GET_PRJ_LOC_LOV — Retrieve locator and project location LOV data.
• CREATE_LOT — Supports lot creation for receiving staging.

Tables Accessed

The package reads and writes through APPS synonyms across several Process Manufacturing and Oracle Inventory tables.

• IC_LOTS_MST, IC_LOTS_CPG, IC_LOCT_INV, IC_LOCT_MST — Lot master, lot CPG attributes, locator inventory balances, and locator master data used for lot and locator validation.
• IC_ITEM_MST, IC_WHSE_MST, IC_JRNL_MST, IC_ADJS_JNL — OPM item master, warehouse master, and journal/transaction staging tables.
• MTL_MATERIAL_TRANSACTIONS_S, MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, MTL_ITEM_SUB_INVENTORIES, MTL_SECONDARY_LOCATORS — Inventory transaction sequence, locator, subinventory, and locator mapping data.
• MTL_CROSS_REFERENCES, MTL_RELATED_ITEMS — Item cross-reference and related item data used to resolve item and PO line LOV values.

Usage Notes

GML_MOBILE_RECEIPT is typically invoked by Oracle Mobile Supply Chain Application (MSCA) forms and mobile receiving servlets, and is referenced by two other APPS packages in the ETRM repository. It is not intended as a standalone public API. Custom code should treat the procedures as internal, avoid direct calls where a documented receiving API exists, and account for global state by calling RCV_CLEAR_GLOBAL or CLEAR_LOT_REC between transactions. Parameter lists should be confirmed against the deployed package specification for the target release, since this package is classified as OTHER rather than a supported public API.