Posted on July 27th, 2008 by Sanjit Anand |
Print This Post
|
Email This Post
| Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today |
Oracle Applications does not allow users to view other's output. Internally Report Review Agent allows(RRA) only the user who submitting the report to view the report output. For those who are very new to Oracle can understood RRA as a default text viewer that Oracle Applications provides, which allows users to view report output and log files. Very often report Review Agent is also referred by the executable FNDFS.
That mean the output cann't be utlized by another user unless untill you have provided the profile option setup for another user.
Sometime business user wants to see other user report submitted by another?
Minimum you have do is you need to alter the value of seeded profile options "Concurrent:Report Access Level".
Business case
Within Oracle installation , lets say you have four different user profiles been maintained:
-
Super User : the one who has access to everything
-
Supervisor : the one who does not have access to all the functions but access to most of Function expect few setup.
-
User : the one who has access to limitted screens based on their responsibility
-
Inquiry :one who has access to limitted screens based on their responsibility.
But along with that, all the users belongs to any of the above category has access to all the Request details like Log, Output, Details screen and Parameters.
in 11i we are able to see all the Concurrent Job details if we are using single a responsibility. But with different responsibilities assigned accross users, only those users that belong to the same responibility can see the Concurrent Job details submitted by others.
that mean if a)UserA is superUser b) UserB is only User and if UserB has submitted a Job and UserA canot see the details of that job even if he is SuperUser as he belongs to a different responsibility.
Resolutions
Attach Profile options "Report Access Level" either at Responsibility leval or user level.
Concurrent: Report Access Level
This profile determines access privileges to report output files and log files generated by a concurrent program. The system profile option "Concurrent:Report Access Level" provides 2 options.
1.If you setting this profile option are set to "User" then you can:
View the completed report output for your requests online
View the diagnostic log file for those requests online
Reprint your completed reports, if the Concurrent:Save Output profile option is set to "Yes".
2.If you setting this profile option is set to "Responsibility", access to reports and diagnostic log files is based on the your current responsibility.
This profile option is visible and updatable at the site, responsibility, and user levels.
The internal name for this profile option is CONC_REPORT_ACCESS_LEVEL
R12 - Profile option "Concurrent:Report Access Level"
Within R12 environment,the profile option "Concurrent:Report Access Level" is inactivated.
It is replaced by a 'grants' function,that mean the RBAC (User Management) has to be implemented in R12 to replace this profile Options to enabled users to view out users log and output files in the Oracle Forms.
Suggested Reading
-
Note:555524.1 :How To Configure Access To Request Output Of Specific Responsibility
Related Posts
February 23rd, 2012 at 8:47 pm
4 steps to creating a new role to view all reports within a responsibility in R12
Step 1 – provision your user with the correct access (this only has to be done once per instance)
Login as sysadmin user
Navigate to user management responsibility ? users and query your regular user
Select “update user “
Assign Role – “Security Administrator” to your user. Save.
Assign Role – “User Management” to your user. Save.
Assign Role – “Functional Developer” to your user. Save.
Log-out as sysadmin,
Step 2 – specify function of the role (in this case ability to view all requests within a responsibility)
login as your user
Via “Functional Developer” responsibility
Search for object Concurrent Requests.
Click on Concurrent Requests.
Click on Object Instance Sets tab.
Click on Create Instance Set button.
Enter Name , Code and Description for new instance set.
– Enter the following for predicate:
&TABLE_ALIAS.request_id in (select cr.request_id from fnd_concurrent_requests cr where cr.responsibility_id = fnd_global.resp_id and cr.responsibility_application_id = fnd_global.resp_appl_id)
Save
Step 3 – Create new Role, create grant, and assign function created in Step 2
Go back to the “home” and goto “user management” responsibility ? goto Role and Role Inheritance tab
Create a Role and then create a Grant for the Role.
Enter Name and Description for the new Grant.
For the Data Security Object enter “Concurrent Requests”.
Click Next and provide the Data Content Type of “Instance Set”.
Click Next and for Instance Set choose instance set created above
The permission Set is “Request Operations”.
(Note: There are no parameters for the grant).
Set 4: assign role to user
Query the User Name you want to add the new role to.
Click on the Update icon.
Click Assign Roles button and find the new role created in Step 3.
Save and Apply to activate the new role.