Last updated on FEBRUARY 22, 2017
Applies to:Oracle Shipping Execution - Version 12.1.3 and later
Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.
Form: INVTVPTX.fmb - Inventory Transaction Open Interface
Form: INVTVTXN.fmb - Inventory Material Transactions
Concurrent: INCTCM - Process transaction interface
Concurrent: INCTCW - Inventory transaction worker
Concurrent: WSHINTERFACE - Interface Trip Stop
Concurrent: WSHINTERFACES - Interface Trip Stop - SRS
When attempting to reprocess a transaction that was stuck in the Inventory Transaction Open Interface form (INVTVPTX), the new attempt failed too and the form is now showing Error Code = 'Oracle error'.
This Error Code 'Oracle error' appears in the request log of the Interface Trip Stop concurrent program (WSHINTERFACES) for a run to reprocess a failed delivery.
Any attempt to resubmit the stuck transaction is unsuccessful.
The problem can occur with any kind of material transaction submitted to the material transaction interface manager:
- transactions originated in other products of the eBusiness suite (Order Management / Shipping Execution, Work in Process, etc.),
- transactions imported into table MTL_TRANSACTIONS_INTERFACE through a custom loader script.
Case of the Interface Trip Stop request log:
1. Navigate to Inventory: (N) Transactions : Transaction Open Interface
2. In Find Interface Transactions:
Keep Process Flag=Error (defaulted)
Do not populate the field Error (because it is the Error Explanation, not the Error Code)
3. In Transaction Interface window:
In the first tabbed region "Error":
Scroll right and review the field Error Code
If too many records got retrieved, then you may refine as below:
Press F11 key (Enter Query Mode)
Set Error Code=Oracle error
Press CTRL-F11 key (Execute Query)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms