Skip to Content
avatar image
Former Member

Ability to hide characteristic from user in Query Definition

Hello All,

Is there a way (table entry, enhancement, mod, or other) to make a characteristic within a cube not be available for selection within the BEx query designer. Although relevant for the cube we do not want it available to the users for reporting.

I have looked at several tables and the field RSIOBJ-PROTECFL looked promising.

Thank you for your attention to this.



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jul 30, 2004 at 12:10 PM

    I am not able to find RSIOBJ table /structure/view in Data Dictionary.. which version of BW are you working on..

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 30, 2004 at 01:49 PM

    Hello David,

    the authorizations for query design do not support checks on characteristics or key figures of the InfoProvider.

    I would say it's not a good design if you need those type of restrictions. It basically means that those users could work only on an aggregate. Therefore, I suggest to build an InfoCube that contains just the aggregated data (i.e. excluding the characteristics that should not be available to the users) and fill it via data mart from the original InfoCube.



    SAP NetWeaver RIG, US BI

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hey Dave,

      I agree with Marc 100%. However I also have an alternate solution. See if it would suit you better.

      So you already have a cube in place. And one CHAR in this cube should not be seen by certain users. What you can do is make a multiprovider using this cube(so the multiprovider contains only 1 cube) and in the multiprovider do not put that CHAR or DIMENSION. so now you have 2 cubes essentially one with your CHAR and the multiprovider without your CHAR. So for ppl who are not authorized to view the CHAR, tell your security guy to grant them authorization on the multiprovider only and not the original cube and all others will have auth for cube.

      See in this case, you dont have to do a data mart and there is no load or any other hassle like update rules. Its an easy workaround.

      Let me know what you think.