Search Results create_mo

Overview

WMS_TASK_DISPATCH_PUT_AWAY is an Oracle Warehouse Management (WMS) package body owned by APPS that governs the directed put-away workflow within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its core business function is to determine, validate, and execute the movement of received inventory from a staging or receipt location to its final storage destination, generating and completing the warehouse tasks that drive this movement. The package supports the dispatching of put-away tasks to warehouse operators, suggests optimal destination subinventories and locators based on put-away rules, and orchestrates the database transactions required to record completed moves.

Beyond basic task dispatch, the package includes logic for lot and serial controlled items. The body declares a record type (msn_attribute_rec_tp) modeled on MTL_SERIAL_NUMBERS, used to capture serial attributes when inserting serial records for serial numbers contained in an LPN. This reflects the FP-J Lot/Serial Support enhancement bundled into the package. The package is classified as OTHER in the ETRM metadata and is referenced by eleven other packages, indicating it is a foundational component of the WMS task execution layer rather than a standalone utility.

Key Procedures and Functions

Eighteen procedures and functions are documented in the package. The user-searched term, CREATE_MO, is a documented procedure that creates the move order header underlying a put-away task. Its companion, CREATE_MO_LINE, creates the corresponding move order line detail for the material to be relocated.

• SUGGESTIONS_PUB — Public entry point that generates put-away suggestions, determining candidate destination locators.
• COMPLETE_PUTAWAY — Finalizes a put-away task once the operator confirms placement, recording the completed move.
• DISCREPANCY — Handles discrepancies encountered during put-away, such as quantity or locator mismatches.
• CHECK_LPN_VALIDITY — Validates that an LPN is eligible for the put-away operation.
• ARCHIVE_TASK — Archives completed or closed task records.
• PUTAWAY_CLEANUP — Cleans up residual task data after completion or cancellation.
• VALIDATE_PUTAWAY_TO_LPN — Validates the target LPN for a put-away.
• CHECK_MMTT_MTL_STATUS — Checks material status against the pending move transaction.
• CLEANUP_PARTIAL_PUTAWAY_LPN — Reconciles LPNs involved in partial put-aways.
• VALIDATE_AGAINST_RULES — Validates candidate locators against configured put-away rules.
• CREATE_USER_SUGGESTIONS — Builds user-facing destination suggestions.
• VALIDATE_LOT_SERIAL_STATUS — Validates lot and serial status for controlled items.
• REVERT_LOC_SUGGESTED_CAPACITY — Reverts capacity consumed by a previously suggested locator.
• CHECK_FOR_CROSSDOCK — Determines whether the receipt should be crossdocked instead of put away.
• INSERT_MSNI_HELPER — Helper that inserts records into the serial number interface.

Tables Accessed

The package reads and writes several core inventory and WMS tables. MTL_MATERIAL_TRANSACTIONS_TEMP and MTL_MATERIAL_TRANSACTIONS_S hold the pending and sequence-side transaction records for completed moves. MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, and MTL_SERIAL_NUMBERS_INTERFACE support serial capture and insertion, while MTL_TRANSACTION_LOTS_TEMP and MTL_TRANSACTION_LOTS_INTERFACE handle lot data. MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES provide destination validation and capacity context, and MTL_RESERVATIONS supports material allocation. MTL_SYSTEM_ITEMS supplies item attributes, MTL_PARAMETERS provides organization-level defaults, MTL_TRANSACTION_REASONS supports discrepancy reasons, and FND_USER identifies the operator or user context.

Usage Notes

WMS_TASK_DISPATCH_PUT_AWAY is typically invoked indirectly through WMS mobile put-away pages, the task dispatch engine, and receiving flows that require directed put-away. Custom code should call only the public entry points (for example, SUGGESTIONS_PUB) and avoid the internal helpers, which assume a specific transaction context. Because eleven other packages reference it, modifications should be regression-tested across the WMS task and receiving stack.