The Inventory transaction worker (INCTCW) processing logic problem
For recent 5 years we've been
successfully using the open interface tables (Mtl_Transactions_Interface
& Mtl_Transaction_Lots_Interface) to process material transactions
from our custom Shop Floor Data Collection system. We're on 11.5.9 CU2
OeBS code level.
Our logic looks like this:
1) The Mtl_Transactions_Interface is populated with TRANSACTION_MODE = 2 (Concurrent Processing).
As per documentation transactions marked as concurrent transaction mode are processed by a dedicated transaction worker to explicitly process a set of transactions. The Transaction Manager does not process transactions marked for concurrent processing.
2) Then a dedicated Transaction Worker (INCTCW) is launched from PL/SQL code with fnd_request.submit_request call, and passing TABLE parameter as "1" (where 1 is the interface table, 2 is temp table).
Our logic looks like this:
1) The Mtl_Transactions_Interface is populated with TRANSACTION_MODE = 2 (Concurrent Processing).
As per documentation transactions marked as concurrent transaction mode are processed by a dedicated transaction worker to explicitly process a set of transactions. The Transaction Manager does not process transactions marked for concurrent processing.
2) Then a dedicated Transaction Worker (INCTCW) is launched from PL/SQL code with fnd_request.submit_request call, and passing TABLE parameter as "1" (where 1 is the interface table, 2 is temp table).
0