Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Securing BW Tables (PSA, DSO, CUBE..) with authorization groups, has anyone

Former Member

‎01-20-2010 4:57 PM

0 Kudos

We want to keep SE16, but limit access to tables with sensitive data. Please share your experience. Thanks Mike.

2 REPLIES 2

Former Member

‎01-20-2010 6:18 PM

0 Kudos

PSA contain the data in plain text so that it can be read with SE16. and can be maintain in S_TABU_DIS This is not possible with data from the InfoCube because it is in INTEGER format.DSO consists of a single flat table & active data table (the data that can be used for reporting .

Former Member
In response to Former Member

‎01-20-2010 6:48 PM

0 Kudos

You can however re-use the analysis authorizations in the new concept and give access to RSA1.

SE16 (as generally with the ability to start arbitrary reports) is a development tool, and BW is not an exception in this regard if it has sensitive data in it. This is particularly true if the majority of the tables are not classified, and in some cases regularly deleted and re-created. SE54 will not help you much there to my knowledge.

A previous discussion on this (I am only aware of one too date) covered several aspects of what should be considered. Take a close look at the post by Peter John in ...

Cheers,

Julius