Error when data autorizations interfere with standard filters.

Question

Hi,
We have set up data authorizations in SAP B/W where people can either see all countries or one country on the characteristic [WAWL_CTRY].
we used to have a standard filter to only allow a selection of [WAWL_CTRY] in the report.
the report runs fine for the users that see all countries but fails when the user is limited to one country with the error below.
A database error occured. The database error text is: The MDX query SELECT  { [Measures].[D83PM0JYG6KACR6GZ1S9ICV3M] }  ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( EXCEPT(  { [WACCTGLOB].[LEVEL01].MEMBERS } , {  { [WACCTGLOB].[60116WTO], [WACCTGLOB].[60195WTO] }  } ),  { [WACCOUNT__WIRISACCT           CEH-IRIS].[R61000C                         0HIER_NODE] }  ),  { [WCURTYPE].[20] }  ),  { [WVERSION].[1] }  ),  { [WAWL_CTRY].[UP], [WAWL_CTRY].[SI], [WAWL_CTRY].[GE], [WAWL_CTRY].[FR], [WAWL_CTRY].[BE] }  ),  { [WVTYPE].[060] }  ), EXCEPT(  { [WPROF_CTR__WFUNCTION].[LEVEL01].MEMBERS } , {  { [WPROF_CTR__WFUNCTION].[#] }  } ) ),  { [0FISCYEAR].[W12010] }  ),  { [0FISCPER3].[001], [0FISCPER3].[002], [0FISCPER3].[003], [0FISCPER3].[004], [0FISCPER3].[005], [0FISCPER3].[006], [0FISCPER3].[007], [0FISCPER3].[008], [0FISCPER3].[009], [0FISCPER3].[010], [0FISCPER3].[000] }  ) DIMENSION PROPERTIES MEMBER_UNIQUE_NAME, MEMBER_CAPTION, [WACCOUNT__WIRISACCT           CEH-IRIS].[2WACCOUNT__WIRISACCT], [WAWL_CTRY].[2WAWL_CTRY], [WPROF_CTR__WFUNCTION].[2WPROF_CTR__WFUNCTION], [WPROF_CTR__WFUNCTION].[5WPROF_CTR__WFUNCTION], [WVTYPE].[2WVTYPE] ON ROWS FROM [G_PCA_M1/CFR_PCA_ALL]  failed to execute with the error Value UP for characteristic WAWL_CTRY unknown. (WIS 10901)
we are currently using the KEY to access the values.
Do you know how we can suppress the error for the country users?
greetings,
Gaetan Maerten

Answer 1

Hi Ingo,
It seems SAP B/W has a very sensitive disposition towards what is in the masterdata and what is not. Or even what is available to the users by means of security. To the contrary to a RDBMS pointing to an ITEM in the cube seems almost like pointing to a physical entity and not data.
I created a filter on Items that are not filtered by the security and thus available to access in the query. thus all the values are available in the list of value / Masterdata.
Thanks for your answer.
Gaetan