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 a view which is based on a secured table

Go to solution
former_member270360
Participant

‎02-22-2010 7:06 PM

0 Kudos

Dears,

Could someone please guide on how to secure a view which is based on a secured table; for example view ENT7064 is based upon three tables : T503K, T503T and T503. The three tables are secured by authorization group 'PC'.

A user having authorization object : S_TABU_DIS with authorization field values : ACTVT = 03 and DICBERCLS = &NC&, is not able to browse any of the three tables through transaction SE11, but, he is able to browse the content of view ENT7064 through transaction SE11.

How could this be avoided ?

Thanks.

Reda

1 ACCEPTED SOLUTION

Go to solution
Former Member

‎02-22-2010 7:53 PM

0 Kudos

> A user having authorization object : S_TABU_DIS with authorization field values : ACTVT = 03 and DICBERCLS = &NC&, is not able to browse any of the three tables through transaction SE11, but, he is able to browse the content of view ENT7064 through transaction SE11.

A view without an authorization group does not make sense. That is the problem.

&NC& will give the users access to much more than the tables you have mentioned.

Unfortunately SAP defaulted the view to &NC& in earlier releases. If you apply support packs (which release are you on?) then there are many corrections and new SU24 data waiting for you as well.

Personally I simply delete everything which is empty in SU24 and then you will find the ones you use. Ideally report them to SAP as well. It is very tricky to retro-fit, but can be done...

Cheers,

Julius

1 REPLY 1

Go to solution
Former Member

‎02-22-2010 7:53 PM

0 Kudos

> A user having authorization object : S_TABU_DIS with authorization field values : ACTVT = 03 and DICBERCLS = &NC&, is not able to browse any of the three tables through transaction SE11, but, he is able to browse the content of view ENT7064 through transaction SE11.

A view without an authorization group does not make sense. That is the problem.

&NC& will give the users access to much more than the tables you have mentioned.

Unfortunately SAP defaulted the view to &NC& in earlier releases. If you apply support packs (which release are you on?) then there are many corrections and new SU24 data waiting for you as well.

Personally I simply delete everything which is empty in SU24 and then you will find the ones you use. Ideally report them to SAP as well. It is very tricky to retro-fit, but can be done...

Cheers,

Julius