Search Results get_pickslip_lov




Overview
Explore in AI Chat

Overview

The APPS.GML_MOBILE_MOVE_ORDER package is a Process Manufacturing (OPM/GML) PL/SQL API that supports mobile move order processing within Oracle EBS 12.1.1 and 12.2.2. It provides the backend logic for handheld and radio-frequency (RF) devices used in warehouse operations, allowing operators to allocate lots, resolve allocation parameters, and record lot movements against move order lines without accessing the full desktop forms. The package is classified as an OTHER API under the APPS schema and encapsulates the validation, defaulting, and transactional logic required to move material between locations while respecting quality grades, lot status, and warehouse rules.

The header comment (GMLMOMBS.pls 120.0) indicates the package originated in the OPM codebase and has been stable since its 120.0 version. It exposes 13 documented procedures, several of which return reference cursors for List of Values (LoV) population on mobile forms. The package is not referenced by any other documented packages, meaning it is intended to be invoked directly by forms, concurrent programs, or custom extensions rather than being called from within the standard API stack.

Key Procedures and Functions

  • GET_ALLOCATION_PARAMETERS — Retrieves allocation setup parameters for a given allocation class, organization, customer, and ship-to organization. It returns the default quality grade for the allocation context. This is the entry point invoked when the mobile user initiates an allocation for a move order.
  • SAVE_ALLOCATION — Persists a single allocation record (lot, location, allocated quantity, grade, lot status, transaction date, reason code, item, line, warehouse, UOMs, and move order line). It returns a status and error message for front-end error handling.
  • AUTO_ALLOCATE — Automatically allocates available inventory to a move order line based on move order type and header. It returns the number of rows created, QC grade, detailed quantities, UOMs, and status/error information.
  • GET_SALES_ORDER_LOV — Returns a cursor of sales orders for the mobile LoV, filtered by organization and sales order number.
  • GET_ITEM_LOV — Returns a cursor of items for a given organization and item number.
  • GET_LOCATION_LOV — Returns a cursor of valid locations filtered by item, warehouse, lot, and whether negative inventory is allowed.
  • GET_LOT_LOV — Returns a cursor of lots for a given lot number, item, and warehouse.
  • GET_SUB_LOT_LOV — Returns a cursor of sub-lots for lot-level inventory.
  • GET_MOVE_ORDER_LOV — Returns a cursor of move orders for mobile selection.
  • GET_DELIVERY_LOV — Returns a cursor of deliveries for move order association.
  • GET_PICKSLIP_LOV — Returns a cursor of pick slips available for move order processing.
  • GET_STACKED_MESSAGES — Returns accumulated error or informational messages generated during allocation processing.
  • GET_REASON_CODE_LOV — Returns a cursor of valid reason codes used when recording lot movements.

Tables Accessed

The package reads and writes several OPM and Oracle Inventory tables through APPS synonyms. Inventory master data is read from IC_ITEM_MST, IC_WHSE_MST, IC_LOCT_MST, and IC_LOCT_INV for item, warehouse, location, and location-inventory validation. Lot and grade data is read from IC_LOTS_MST. Allocation parameters are read from OP_ALOT_PRM. Pending allocation transactions are staged in IC_TRAN_PND, while move order header and lines are read from IC_TXN_REQUEST_HEADERS and IC_TXN_REQUEST_LINES. Reason codes come from SY_REAS_CDS. Cross-reference data and item validation use MTL_CROSS_REFERENCES and MTL_SYSTEM_ITEMS. Sales order linkage reads OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, and delivery association reads WSH_DELIVERY_ASSIGNMENTS.

Usage Notes

GML_MOBILE_MOVE_ORDER is typically invoked from OPM mobile move order forms and RF device interfaces, where each procedure maps to a user action such as querying an LoV, allocating a lot, or saving a movement. The AUTO_ALLOCATE procedure supports barcode-driven, rapid allocation, while SAVE_ALLOCATION handles manual entry. GET_STACKED_MESSAGES allows the mobile UI to surface all accumulated validation errors in a single response. Because the package is not referenced by any other documented package and is not itself an Oracle-supported public API, customizations should call it directly only through supported extension points, and any use of the t_genref cursor type must be handled within the calling application. No invalidation or concurrent-program dependencies are documented.