This essay explains how you, as System Administrator, can view and change the status of concurrent requests, and how to view request log and report output files.
Use any of the following methods to view the status and output of concurrent requests.
Use the Requests window to view the status of concurrent requests, and to view request log and report output files.
The System Administrator and Oracle Alert Manager have a privileged version of the Requests window that provides you with more capabilities than your end users. For example, using the Requests window, you can view the status of and log files for all concurrent requests (not just your own), including requests that completed unsuccessfully. On some platforms, you can even view the log files of running requests.
Using the same window, you can view your own report output online. You cannot, however, view report output from other users' requests.
From the Requests window, you can also:
place and remove holds from any pending or inactive request
cancel a pending request, or terminate a running request
restart a request set.
change the priority of any pending request
view the manager log file
determine where any pending request stands in the queue for each manager defined to accept the request
determine when the concurrent manager is inactive and needs to be restarted.
You can run a report that lists parameters and any error messages associated with concurrent requests that have completed running. See: Completed Concurrent Requests Report.
The user profile option Concurrent:Report Access Level determines report output file and log file access privileges for your end users. As System Administrator, you can set this profile option to either "User" or "Responsibility."
All users can can review the log and report output files from requests that they submitted.
If you set the Concurrent:Report Access Level option to "Responsibility" at the User level, that user can also review the log and report output files from all requests submitted from the current responsibility.
If you set the Concurrent:Report Access Level option to "Responsibility" at the Responsibility level, any user of that responsibility can also view the log and report output files from all requests submitted by any other user of that responsibility.
The Oracle E-Business Suite Report File Viewer is used by default for viewing your text report files. You can also display text files in a browser or use another application such as Microsoft Word. You define your default viewer by setting a profile option.
If the Viewer:Text profile option is set to "Browser" then reports are sent to a web browser. If this profile option is left blank, the Report File Viewer is used instead.
If this profile option is left blank, a report or log file can still be viewed in a browser by first viewing it using the Report File Viewer, and then choosing "Copy File..." from the Tools menu.
You can view your reports with HTML output in a browser. Once an HTML report has been sent to a browser, it can be saved to the desktop by using the Save As functionality of the browser.
Note: HTML reports are displayed by the browser in the character set of the server. This character set may or may not match the character set on the client. Therefore, it may be necessary to convert the output to the client character set when saving the report. If the browser supports character set conversion with Save As, there will be a poplist in the Save As dialog box. The user can then choose an encoding which matches the client character set.
You can set up your Online Report Review implementation to enable viewing output files in other applications, such as Microsoft Word or Excel. To do this you associate MIME types with file output formats.
Users can then set their preferred MIME types for particular output formats using profile options, or the users may be prompted to choose the appropriate MIME type for a file at runtime.
You can register more than one MIME type file format with each output format. In the Viewer Options window, you enter in the file format, the MIME type, whether you want to utilize the value of the FND: Native Client Encoding profile option, and a description. The description is displayed to the user in the Profile Values window and the Submit Request form.
If the Allow Native Client Encoding box for the associated MIME type has been checked in the Viewer Options window, the Report Viewer will convert the output file into the character set specified by the profile option FND: Native Client Encoding.
When the report is viewed, it is first sent to a browser. The browser then uses the associated MIME type to display the report.
Attention: For printing, if users choose either HTML or PDF as the output type with Oracle Report programs, they must use appropriate printer drivers to handle the PDF and HTML file for printing their output. See: Overview of Printers and Printing.
Note: For PDF files, the Adobe Acrobat Reader application must have options set as described below:
For Acrobat 4, under File > Preferences > General: uncheck Web browser integration.
For Acrobat 5 and 5.1, under Edit > Preferences: under options, unselect "Display PDF in Browser".
For Acrobat 6 and higher, under Edit > Preferences > Internet: under Web browser options, unselect "Display PDF in browser".