Defining Request Groups

Defining Request Groups

Defining Request Groups

We should recall that request security group are used to restrict and group the concurrent reports and programs that we can run. To create a request security group, you attach a request group to a responsibility. (We can also use the request groups to customize the SRS processing or reports, which we will learn about in the next section.) In this section, we will explore defining request groups. We define request groups through the navigation path
Security/Responsibility/Request
This will take you to the Request groups form.

To create a request group, we would first enter the group (request group name)and the application. We may include requests from any application in our request group, regardless of the application attached to our request group. The application name is for informational purpose only. The group and application are both required, and must be unique across Oracle Applications. Next, we can optionally assign a code to the request group. This code is used for a custom SRS form so that only programs or reports in this request group could be processed by the custom SRS form. The code together with the application module also must be unique. As a last step , we can enter an optional description.

Enter requests that are included in the request groups by selecting the type and the request name. The type can be Application, program, Set or stage function. Application means include all concurrent programs and reports within the application. Program and Set mean a particular concurrent request or a particular request set. Function means a particular concurrent request set stage function. Query up the GL concurrent program Group to see the definition of the request group you utilized for our responsibility.