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
Showing results for 
Search instead for 
Did you mean: 

URGENT: Supress Views in MM01/02/03

Former Member
0 Kudos
112

Hi,

We currently have a request to implement a restriction to the MM01/02/03 transactions in terms of view accessability. This means that depending on a new authorization object we have to make certain views invisible or at least inaccessible.

(The following is a short description of the request, so please refer to the bottom section for the problem itself.)



The reason for this is, that our customer has several plants whose workers should have restricted access to material views. This means they should have access to all plants' views except for some specific views like the costing views which they should only be granted access if they are authorized.

To make it a bit clearer, a short example.

A worker is assigned plant 1000, the material has views for plants 1000, 2000, 3000. The worker now is allowed to access the plant view, storage view etc. for all 3 plants. However, he should only be able to access the costing view for plant 1000 but not 2000 and 3000.

From what I know about authorization in the MMxx transactions we only can grant or deny access to all views for a specific plant or for all views of a specific type (i.e. either all or none of the views for 2000 and 3000 or costing views in general (for all plants)).

That's why we need a new authority object.

The problem:

We wanted to check the above described authority object in the MMxx transactions and based on the result grant or deny access to specific views. We tried to do this by setting or deleting function codes that drive view display.

The problem now is that according to our developer, the standard SAP authority objects override our custom object, so that if the user is allowed to see all views of a type and all views for a given plant, he will be granted access to all those views. To achieve our goal we'd have had to change the standard authority checks in all depending programs which would be infeasible.

Yet, there might (and I'm sure there must) be a way to tell the standard programs not to display a certain view in a feasible manner. I could imagine that there either is a list of function codes that we can alter based on our custom authority check or change something else that influences view display.

So does anybody of you know how to accomplish this or at least where to look further? Any help will be deeply appreciated.

Thank you very much in advance.

Thomas Göttlich

3 REPLIES 3

Former Member
0 Kudos
74

Anyone?

0 Kudos
74

I think you can try SPRO -> Material Master -> configuring material masetr -> maintain user settings. Here, you can select which views you want.

I've not used it but it seems this hsould work.

0 Kudos
74

Thank you for your answer.

Unfortunately this isn't a solution to the problem since as far as I know you the user settings only allow you to preselect screens. Other functionality like changing the screen sequences / screens that a user may see are not sufficient either.

The problem is that a user potentially may have access to ALL the screens. In fact the authority check has to work on a combination of plant/screen, so a specific screen may be accessible for plant A but not for plant B, depending on the user. And from what I know you can't do those restrictions in customizing.