Query - Authorization Check for Material Details

[Former Member]

Hi Experts,

I've got a requirement where I've to put authorization check in a number of transactions (standard as well as custom) which lead to material display some way or the other for specifc matarils (checking the authorization field). Few are for reports (may be interactive) as well. The need is to stop unauthorized people from getting access to the specifc material details such as dimensions (quantity,length, width, etc.).

The first option would be to stop the user from viewing the material itself and showing some appropriate error message.

The second option would be to make the above said details invisible in the screen for the specific matarials.

The Authorization object is M_MATE_MAT.

The Authorization field is BEGRU.

The range of tcodes start from ME21, ME22, ME23, ME23N ...to MM01, MM02 etc. and a number of custom tcodes.

What is the best way to achieve this? I guess I'd need to look for exits. Please suggest

Thanks & Regards

Pritam

[Former Member]

Hi Experts,

I've got a requirement where I've to put authorization check in a number of transactions (standard as well as custom) which lead to material display some way or the other for specifc matarils (checking the authorization field). Few are for reports (may be interactive) as well. The need is to stop unauthorized people from getting access to the specifc material details such as dimensions (quantity,length, width, etc.).

The first option would be to stop the user from viewing the material itself and showing some appropriate error message.

The second option would be to make the above said details invisible in the screen for the specific matarials.

The Authorization object is M_MATE_MAT.

The Authorization field is BEGRU.

The range of tcodes start from ME21, ME22, ME23, ME23N ...to MM01, MM02 etc. and a number of custom tcodes.

What is the best way to achieve this? I guess I'd need to look for exits. Please suggest

Thanks & Regards

Pritam

[former_member191735]

> I've got a requirement where I've to put authorization check in a number of transactions (standard as well as custom) which lead to material display some way or the other for specifc matarils (checking the authorization field). Few are for reports (may be interactive) as well. The need is to stop unauthorized people from getting access to the specifc material details such as dimensions (quantity,length, width, etc.).

>

> The first option would be to stop the user from viewing the material itself and showing some appropriate error message.

>

You can do this with authorization at transaction level.

> The second option would be to make the above said details invisible in the screen for the specific matarials.

>

Invisible on the screen, you might need to consider the material screens user exit. I am not sure how your material master configured

> The Authorization object is M_MATE_MAT.

> The Authorization field is BEGRU.

>

> The range of tcodes start from ME21, ME22, ME23, ME23N ...to MM01, MM02 etc. and a number of custom tcodes.

>

> What is the best way to achieve this? I guess I'd need to look for exits. Please suggest

All in all, you need user exits to have field level authorization and maintain authorizations at transaction level for the one you dont want to show anyone or to few

[Former Member]

Hello,

For each transaction you need to check how it can be enhanced (with a user exit, BADI, switch framework, ...).

Then you have to see if you can use the enhancement to control your process flow (block certain fields or screens, ...).

When this is possible you can build in your supplementary authorisation check.

Also check on this forum how you can find back enhancements in standard SAP transactions, there exist a lot of threads about this subject.

Success.

Wim

[Former Member]

first decide on a concept. what materials go to which group? then mass-maintain the material masters (MM17 or LSMW) and fill in the group. adjust your roles accordingly: check in tx. SUIM where the object M_MATE_MAT is used and adapt the roles.

actually, you would not need exits/enhancements for MM0* transactions. but things do not look so well when it comes to other transactions, because:

- if the view of the material master is called from another transaction (via GoTo or Environment-Menu) and this call is a BAPI -> it might not make that authority check.

- several transactions will display data of the material master without so much as asking for a BAPI/transaction/authority. e. g. ME*N (PO's etc.). some data -like the measurement data, weights etc- will be put into the PO, regardless whether the user has authority to view them in the material master.

i have no idea how you would manage to take your concept over all the system and it's interfaces. i do not think this is possible. sorry.

[Former Member]

Hi Mylène,

I'm thinking in the same line and given the input to business. I'm yet to get a feedback from the business. This is actually a defence requirment and I'm not sure how they are going to address this.

Anyways thanks to all of you. I'm keeping this thread open. I'll put some specific information once I've the concrete details.

Regards,

Pritam

[Former Member]

This requirement has now changed and they want add the Authorization value to each individual material and verify the same while any user tries to access the material. It has chaned the scenario and a report would do the trick. So I'm closing this thread and and have awarded points for your helpful answers.

Thanks,

Pritam