How to Prevent OPM Batches from being Closed or Cancelled When They Have Stuck Pending Transactions, or Why Do I Get Error "STUCK_INTER_TRANS_EXIST" or "STUCK_TEMP_TRANS_EXIST" When Trying to Close or Cancel a Batch (Doc ID 1956224.1)

Last updated on MARCH 08, 2017

Applies to:

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

Goal

 Transactions for batches sometimes become stuck, in either mtl_transactions_interface (MTI) or mtl_material_transactions_temp (MMTT). These transactions must either be reprocessed or deleted, depending on the exact situation. Sometimes the transactions need to be re-entered, or other batch data fixed. Once a batch is closed or cancelled, however, stuck transactions cannot be reprocessed, nor can new transactions be entered. Therefore, it would be helpful to prevent batches from being closed or cancelled if they have stuck transactions.

Solution

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