WIP Issue & Completion Transactions Stuck In Mtl_material_transactions_temp Table From Calling Incremental Backflush API

(Doc ID 2140447.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Process Manufacturing Process Execution - Version 12.2.5 and later
Information in this document applies to any platform.


While calling the Incremental Backflush API, the WIP Issue & Completion transaction got stuck in MTL_MATERIAL_TRANSACTION_TEMP tables. This is happening only when ingredients were not reserved in the batches. Whereas from front end everything is working fine & WIP transaction are processed successfully.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms