Using Request Set

Using a Request Set

After you define a request set, it becomes your private request set. You can run it as long as you have access to a standard Submit Requests window that does not limit access to specific requests.

Other users can run the request set only if your system administrator assigns the request set to their responsibility’s request group. It is possible to have a request set in your request group that contains individual requests that are not in your request group.

You can only edit request sets that you own. You can add any requests in your request group to the request set. You can delete any request from the request set, regardless of whether that request is in your request group. To update information about an individual request in the request set, however, the request set must be in your request group.

Viewing and Changing Requests

Since all reports, programs, and request sets are run as concurrent requests in Oracle Applications, you can navigate to the Request window to view the progress and output of all your concurrent requests, and you can change aspects of a request’s processing options.

You can use the Request window (summary and detail) to view a list of all the submitted concurrent requests, check whether your request has run, change aspects of a request's processing options, diagnose errors, or find the position of your request in the queues of available concurrent managers.

How to Use the Request Window

1. Upon initial navigation to the Requests window, you are directed to the Find Requests window.

2. Use the Find Requests window to specify the types of requests you want to see. You can choose to view your completed requests, your requests in progress, or all of your requests by selecting the appropriate option group.

In addition, you can look for a particular request using the Specific Requests option group. Use the find criteria fields as you would for any other find window to specify as many or as few details as you need to locate the desired request information. Navigate to the Find Request window.

3. Enter specific criteria in the Find window that appears, or click Find to display all of your requests that you have submitted.

4. Use the Order By poplist to specify the order in which you want your requests displayed.

Performing Concurrent Processing Tasks

You can click various buttons in this window to perform tasks relating to concurrent processing.

•Refresh Data button: The Requests window will not automatically refresh in order to display updated progress of your request. Use this button to requery the lines in the request table.

•Find Requests button: Displays the Find Request window to perform a search for additional requests

•Submit a New Request button: Displays the Submit Requests window to submit a new request to the concurrent manager

•Hold Request and Cancel Request buttons: These buttons illuminate if the concurrent manager has not already begun running the program. You can Hold or Cancel a request by using these buttons. If the request is already running the Cancel button will terminate the request.

•View Details button: Displays the Details window to view detailed information about your request, for example, submission dates, scheduling and other information. If a request has not already run, you can change selected fields so that the updated information will affect your request when it is run by the concurrent manager.

•Diagnostics button: Displays diagnostic information about your request such as when it ran and if it completed successfully.

•View Output button: Displays an online format of your report. 

Note: Reports that produce an output other than a text file (for example HTML or PDF) are displayed in a browser. If you set the profile option VIEWER: TEXT to Browser, your text files are also displayed in a browser as opposed to the Report Viewer. VIEWER: TEXT may also be set to display your output in a text editor such as Microsoft Word, or in a spreadsheet such as Microsoft Excel.

•View Log button: Displays information about the request regarding arguments used and other technical information

•Screen colors help you identify the status of the request.

–Green: Pending, running or scheduled requests

–Yellow: Completed requests with a status of Warning

–Red: Requests that complete with a status of Error.

Phase and Status for a Concurrent Request

The Concurrent Requests Summary window displays a phase and status summary for each concurrent request listed in the window.

A concurrent request has a life cycle consisting of the following phases:

•Pending: The request is waiting to be run.

•Running: The request is running.

•Completed: The request has finished execution.

•Inactive: The request cannot yet be run.

During each phase, a concurrent request has a specific condition or status. The table lists each phase/status combination and describes its meaning in relation to a request.

Pending Phase

A program in the Pending phase can be in one of four statuses:

•Normal: The program is waiting for an available manager.

•Waiting: A child program is waiting for a parent to mark it ready to run.

•Standby: A program is waiting for another incompatible program in the same logical database to complete.

•Scheduled: A program’s scheduled start time has not yet elapsed.