1/17/2018 Document 148651.

PowerView is On [My Core Products] Product Line: Internal ... ERP (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates

Give Feedback...

INV DEBUG: How to get Debug Information for Inventory Material Transactions (Doc ID 148651.1) To Bottom

In this Document Was this document helpful?

Goal Yes
No
Solution
Enabling Debug
Document Details
Disabling Debug
About the Profiles
Type:
Other Tips Using Debug HOWTO
Status:
PUBLISHED
Profile Configuration Last Major
Update: 27-Jul-2016
References Last 07-Sep-2017
Update: English
Language:
APPLIES TO:
Related Products
Oracle Inventory Management - Version 11.5.10.2 and later
Information in this document applies to any platform. Oracle Inventory Management
This document includes all versions of Oracle E-Business Suite 11i and Release 12
Information Centers
Information Center: Oracle
Inventory Management
[1381258.2]

GOAL
Document References
How to get Inventory (INV) debug information for material transactions? No References available for
this document.

SOLUTION
Recently Viewed

Summary: The inventory debug profiles are found searching on INV%ebug% including "INV: Debug Trace", "INV:Debug Level", INV DEBUG: How to get
and "INV: Debug file". Here is an example of the common inventory debug profile settings that you might make: Debug Information for
Inventory Material
INV: Debug Trace: Yes Transactions [148651.1]
INV:Debug Level: 15 R12: ''Online Accounting
INV: Debug file: /usr/tmp/invdebug.log Could Not Be Created For
This Transaction'' On Create
Accting [745232.1]
Note: Remember to include a valid directory and filename. Also set the debug at the least intrusive level possible to reduce Not Able To Create Online
impact on the system. For example, we suggest setting at the User level. Accounting For PO Receiving
Transactions [752804.1]
R12: "Online accounting
Action Details: could not be created for this
transaction." [1901835.1]

Enabling Debug
APP-SQLAP-10304 Cannot
Close Period And No Data
On Period Exception Report
[1479903.1]
Take the following steps to enable the inventory debug:
Show More
1. Navigate to system administrator > Profiles > System.

Note: Another navigation is via Edit > Preferences > Profiles.

2. Query for INV%ebug% at the appropriate level -- For example, user level:

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=352641416706091&id=148651.1&_afrWindowMode=0&_adf.ctrl-state=15g1dgk… 1/4
1/17/2018 Document 148651.1

3. Set the inventory debug profiles being sure to enter a valid directory and filename for the debug file profile (*):
INV: Debug Trace: Yes
INV:Debug Level: 15
INV: Debug file: /usr/tmp/invdebug.log

Note: (*) INV: Debug file (Including the complete path): must be a valid path (directory) and filename. The directory must
exist in the "UTL File" listing that you can review with the sql :

SELECT value FROM v$parameter WHERE name = 'utl_file_dir';

5. After setting the above system profile values, bounce the Process Transaction Manager to make sure that the new system
profile values are utilized.

Bounce the Process Transaction Manager

a. Cancel it from Sysadmin / view requests / specific / enter 'Process transaction interface' in Name field and click find
b. Launch concurrent request "Process Transaction Manager" from Inventory > Setup > Transactions > Interface managers >
Click on Material Transaction Manager > Tools -> Launch > Accept Defaults > Ok

6. Resubmit the transactions for processing to capture the process and error messages in the log.

7. Unset debug: Please be sure to set the INV: Debug Trace: No, once your trace is created and your test is completed. Leaving
the debug on can cause performance issues when processing transactions.

Disabling Debug
To disable debug, set the profile to no: INV: Debug Trace: No

1. Navigate to system administrator > Profiles > System.

2. Query for INV%ebug% at the appropriate level -- For example, user level.

3. Change the debug trace to no:

INV: Debug Trace: No

About the Profiles

There are three profiles related to inventory debug. They are used together.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=352641416706091&id=148651.1&_afrWindowMode=0&_adf.ctrl-state=15g1dgk… 2/4
1/17/2018 Document 148651.1
INV: Debug Trace: set Yes to turn on the debug functionality. Set No to turn off the debug functionality.

INV:Debug Level: set 0 , will print the summary debug messages.

Set to 11, to print the detail debug messages.
Set to 15 for more details
Set to 102 for maximum information (may create a VERY large log file)

(*) INV: Debug file (Including the complete path): The path is one of the directories from the valid directories defined in the
obtained v$parameter through the following sql :

SELECT value FROM v$parameter WHERE name = 'utl_file_dir';

Make sure to include the file name at the end of the path, e.g. '/usr/tmp/trx_mgr.log',
'/home/globsupt/log_file_jan_26.log'

While setting debug, consider the impact where you set the profile. A site setting will impact all users of the system while a
user setting has the least impact because the messages are focused on the one user. The level depends on your needs but
we usually recommend setting the profile values at user level.

When the profile option 'TP:INV Transaction processing mode' is set to Background, the debug messages will be printed in the
system request log file and may be reviewed under View > Requests.

When the profile option 'TP:INV Transaction processing mode' is set to Online, the debug message will be put into the user-
specified file, e.g. '/usr/tmp/trx_mgr.log'

Other Tips Using Debug

1. Inventory debug messages may be generated in a number of applications and programs even if they are not necessarily
inventory applications. For example, work in process (WIP) may call an inventory API that could generate inventory debug
messages.

2. Inventory debug messages could be generated via the transaction processing as discussed above, BUT also some form
navigation results in debug messages.

3. Important clues for debugging may also be found in the trace file. Also see Note 296559.1 Tracing FAQ: Common Tracing
Techniques within the Oracle Applications 11i (Trace). Note that if you can generate trace with binds that you might also see
the debug messages in the raw trace file as well.

Profile Configuration
If you have issues setting the debug profiles, you might want to review the configuration of the profiles in the Application
Developer responsibility.

Note: If having issues collecting the Inv debug, you should verify that the Profile INV: Debug Trace is properly setup.

Steps:

a. Navigate to Application Developer (responsibility) > Profiles (Menu)

b. Query the profile name field: INV_DEBUG_TRACE
c. You will see the profile details that should match the screen shot.
Name: INV_DEBUG_TRACE
Application: Inventory
User Profile Name: INV: Debug Trace

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=352641416706091&id=148651.1&_afrWindowMode=0&_adf.ctrl-state=15g1dgk… 3/4
1/17/2018 Document 148651.1
Here is a screen shot showing the way it should show here.

Didn't find what you are looking for? Ask in Community...

Related
Products
Oracle E-Business Suite > Logistics > Logistics > Oracle Inventory Management

Keywords
DEBUGGING; INV; INV_DEBUG_TRACE; LOG FILE; MATERIAL TRANSACTIONS; OPM_PIC_DEBUGOTHER; PROFILE; PROFILE VALUES; TRACE
Translations
English Source Chinese 简体中文 Korean 한국어

Back to Top
Copyright (c) 2018, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=352641416706091&id=148651.1&_afrWindowMode=0&_adf.ctrl-state=15g1dgk… 4/4