Unknown error when executing MDX when refreshing Crystal Report with BEx

Question

Hello Experts,
I have created a Crystal Report (Crystal 2008 SP1) with BEx Query (7.10) and have been able to refresh successfully when the SAP_ALL authorization is included in my user role. I don't want my end users to have SAP_ALL so I created a role and assigned the authorizations recommended in the SAP Integration Kit for BusinessObjects 3.1 Install Guide.
When I run the report as one of the users assigned to my new role I get the following error in the trace file.
ERROR: .\crdb_bwmdx_execution.cpp [200]: l_bapiGetStreamInfo failed with return code RFC_RC = 0 Exception:  BAPI Error: BAPI Error #:0
Unknown error when executing MDX
2188     6556     Caught DbError #1 with Message 'BAPI Error #:0
Unknown error when executing MDX'
2188     6556     Caught DbError #1 with Message 'BAPI Error #:0
Unknown error when executing MDX'
2188     6556     Caught DbError #1 with Message 'BAPI Error #:0
Unknown error when executing MDX'
I tried all the Fix Packs (ie 1.1., 1.2 and 1.3) for XI 3.1 Integration Kit to try resolving the error but it didn't work.
The same query works fine in BEx Web when running as one of the users in the new role I created for Crystal Report users.
Are there any other Authorizations that I need to include in the role?
Cheers.
Paul.

Answer 1

We have been able to identify what causes the MDX driver to error and I will explain what we are trying to implement with the hierarchies.
Firstly, we are creating reports of the HR cube Mutliprovider using the SAP MDX Driver which works well when there are no authorization analysis set on the cube. But with the authorization analysis set for on 0ORGUNIT for BEx Explorer Crystal returns the MDX error.
Each of the Business Unit managers are assigned to an Organization Unit that will be used to restrict the employees that will be reported. To restrict the Managers to only see their Org Unit we have set the 0ORGUNIT object to use authorization ananlysis and a custom authorization variable to return only data for the Org Unit they belong too.
In Crystal this works well when a manager has an Org Unit that is a head department of other Org Units. This scenario will give Crystal the NodeID and Parent NodeID to create the hierarchies in the report. But when a manager does not have any other Org Units beneath there own department then Crystal doesn't have a Parent NodeID to create the Hierarchies with the NodeID. In the RFC trace I can see an error when Crystal is trying to get the Parent NodeID but the user is not authorized to that Org Unit then it throws the error.
We have got a temporary workaround which is to create the managers a dummy Org Unit below their own department. The workaround will do for now but shouldn't the MDX driver be able to recognise that it has returned the last level in the Org Unit Hierarchy and not return an error?
The customer is looking for a product fix as they believe this should be handled by the driver. Is this a bug or a limitation of the product?
Paul.