Search Results complete_tm_processing

Overview

WMS_ATF_UTIL_APIS is a utility PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Warehouse Management System (WMS) module that supports Advanced Task Framework (ATF) processing. The package exposes public procedures that govern the lifecycle of operation plans associated with task execution, principally the assignment of operation plans to tasks and the completion of task execution once inventory transactions have been processed. Its header identifies the package as AUTHID CURRENT_USER, meaning procedures execute with the privileges of the calling schema rather than the definer, a characteristic typical of utility APIs invoked from both standard EBS transaction flows and customer extensions. In the context of Oracle EBS 12.1.1 and 12.2.2, the package plays a supporting role in coordinating Warehouse Management task execution with the Inventory Transaction Manager (TM), ensuring that operation plans are correctly opened, tracked, and closed as material movements flow through the system.

Key Procedures and Functions

ETRM documents two public procedures for this package:

• ASSIGN_OPERATION_PLAN — Associates an operation plan with a task and, optionally, an activity type and organization. It is the entry point used when a task must be linked to the operation plan that governs its execution, establishing the relationship that subsequent transaction processing depends upon. The procedure uses the standard EBS API convention of version, initialization, and commit parameters together with validation level and the standard OUT parameters for return status, message count, and message data.
• COMPLETE_TM_PROCESSING — Concludes the execution of an operation plan after the Inventory Transaction Manager has finished handling a transaction. Its documented contract states that the Transaction Manager should call this API after processing a transaction, before deleting the MMTT record, and when MMTT.OPERATION_PLAN_ID is not null. Inputs distinguish whether a single MMTT within a batch succeeded or failed, and the procedure accepts the mode in which TM was invoked (online, background, or concurrent). The documented parameters include organization identifier, transaction header and batch identifiers, transaction temporary identifier, and the TM completion status, alongside the standard return status, message count, and message data outputs.

Tables Accessed

According to the documented metadata, the package references the following tables through APPS synonyms:

• MTL_MATERIAL_TRANSACTIONS_TEMP (MMTT) — The temporary transaction staging table. The completion API is expressly designed to be called before MMTT rows are deleted, using MMTT identifiers and the OPERATION_PLAN_ID column to determine whether operation plan completion is required.
• RCV_TRANSACTIONS — The receiving transactions table, referenced in support of receipt-related task and operation plan processing.
• WMS_DISPATCHED_TASKS — The table holding dispatched warehouse tasks; operation plan assignment and completion logically operate against the tasks recorded here.
• DUAL — Used for single-row PL/SQL evaluations and trivial queries within the package body.

Usage Notes

COMPLETE_TM_PROCESSING is not intended for direct end-user invocation. Its documented contract assigns the caller role to the Inventory Transaction Manager, which must call it after transaction processing, before deleting the corresponding MMTT record, and only when the operation plan identifier is populated on that record. The completion status parameter communicates whether TM processing succeeded, and the processing mode parameter indicates the invocation context. ASSIGN_OPERATION_PLAN is similarly a programmatic entry point used during task dispatch and operation plan setup, rather than a form-driven action. The package is referenced by two other packages within the EBS codebase, confirming it operates as a shared internal utility. Because it is AUTHID CURRENT_USER, custom code that calls these procedures must ensure appropriate privileges on the underlying WMS and inventory objects, and any extension invoking the completion API must replicate the TM sequencing rules exactly to avoid orphaned operation plans or premature deletion of MMTT rows.