Search Results update_tree_flex_lot

Overview

APPS.WMS_TASK_LOAD is a Warehouse Management System (WMS) PL/SQL package that drives the load-confirmation engine used by Oracle Warehouse Management within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal responsibility is to persist the results of material-handling tasks executed by warehouse operators, translating user-confirmed quantities, license plate numbers (LPNs), lots, serials, and subinventory or locator selections into inventory transaction records. The package underpins the "Tasks loaded successfully" confirmation message returned to operators upon completion of a load, split, or merge action performed at the RF or desktop interface.

Beyond single-task confirmation, the package supports split and consolidation logic, quantity conversion between confirmed, secondary, and suggested units of measure, and validation of LPN, lot, and serial constraints before transactions are committed. The header comment identifies the source file as WMSLOADS.pls and classifies the package as an API-style construct of type OTHER, invoked by WMS execution flows rather than by name in the standard concurrent manager.

Key Procedures and Functions

• TASK_LOAD — The primary driver procedure. It accepts an action code that selects the operational mode (LOAD_SINGLE, LOAD_MULTIPLE, SPLIT, or UPDATE_LOADED) and processes the confirmed transaction parameters, including organization, item, revision, quantities, lots, serials, LPN identifiers, and transaction type context. It is the entry point that ultimately causes the "Tasks loaded successfully" outcome.
• TASK_MERGE_SPLIT — Handles merge and split handling of LPN contents during task execution.
• PROC_CONVERT_QTY_TO_SUGG_UOM — Converts confirmed quantities into the suggested unit of measure to keep transactional and presentation quantities aligned.
• POPULATE_LOT_LOV — Populates the lot list of values for the loading interface.
• LPN_MATCH and LOOSE_MATCH — Perform LPN matching against expected or loosely associated content when validating loaded material.
• CAN_PICKDROP — Determines whether a pick or drop operation is permitted for the given context.
• CHECK_PACK_LPN — Validates packing LPN relationships prior to load confirmation.
• VALIDATE_PICK_TO_LPN and VALIDATE_SUB_LOC_STATUS — Validate LPN pick targets and subinventory/locator status respectively.
• INSERT_SERIAL — Inserts serial number records into the temporary serial structures during load processing.
• CHECK_IF_LOT_IS_SUBSTITUTED — Determines whether a lot has been substituted, enforcing lot substitution rules.
• ITEM_LOT_DIVISIBLE_FLAG — Reports the lot-divisible attribute of the item for quantity-splitting decisions.
• UPDATE_TREE_FLEX_LOT — Maintains lot descriptive flexfield hierarchy values after loading.
• PROCESS_F2 — Supporting processing routine used in the load confirmation flow.

Tables Accessed

The package reads and writes a defined set of APPS-synonym tables. On-hand and reservation data are drawn from MTL_ONHAND_QUANTITIES_DETAIL and MTL_RESERVATIONS, while allocation staging uses MTL_ALLOCATIONS_GTMP. Item definitions, revisions, and descriptive attributes are sourced from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_KFV. Lot validation relies on MTL_LOT_NUMBERS, and serial tracking uses MTL_SERIAL_NUMBERS and MTL_SERIAL_NUMBERS_TEMP. Transaction documents and temporary transaction lines are held in MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTION_LOTS_TEMP, with transaction type context derived from MTL_TRANSACTION_TYPES. Locator and subinventory validation reference MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES.

Usage Notes

WMS_TASK_LOAD is not exposed directly to end users. It is invoked by the Oracle Warehouse Management execution forms and RF transactions when an operator confirms a load, and by any custom WMS extension that must post task-loading results. Because the package emits no "Tasks loaded successfully" text itself, that message originates in the calling WMS form or mobile framework after TASK_LOAD completes without exception. The ETRM metadata records zero dependent packages, indicating no other shipped code invokes it by name; customizations should therefore call it only through supported WMS extension points to preserve upgrade safety across the 12.1.1 to 12.2.2 boundary.