Duplicate Pending (MMTT) WIP : How To Verify If Pending WIP Completion And Issue Transactions In MMTT Are Duplicates Or Not (Before Resubmitting Or Deleting) (Doc ID 1073279.1)

Last updated on JULY 09, 2024

Applies to:

Oracle Work in Process - Version 11.5.10.2 and later
Oracle Inventory Management - Version 11.5.10.2 and later
Information in this document applies to any platform.
This document includes all versions of 11i and R12 and later

Goal

How to verify if pending WIP completition or issue transactions in the pending transaction table (MTL_MATERIAL_TRANSACTIONS_TEMP - MMTT) are duplicates or not (before resubmitting or deleting)?

Background

The pending transactions table (MTL_MATERIAL_TRANSACTIONS_TEMP - MMTT) is the gateway for all material transactions. This is a temporary table, the final destination of each transaction being MTL_MATERIAL_TRANSACTIONS.
Records are processed from this table into Inventory through the transaction processor. All Inventory transaction forms write directly to this table. Outside applications must write transaction records to MTL_TRANSACTIONS_INTERFACE to be processed through MTL_MATERIAL_TRANSACTIONS_TEMP and the transaction processor by the Transaction Worker concurrent program.

Note : Using the SQLs we cannot really confirm them as duplicates. The above SQLs only tell us there is a pending transaction in MMTT which is very similar to the transaction existing in MMT which was created in very close time proximity. So Users can use the output of the SQL as a guidance to verify if those are really duplicates or 2 transactions which were performed by the users.