Skip to Content

Restricting tables available for selection for object type in MM46

Jan 20, 2017 at 01:34 PM


avatar image
Former Member

Transaction MM46 (Mass Maintenance: Articles (retail)) affords the opportunity to do mass changes across various objects. You can usually choose from multiple tables available for updates.

We would like to give access to the transaction but limit the objects and tables the user can update via roles.

I have searched quite extensively and inquired from some peers in the functional and authorisations areas and it does not seem possible to go to this level.

I would like to confirm there is absolutely no way to do this before I feedback to the requester. I would really appreciate any feedback or suggestions.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Colleen Hebbert
Jan 29, 2017 at 10:22 AM

if you have run a trace and cannot see an authorisations being checked at a granular enough level then I'd get your ABAP developer to see if there's any place for a customer enhancement spot to make it possible.

Depending on screen layout of this transaction, you might be able to look at creating a screen variant transaction and supressing fields you don't want user to have access to (I suspect unlikely)

10 |10000 characters needed characters left characters exceeded
Veselina Peykova
Jan 30, 2017 at 08:06 AM

Typically, mass change transactions, such as MM46, are not granted to business users.
In a productive environment usually such master data changes are handled with a support request - the business provides a template, this goes through an approval process and then the support team uploads the data (logging on with some firefighter ID - Big Brother is watching).
Honestly, I don't see the point in trying to restrict data uploads, done by the support consultants (who supposedly know how to use the transaction), when this has already been approved and that everything is being recorded.
You could probably have a look at variants for transaction MASS (MM46 is simply a variant of it) and create something similar, but to me this not the most optimal way to spend development/functional effort.

10 |10000 characters needed characters left characters exceeded