Aug 1, 2011

Defining Request Sets


Defining Completion Options
1. In the Upon Completion region of the Submit Request window, check the Save all Output Files checkbox to write your request to a file. If you want to view your report online, you must use this check box.
2. Click the Options button.
Specify additional people to notify using Oracle Workflow, upon completion of this report. You can also specify a language for the person if multiple languages are installed.
3. Select a print style.
4. Use the LOV to select the printers and languages you want used to produce a hardcopy of your report.
5. Enter the number of copies.
6. Click OK.
7. Click Submit Request when you are finished specifying scheduling and completion options.
Finding Your Request Using the Request ID
After your request is submitted, Oracle Applications assigns a request ID to each request submission so that you can identify the results of the request when it is complete.
You can use the request ID to query for your request output in the Requests window. Oracle Applications also assigns a new request ID number to each resubmission of a request and displays the request ID in the log file of the previous request.
Reprinting a Report That Has Already Been Run
1. Navigate to the Requests window.
2. Query your request so that it is displayed as a record in the Requests window.
3. Select the specific request that you want to reprint.
4. To reprint a report, select Tools > Reprint from the menu.
Defining Request Sets
By defining request sets, you can submit the same set of requests regularly by using a single transaction. You use the Request Set window to create and edit request sets. You can also use the Request Set Wizard to create simple request sets.
Organizing Requests with Stages
Request sets are divided into one or more stages which are linked to determine the sequence in which your requests are run. Each stage consists of one or more requests that you want to run in parallel (at the same time in any order). For example, in the simplest request set structure, all requests are assigned to one stage. This allows all requests to run in parallel.
To run requests in sequence, you assign requests to different stages, and then link the stages in the order you want the requests to run.
The concurrent manager allows only one stage in a request to run at a time. When one stage is complete, the next stage is submitted. A stage is not considered complete until all of the requests in the stage are complete. One advantage of using stages is the ability to run several requests in parallel and then move sequentially to the next stage. This enables you to create more versatile and efficient request sets.




No comments:

Post a Comment