Search Results get_reason_code_lov

Overview

GML_MOBILE_MOVE_ORDER is an Oracle EBS PL/SQL package owned by APPS and classified as an OTHER API within the ETRM repository. It supports the Process Manufacturing (OPM) mobile move order workflow, providing the server-side logic that allows warehouse personnel to allocate, save, and confirm inventory move order transactions from a mobile or forms-based interface. The package exposes procedures for retrieving allocation parameters, validating and persisting allocation lines, performing automatic allocation, and populating a series of List of Values (LOV) cursors used by the mobile user interface. In EBS 12.1.1 and 12.2.2 the package remains a non-shipped, site-deployed object (the header comment indicates noship), so its presence and behavior depend on the specific implementation rather than on the standard product installation.

Key Procedures and Functions

The package documents thirteen procedures, several of which are LOV providers returning a strongly typed REF CURSOR (t_genref) to the calling form or page. The user search for "get_reason_code_lov" maps directly to GET_REASON_CODE_LOV, which supplies the valid reason codes for a move order allocation adjustment.

• GET_ALLOCATION_PARAMETERS — Retrieves allocation defaults and parameters (such as grade) for a given allocation class, organization, customer, and ship-to organization.
• SAVE_ALLOCATION — Persists a single allocation line, capturing lot, location, quantities, grade, transaction date, reason code, item, and move order line detail, and returning status and error information.
• AUTO_ALLOCATE — Performs automatic allocation for a move order line, optionally deleting existing allocations, and returns row counts and detailed quantity/grade information.
• GET_SALES_ORDER_LOV — Returns a cursor of sales orders for a given organization and 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 inventory locations for an item, warehouse, lot, and negative-inventory setting.
• GET_LOT_LOV and GET_SUB_LOT_LOV — Return cursors of lots and sub-lots matching the supplied item and warehouse context.
• GET_MOVE_ORDER_LOV — Returns a cursor of move orders available for selection.
• GET_DELIVERY_LOV — Returns a cursor of deliveries associated with the move order transaction.
• GET_PICKSLIP_LOV — Returns a cursor of pickslips for the mobile transaction.
• GET_STACKED_MESSAGES — Returns accumulated or stacked error/information messages generated during processing.
• GET_REASON_CODE_LOV — Returns a cursor of valid reason codes, drawn from the SY_REAS_CDS table, for use when a move order allocation requires a reason (for example, an adjustment or variance).

Tables Accessed

The package reads and writes inventory, lot, and move order data through APPS synonyms. IC_ITEM_MST, IC_LOCT_INV, IC_LOCT_MST, IC_LOTS_MST, IC_WHSE_MST, and IC_TRAN_PND support item, location, lot, warehouse, and pending transaction definitions used during allocation and LOV population. IC_TXN_REQUEST_HEADERS and IC_TXN_REQUEST_LINES hold the move order header and line records that are created or updated. OP_ALOT_PRM supplies allocation parameters. SY_REAS_CDS provides the reason codes returned by GET_REASON_CODE_LOV. MTL_SYSTEM_ITEMS and MTL_CROSS_REFERENCES supply item validation and cross-reference data, while OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and WSH_DELIVERY_ASSIGNMENTS link move orders to sales orders and deliveries.

Usage Notes

GML_MOBILE_MOVE_ORDER is normally invoked from the OPM mobile move order forms and from custom extensions that mimic that interface. Because it is not referenced by any other documented package, it is a top-level entry point rather than a shared utility. The LOV procedures, including GET_REASON_CODE_LOV, are called to populate selection lists on the form, while SAVE_ALLOCATION and AUTO_ALLOCATE perform the transactional work. Callers should always inspect the x_return_status and x_error_msg outputs and should retrieve GET_STACKED_MESSAGES when validation fails. Any custom code should be regression-tested against both 12.1.1 and 12.2.2, as the package is a non-shipped object whose source may differ between environments.