on 09-11-2014 7:57 AM
Hello Experts,
I have created a dashboard using a Bex query which has a ready for input authorization variable.
I have used this variable as a query prompt selector in the dashboard.
When a user with restricted authorizations executes the dashboard, he gets the following error.
'Request processing failed. BW System returned state USER_NOT_AUTHORIZED. Message 'You do not have sufficient authorizations'.
However, when the same user executes the BEx query, he gets the correct data without any error message.
Can you please help?
Regards,
Suraj
I solved this issue by using two variables, one of authorization and one without.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
is the user passing same value to variable in both RSRT and Dasbhoard?
You can restrict the list of values by writing customer exit for i_step1, so that it wont bring any unauthorized selection values.
-Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check that input runs top of any hierarchy or specific info object (What is the info object name ?).
What is the connection you have used to take the BEx query to dashboard ?
Symptom
Environment
Reproducing the Issue
CauseThe Dashboard processing server doesn't has adequate memory allocated to process the LOV with big set of data.
Resolution
If you have used webi to bring the Bex query, check the below link.
Symptom
Environment
SAP BusinessObjects Business Intelligence platform 4.0
Reproducing the Issue
Workflow1 with SAP authentication:
Workflow2 with non SAP authentication:
Cause
This issue had been raised to dev under ID ADAPT01682867 however was rejected as By Design behavior:Here is the detailed explanation:First of all, if you execute in RSRT exact same query as in WebI then it will also fail;
There is a mechanism in BW to filter Hierarchy with user's authorizations, even if Authorization variable is not answered.
Implementation's role is to limit amount of Hierarchy nodes to work with and consequently accelerate Query execution.
It's important to note that if Hierarchy is not selected in Query, then this pre-filtering will not occur and so Authorization mechanism will fail...
Resolution
Workarounds:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suman,
The restriction is on company code. (0COMP_CODE). There are three company codes in the system 1000, 1001 and 1002. User is authorized to see only 1001.
The bex query variable uses authorizations as follows.
In the input variable screen, if user enters nothing, he sees only 1001 in the result.
If he enters 1000 or 1002 he gets an error message
If he enters 1001, he gets 1001 in the result.
Now I am using this variable as a prompt selector in my dashboards. Connectivity is using query browser directy to Bex. When the dashboard executes, I get the above mentioned error. If I then look at the possible values of comp_code from the dashboard, I see only 1001. If user selects 1001 from the prompt dropdown and executes, dashboard runs fine.
I feel on intial load, the prompt selector sends back * to BW and BW returns a not authorized error.
Regards,
Suraj
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.