Search Results wms_operation_type

Overview

APPS.WMS_GLOBALS is a declarative PL/SQL specification package in Oracle Warehouse Management (WMS), shipped as part of the Oracle E-Business Suite. It is defined with AUTHID CURRENT_USER, meaning its unqualified references resolve against the invoker's schema rather than the package owner's schema. The package body, if present, carries no business logic of consequence; WMS_GLOBALS serves almost entirely as a central repository of named constants used throughout the WMS and Inventory modules.

The source header identifies revision 115.11, dated 2004/05/10, indicating that the specification has remained stable across the 12.1.1 and 12.2.2 releases. Its abstraction purpose is to eliminate hard-coded "magic numbers" from warehouse logic: instead of embedding literals such as 1 or 4 when referring to an LPN context or a task type, developers reference the symbolic constant. This improves readability and centralizes the definition of enumerations that are shared by many packages.

The user search term g_op_type_drop corresponds to the WMS_OPERATION_TYPE enumeration that begins in the documented source with G_OP_TYPE_LOAD CONSTANT NUMBER := 1;. The g_op_type_drop constant is the counterpart value used to denote a drop operation, and it is referenced wherever WMS must distinguish between load and drop activity — most notably in LPN movement, putaway, and task execution flows.

Key Procedures and Functions

The ETRM metadata for 12.2.2 documents no procedures or functions in APPS.WMS_GLOBALS. This is consistent with its role as a constants-only specification. The package exposes no callable subprograms; consumers reference its public constants directly.

The documented constants fall into several enumerations:

• LPN context values — LPN_CONTEXT_INV (1), LPN_CONTEXT_WIP (2), LPN_CONTEXT_RCV (3), LPN_CONTEXT_STORES (4), LPN_CONTEXT_PREGENERATED (5), LPN_CONTEXT_INTRANSIT (6), LPN_CONTEXT_VENDOR (7), LPN_CONTEXT_PACKING (8), LPN_LOADED_FOR_SHIPMENT (9), LPN_PREPACK_FOR_WIP (10), and LPN_CONTEXT_PICKED (11). These describe where a license plate number currently resides or what state it occupies, including the temporary packing context used when reassociating an LPN with a different license plate number or container item.
• WMS task types — g_wms_task_type_pick (1), g_wms_task_type_putaway (2), g_wms_task_type_cycle_count (3), g_wms_task_type_replenish (4), g_wms_task_type_moxfer (5), g_wms_task_type_moissue (6), g_wms_task_type_stg_move (7), and g_wms_task_type_inspect (8). These classify the work performed by the warehouse task engine.
• LPN control subtypes — g_lpn_controlled_sub (1) and g_non_lpn_controlled_sub (2).
• WMS operation types — beginning with G_OP_TYPE_LOAD (1) and continuing with the drop counterpart searched by the user, g_op_type_drop.

Tables Accessed

The ETRM metadata lists no tables referenced through APPS synonyms. Because APPS.WMS_GLOBALS is a specification of constants, it performs no DML and issues no SELECT statements. Any table access associated with WMS processing occurs in the consuming packages — for example, the LPN context values are interpreted against the tables that describe license plates, locators, and tasks, but those reads happen in the callers, not within WMS_GLOBALS itself.

Usage Notes

WMS_GLOBALS is referenced by 24 other packages according to the ETRM metadata, making it one of the more widely depended-upon low-level objects in the WMS schema. Typical consumers include packages handling LPN transactions, task dispatch, putaway and picking rules, and receiving integration.

Because the constants are declared in the package specification rather than the body, they are public and available to any schema granted EXECUTE on APPS.WMS_GLOBALS. Custom code that manipulates LPNs or WMS tasks should reference these constants instead of literal values to remain aligned with Oracle's internal enumerations. It should be noted that, being a specification, changes to constant values would require recompilation of dependent packages; the long-standing revision number suggests Oracle treats these enumerations as frozen interface values. In Oracle EBS 12.1.1 and 12.2.2 the package is invoked implicitly by the standard WMS forms and concurrent programs, and it is not itself exposed as a user-facing API.