Your situation: You are in support. A user has raised an urgent support ticket that a concurrent request has errored out - other than the concurrent request number, no other details have been provided. Its late at night and you cannot get hold of the user to get further details from the "View Log" and "View Output". You need a way to view the log and output, without asking the DBA to send across those files. What do you do from here?
The 11i profile option - Concurrent:Report Access Level - no longer applies in R12. This has been replaced by Role Based Access Control - RBAC in short.
If you are already familiar with RBAC and wish to setup advanced controls around which users can share outputs, then MOS Note ID 736547.1 is a good place to start.
However, if your requirement is simple - you have business users running concurrent programs, and as part of support team, you simply want to query the concurrent program they have run and view the log and view output - then follow the simple steps below.
The goal here is - from under the "System Administrator" responsibility, you should be able to view the log and output for concurrent programs submitted by ANY user. If you do not have this responsibility (i.e. if you are a business user), you will only be able to query programs that have been submitted by you.
Step 1: Through the Functional Administrator responsibility, using the "Grants" tab, search for Object: Concurrent Requests and click on Go
Step 2: You have a delivered grant called XDO Concurrent Request Security. Click on the Duplicate icon, which will readily create a duplicate of this grant.
Step 4: Click the "Next" button
Object: Concurrent Requests
Data Context Type: All Rows. All Rows indicates access to ALL concurrent program logs and outputs. If you want access to be shared for only a limited set of concurrent programs, you can achieve this be selecting the Data Context Type as Instance Set. Definition of Instance Set is not part of scope of this blog. The MOS note referred above explains instance sets in detail, along with a couple of examples.
If you now navigate to System Administrator responsibility, you will be able to access requests submitted by other users and inspect the logs and output of the concurrent programs.
The 11i profile option - Concurrent:Report Access Level - no longer applies in R12. This has been replaced by Role Based Access Control - RBAC in short.
If you are already familiar with RBAC and wish to setup advanced controls around which users can share outputs, then MOS Note ID 736547.1 is a good place to start.
However, if your requirement is simple - you have business users running concurrent programs, and as part of support team, you simply want to query the concurrent program they have run and view the log and view output - then follow the simple steps below.
The goal here is - from under the "System Administrator" responsibility, you should be able to view the log and output for concurrent programs submitted by ANY user. If you do not have this responsibility (i.e. if you are a business user), you will only be able to query programs that have been submitted by you.
Step 1: Through the Functional Administrator responsibility, using the "Grants" tab, search for Object: Concurrent Requests and click on Go
Step 2: You have a delivered grant called XDO Concurrent Request Security. Click on the Duplicate icon, which will readily create a duplicate of this grant.
Step 3: Next, start overwriting the fields to be meaningful:
Name: Concurrent Request Security - System Admin Views ALL Requests
Description: Concurrent Request Security - Allow System Administrator to View All Request Logs and Outputs
Effective From: 01-Jun-2000
Grantee Type: All Users
Operating Unit: Leave Blank
Responsibility: System Administrator. This means this "grant" is only applicable when you switch to the System Administrator responsibility. You can replace this with any other responsibility that you wish to see all logs and outputs from.
Object: Concurrent Requests
Step 4: Click the "Next" button
Object: Concurrent Requests
Data Context Type: All Rows. All Rows indicates access to ALL concurrent program logs and outputs. If you want access to be shared for only a limited set of concurrent programs, you can achieve this be selecting the Data Context Type as Instance Set. Definition of Instance Set is not part of scope of this blog. The MOS note referred above explains instance sets in detail, along with a couple of examples.
Step 5: Click the "Next" button, accept all defaults on this page
Set: Request Operations. This is a seeded permission set, which gives access to Submit Requests, as well as View Requests
If you now navigate to System Administrator responsibility, you will be able to access requests submitted by other users and inspect the logs and output of the concurrent programs.
