Search Results cleanup_task

Overview

APPS.WMS_TXNRSN_ACTIONS_PUB is a public PL/SQL package body in the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The suffix _PUB denotes that this is a published, externally callable API layer intended for consumption by other Oracle applications, forms, and customer extensions, as opposed to a private utility package. The package governs transaction-reason-driven actions executed against warehouse tasks and inventory exceptions—situations where a mobile or RF transaction cannot complete cleanly because of insufficient quantity, an unavailable locator, or a serial/lot discrepancy. Its principal role is to record the exception, apply the appropriate transaction reason, and either resolve the task in place or route it for follow-up processing. The header comment ($Header: WMSTRSAB.pls 120.6.12000000.5 2007/10/23) indicates the source has been stable since the 11i/12.0 lineage, and it is referenced by seven other packages within the application, confirming its position as a shared integration point.

Key Procedures and Functions

The documented package exposes seven public procedures and functions, of which five are named in the ETRM metadata.

• INADEQUATE_QTY — Handles the business case in which the quantity picked or staged is less than the quantity demanded by the task. It captures the shortfall, accepts quantity and UOM values, an optional carton identifier, the responsible user, and a reason identifier, and returns the standard FND_API return status, message count, and message data. The body declares local variables for message count, return status, message data, carton, user, picked quantity, and picked UOM.
• SUGGEST_ALTERNATE_LOCATION — Proposes an alternative locator when the current location cannot satisfy the transaction, supporting the re-routing of warehouse work without manual intervention.
• LOG_EXCEPTION — Writes an exception record into the WMS exception tables, providing the audit trail that subsequent dispatching or resolution processes consume.
• CLEANUP_TASK — Declared in the package specification with parameters for temp ID, quantity reason ID, user ID, employee ID, a workflow-invocation flag, and the standard three OUT parameters. It reverses or tidies task state after an exception has been handled.
• PROCESS_EXCEPTIONS — The central driver invoked by the user's search term. It evaluates outstanding exceptions and applies the transaction reason logic that determines whether a task should be completed, cancelled, or escalated.

An internal debugging helper, MDEBUG, and a package-level trace flag driven by the INV_DEBUG_TRACE profile option (and inv_mobile_helper_functions.tracelog) support diagnostics across all entry points.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• WMS_EXCEPTIONS / WMS_EXCEPTIONS_S — The primary exception repository where LOG_EXCEPTION and PROCESS_EXCEPTIONS persist and retrieve exception records.
• WMS_DISPATCHED_TASKS — Provides the task context (task, organization, status) against which exceptions and cleanup actions are applied.
• MTL_TXN_REQUEST_HEADERS / MTL_TXN_REQUEST_LINES — Source of move-order demand used to evaluate inadequate quantities and alternate-location decisions.
• MTL_ONHAND_QUANTITIES_DETAIL, MTL_RESERVATIONS — Used to determine available quantity and existing reservations when validating or re-sourcing a task.
• MTL_SYSTEM_ITEMS, MTL_TRANSACTION_REASONS — Item attributes and the reason codes applied to exception transactions.
• MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP — Staging and final transaction records for the inventory movement that results from resolving an exception.
• MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, MTL_SERIAL_NUMBERS_TEMP, MTL_TRANSACTION_LOTS_TEMP — Lot and serial validation and staging for controlled items involved in the exception.

Usage Notes

WMS_TXNRSN_ACTIONS_PUB is normally invoked from the WMS mobile/RF transaction flows and from Oracle Warehouse Management forms when an operator reports a short pick, wrong locator, or similar discrepancy. Because it is a _PUB API, it is also a supported entry point for custom PL/SQL and for concurrent programs that batch-process open exceptions; callers should follow the standard FND_API conventions, honoring p_api_version_number, p_init_msg_lst, and p_commit, and checking x_return_status for g_ret_sts_success, g_ret_sts_error, or g_ret_sts_unexp_error. Diagnostic output can be enabled through the INV_DEBUG_TRACE profile option. Given its wide dependency footprint, changes to this package should be regression-tested against the seven packages that reference it.