Search Results cancel_operation_plan

Overview

APPS.WMS_ATF_RUNTIME_PUB_APIS is the public PL/SQL package that exposes the Warehouse Management System (WMS) Application Task Framework (ATF) run-time APIs within Oracle E-Business Suite. Its header shows authorship dated 2003 and a version of 1.0, and it is declared AUTHID CURRENT_USER, meaning execution privileges are resolved against the calling schema rather than the package owner. The package governs the life cycle of warehouse operation plans and operation instances — the executable units of work generated when WMS dispatches tasks to operators on the shop floor. It provides the programmatic entry points used to instantiate a plan for an operation, activate and complete individual operation instances, validate operation state against inspection, load, drop, and crossdock flags, split and clean up instances, and cancel, abort, or roll back whole operation plans. In EBS 12.1.1 and 12.2.2 this package is part of the WMS module's integration surface, invoked from forms, concurrent programs, and other ATF-aware packages rather than by end users directly.

Key Procedures and Functions

Eleven documented entry points comprise the public API. INIT_OP_PLAN_INSTANCE creates an operation plan instance for a given document or plan, establishing the run-time context for subsequent activities. ACTIVATE_OPERATION_INSTANCE transitions an operation instance into an active state so operators can begin executing it. COMPLETE_OPERATION_INSTANCE marks an instance as finished and typically triggers task history updates. VALIDATE_OPERATION evaluates operation parameters against the package's inspection, load, drop, and crossdock constants (G_NO_INSPECTION/G_PARTIAL_INSPECTION/G_FULL_INSPECTION and their load, drop, and crossdock equivalents), returning validation outcomes. SPLIT_OPERATION_INSTANCE — the entry point referenced by the user's search — divides an existing operation instance into subordinate instances, enabling work to be redistributed across tasks, equipment, or personnel while preserving plan integrity. CLEANUP_OPERATION_INSTANCE removes transient run-time artifacts associated with a completed or abandoned instance. CANCEL_OPERATION_PLAN, ABORT_OPERATION_PLAN, and ROLLBACK_OPERATION_PLAN provide progressively different terminal behaviors for an entire plan, from orderly cancellation through abnormal termination to reversal of executed work. CHECK_PLAN_STATUS reports the current status of a plan instance. The package maintains a task_id_table_type (a PL/SQL associative array of NUMBER indexed by BINARY_INTEGER) for passing collections of task identifiers, and defines error codes from -20001 through -20011 covering invalid document, plan, and operation instance identifiers, instance existence conflicts, missing tasks, and invalid input.

Tables Accessed

The package reads and writes WMS run-time and inventory tables through APPS synonyms. Dispatched task state is held in WMS_DISPATCHED_TASKS and its history counterpart WMS_DISPATCHED_TASKS_HISTORY. Inventory context is drawn from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_KFV, with subinventory and locator validation against MTL_ITEM_SUB_INVENTORIES, MTL_SECONDARY_INVENTORIES, and MTL_SECONDARY_LOCATORS. Quantity and availability checks reference MTL_ONHAND_QUANTITIES_DETAIL, while transaction staging and confirmation use MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTION_LOTS_TEMP. Move-order lines are inspected in MTL_TXN_REQUEST_LINES, personnel context is resolved through PER_ALL_PEOPLE_F, and FND_NEW_MESSAGES supports messaging. These accesses confirm that the package bridges task-level execution with real inventory and personnel data.

Usage Notes

WMS_ATF_RUNTIME_PUB_APIS is referenced by eleven other packages, indicating it is an orchestration-layer API invoked by internal ATF components rather than a standalone application entry point. Customizations and integrations should call the public procedures only, respect the declared constants rather than hard-coding flag values, and handle the documented error codes. Because the package is AUTHID CURRENT_USER, callers must hold appropriate privileges on the underlying tables. The SPLIT_OPERATION_INSTANCE procedure is the supported mechanism for breaking an in-progress operation into multiple instances during warehouse execution.