Search Results save_allocation




Overview
Explore in AI Chat

Overview

GML_MOBILE_MOVE_ORDER is an Oracle EBS PL/SQL package owned by the APPS schema and classified under ETRM as an OTHER API. It belongs to the Oracle Process Manufacturing (OPM) family of GML modules and provides the server-side business logic that drives mobile move order execution in a Process Manufacturing environment. In 12.1.1 and 12.2.2 the package is the programmatic backbone of the mobile move order user interface, allowing warehouse and shop-floor personnel to allocate on-hand inventory to move order lines, record the resulting material transactions, and query the validation lists that constrain what a mobile user may enter.

The package is documented as exposing thirteen public procedures. It combines data-entry helper functions, validation list-of-values (LoV) queries, allocation retrieval, and the allocation save routine that ultimately writes pending inventory transactions. Although the package is not referenced by any other package, it is invoked directly from the mobile move order form and associated application logic.

Key Procedures and Functions

The documented procedures fall into four logical groups:

  • GET_ALLOCATION_PARAMETERS — Retrieves the allocation parameters and rules applicable to a move order, taking allocation class, organization, customer, and ship-to organization context. It returns the grade and a return status.
  • SAVE_ALLOCATION — The central transactional procedure, and the object returned when a user searches for "save_allocation." It accepts the move order line, lot, location, item, warehouse, quantities, transaction unit of measure, grade, reason code, and related context, and persists the allocation as a pending inventory transaction. It returns a status and an error message.
  • AUTO_ALLOCATE — Performs systematic allocation across a move order line, accepting flags for allowable deletion and move order type, and returning row counts, QC grade, detailed quantities, and unit-of-measure information along with status and error message.
  • Validation LoV procedures — GET_SALES_ORDER_LOV, GET_ITEM_LOV, GET_LOCATION_LOV, GET_LOT_LOV, GET_SUB_LOT_LOV, GET_MOVE_ORDER_LOV, GET_DELIVERY_LOV, GET_PICKSLIP_LOV, and GET_REASON_CODE_LOV each return a reference cursor (TYPE t_genref IS REF CURSOR) used to populate mobile form fields. GET_STACKED_MESSAGES returns accumulated messages for display.

Tables Accessed

The package reads and writes inventory, lot, warehouse, and order tables through APPS synonyms. Key tables include IC_TRAN_PND, the pending transaction table written by SAVE_ALLOCATION; IC_LOTS_MST and IC_LOCT_INV for lot and locator on-hand validation; IC_LOCT_MST and IC_WHSE_MST for location and warehouse definition; and IC_ITEM_MST plus MTL_SYSTEM_ITEMS and MTL_CROSS_REFERENCES for item validation. IC_TXN_REQUEST_HEADERS and IC_TXN_REQUEST_LINES hold the move order header and line being fulfilled. OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL support sales order and pick-slip LoVs, OP_ALOT_PRM supplies allocation parameters, SY_REAS_CDS supplies reason codes, and WSH_DELIVERY_ASSIGNMENTS relates deliveries to move order lines.

Usage Notes

GML_MOBILE_MOVE_ORDER is normally invoked from the Oracle Process Manufacturing mobile move order form during interactive allocation and saving, and may be called from custom concurrent programs or wrapper code that automates allocation. Developers customizing or troubleshooting "save_allocation" should note that SAVE_ALLOCATION returns an explicit x_return_status and x_error_msg and writes only to the pending transaction table; the pending rows must subsequently be processed to update on-hand balances. Because the package is not referenced by other packages, its procedures are entry points rather than shared utilities, and callers must supply the full execution context. Always check the return status before proceeding.