A. To generate a debug file from the Sales Orders form:
- Set
the following profile options:
OM: Debug Level - set to 5
OM: Debug Log Directory - any directory that can be written to by the database
To check, run the
following SQL statement:
Code:
select value from
v$parameter where name = 'utl_file_dir'
Set profile option
OM: Debug Log Directory at the Site & Application Level.
- In
the Sales Orders form go to Tools -> Debug and select 'Write to a File'
-- or Tools -> Debug and note the the debug file name.
Note: Later versions of the Sales Order form do not have this option. Simply click on Tools and check the Debug box. This will print out a file name - NOTE down this file name (the first letter in the file name is lower case 'L'). - Perform
the action you wish to debug.
- Go
to Tools -> Debug and select 'Turn Debug Off' to complete debugging. Or
on later form versions just uncheck Debug.
- After
you have completed generating the debug file, please set the value of the
profile OM: Debug Level back to 0, otherwise there will be some
performance impact. Retrieve the debug file from the directory specified
in step 1.
B. To generate debug information for a concurrent process:
- Set
the profile option OM: Debug Level to 5. This will cause debug statements
to be generated in the concurrent request log file.
Note: It is best to set this profile at the User level so only the user who submits the concurrent request is impacted, as opposed to all concurrent requests generating debug messages.
C. To retrieve the debug file in 11.5.8 or higher versions:
- To
retrieve the debug file, navigate to Order Management > Run Requests.
Then choose:
Diagnostics: OM Debug File Retrieval.
Parameters: Give the name of the debug file noted in Step 3 above. Only give the file name, not the directory path. Remember the first letter in the file name is lower case 'L'. - To view the
debug and save, navigate to View > Requests > Relevent Request_id
(button). Click View Output > Save file as "filename.txt".
