2007 Mar 12 5:46 PM
Hi,
Did any of you block the Query Builder Tool access to your end users?
In our Netweaver 2004s BI implementation, we have a special need to restric the access to Query Builder Tool. Mostly our users are using BEx Analyzer tool (Front end service pack- SP12). Any ideas in this regards would be highly appreciated? Of course I can restrict access on the back end that our end user is only able to read the Query. What I am looking what is, how to stop the user even from launching Query Builder tool?
Thanks
Jay Lakshmanan
Hi,
Did any of you block the Query Builder Tool access to your end users?
In our Netweaver 2004s BI implementation, we have a special need to restric the access to Query Builder Tool. Mostly our users are using BEx Analyzer tool (Front end service pack- SP12). Any ideas in this regards would be highly appreciated? Of course I can restrict access on the back end that our end user is only able to read the Query. What I am looking what is, how to stop the user even from launching Query Builder tool?
Thanks
Jay Lakshmanan
2007 Mar 13 6:37 AM
Hi Altera,
If the role doesnt give access to transaction RRMX and if none of the Reporting Auth Objects (S_RS_COMP, S_RS_COMP1, S_RS_FOLD) exists, than the user will not have access to Query Builder.
Hope it helps.
Please award points if it is useful.
Thanks & Regards,
Santosh
2007 Mar 13 11:52 PM
Santosh,
If I don't give access to RRMX, S_RS_COMP, SRS_COMP1, S_RS_FOLD can still the user be able to view the quriers? create query views? Workbooks?
Thanks
Jay
2007 Mar 14 6:07 AM
Hi Altera,
Nope, without those Objects and Transaction, user will not be able to access Bex tool.
Thanks & Regards,
santosh
| User | Count |
|---|---|
| 6 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |