Dashboards: Issue with BEx Authorization Variable

[Former Member]

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

[Former Member · Accepted solution]

I solved this issue by using two variables, one of authorization and one without.

Thank you.

[Former Member · Accepted solution]

Suraj,

Can you please explain in detail how you have used the variable without authorization. I have Org unit as my auth variable. Do i have to pass the value from the dashboard to the Org Unit variable without Auth?

Thanks

[cristian_nazar2 · Accepted solution]

Abhi, hi

do you fix this issue , i have the same problem.

regards.

Cristian

[Former Member · Accepted solution]

Cristian,

Yes, I have created a duplicate of the authorization variable and removed the input values and used the duplicate in my queries. Hope this helps

Thanks

Abhi

[sriramvijay_ravidoss]

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

[Former Member]

Hi Sriramvijay,

In the bex report, if user sends * he gets only the company code he is authorized to see, ie, 1001.

In dashboard, the prompt selector by default has no value selected, and it gives an authorization error on load.

Regrads.

Suraj

[former_member182541]

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 ?

1927274 - BI 4.0/4.1: The Query Prompt Selector can't initialize when view the dashboard from BI Lau...

Symptom

• The Query Prompt Selector was configured with the BW Variable which has a LOV with big set of data
• The Query Prompt Selector can't initialize when view the dashboard from BI Launch Pad or Dashboard Designer
• The following error message display from the dashboard after the Query Prompt Selector loading for sometime
  Error: "Request processing failed: Error Failure Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator. [RCIRAS0546]"
• The following error message also displayed from the Fiddler trace
  Error: "getLOV excepction (Error: N/A 99998)"

Environment

• SAP BusinessObjects Dashboard Designer 4.0
• SAP BusinessObjects Dashboard Designer 4.1

Reproducing the Issue

1. Create BW BEx Query with variable which has a LOV with big set of data.
2. Create the dashboard with direct access to BEx Query through BICS connection.
3. Configure the BW BEx Query to refresh at initial load.
4. Configure the Query Prompt Selector with the variable.
5. Preview the dashboard from designer or view it from the BI Launch Pad.
6. The Query Prompt Selector will load for sometime, but finally will return the following error message.
   Error: "Request processing failed: Error Failure Your request could not be completed because a failure occurred while the report was being processed. Please contact your sysem admnistrator. [RCIRAS0546]"

CauseThe Dashboard processing server doesn't has adequate memory allocated to process the LOV with big set of data.

Resolution

1. Login the CMC.
2. Switch to the Servers page.
3. Right click on the Dashboard Processing Server and click Properties.
4. Find the entry Java Child VM Arguments and change the Xmx parameter to a bigger value.
5. Restart the Dashboard Processing Server.
   
   Note: For this scenario, the target value for this parameter was defined depends on the physical memory of your server on which Dashboard Processing Sever is running as well as how big the LOV is,
   if you have adequate memory for your server then you can set this parameter to a relatively big value for test and change to a smaller one later to try to get the appropriate value for this parameter,
   however, the best practice is to prevent to use the variable with big LOV or control the size of LOV by restricting the data from BW side because loading a big LOV means longer processing time hence
   impact the overall performance of your dashboard.

If you have used webi to bring the Bex query, check the below link.

1812327 - Error:" BW System <system ID> returned state: USER_NOT_AUTHORIZED (WIS 00000)" is displaye...

Symptom

• Restricted user must provide an input value for BW optional variable
• Error:"BW System <system ID> returned state: USER_NOT_AUTHORIZED (WIS 00000)" is displayed if no value is provided

Environment

SAP BusinessObjects Business Intelligence platform 4.0

Reproducing the Issue

Workflow1 with SAP authentication:

1. Connect to Web Intelligence using SAP authentication with User1(restricted user)
2. Create a Web Intelligence report based on a bex query having an optional variable with analysis authorization
3. Run the query and don't provide any input value for the optional variable

Workflow2 with non SAP authentication:

1. Create a BICS connection on a bex query with analysis authorization using a non SAP_ALL authorization account
2. Create a webi report based on that connection with any user
3. Run the query and don't provide any input value for the optional variable

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:

• Include the Hierarchy which contains authorized nodes in the Webi query ResultObjects
• Provide a default value for the variable which is accessible by all the users
• Disable the optional variable in the query panel each time the user decides to not provide an input value

[Former Member]

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

[former_member182541]

So that is because user are not aware of it, pass 1001 by default and suppress the error message in the background and alert them with the text box "Result executes only with the company code 1001".

Instead of query prompt selector use combo box here.