Interface Trip Stop Errors with Ex.. in INTORD...querying PO_REQUISITION_LINES_ALL..:oracle.apps.inv.transaction.utilities.InvTrxException (Doc ID 290920.1)

Last updated on AUGUST 21, 2016

Applies to:

Oracle Inventory Management - Version 11.5.9 to 11.5.10.CU2 [Release 11.5 to 11.5.10]
Information in this document applies to any platform.
*** Checked for relevance 02-Nov-2015 ***

Symptoms

Interface Trip Stop fails for an internal order with the following error in the request log:

[16-NOV-04 15:57:25] INV_TXN_MANAGER_PUB: -----Inside process_Transactions-------.trxhdr=11566732
[16-NOV-04 15:57:25] INV_TXN_MANAGER_PUB: MTI Rows cnt before Validation=0
[16-NOV-04 15:57:25] INV_TXN_MANAGER_PUB: Unexpected Error in Validate Group : No Transaction found in MTI
[16-NOV-04 15:57:25] INV_TXN_MANAGER_PUB: *** SQL error User-Defined Exception
[16-NOV-04 15:57:25] INVTXNB: Error from INV worker : error_code : Transaction processor error, err_expl :Ex.. in INTORD...querying PO_REQUISITION_LINES_ALL..:oracle.apps.inv.transaction.utilities.InvTrxException
MTL_ONLINE_TRANSACTION_PUB.process_online returns false
Error Code:Transaction processor error
Error Explanation:Ex.. in INTORD...querying PO_REQUISITION_LINES_ALL..:oracle.ap
ps.inv.transaction.utilities.InvTrxException
Retrieving messages from the stack


The Interface Trip Stop launches the Receiving Transaction Manager with processing mode 'On Line'. To debug the 'On Line' receiving process in order to capture any additional error messages, please do the following:

Profile Option settings :
RCV: Debug Mode: Yes
RCV: Processing Mode: On-line
FND: Debug Log Enabled : Yes
FND: Debug Log Level : Statement
FND: Debug Log Module: po (This must be in lower case)
INV: Debug Trace : Yes
INV: Debug Level : 10
INV: RPC Timeout : 300
INV: Debug file : utl_file_dir/inv_trx.log
where utl_file_dir is one of the directories returned by the foll. query:
select value from v$parameter where name = 'utl_file_dir';

2. Resubmit the stuck record from Transaction open interface form.
3. Go to Help-> Diagnostics-> Logging -> View
4. Login as SYSADMIN
5. Under Main Menu tab, navigate to Preferences -> System Administration
6. Under Diagnostics, navigate to Debug Log Display
7. This should pop up the Find Log page
8. Enter Logging Level : Statement
9. Module to View: po
10. Enter Start Date and End Date for which you want to see the log
11. Only show log for user: Username (user who performed receiving transaction)
12. Press Find
13. You should be able to see the logs with module name: "po.src.xit.pouer.pouerdebug.online"
.
Note: You may want to purge the data for the User to remove the existing debug messages so that the final count after running the flow is smaller and more manageable. Click on Purge log data for this current user session or Purge log data for all sessions belonging to this user as needed. These two options are
also on the Find Log page.

The logfile created with module "po.src.xit.pouer.pouerdebug.online" showed the following additional error:
ORA-20001: GLMCCURB : There is no daily exchange rate defined from RU RVTPT:054

Cause

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