Restricting in MM

Question: I have 3 objects that I would like to test for ME51N, being
K_ML_MTART to restrict field MTART - material type)
M_MATE_MAT and M_MATE_MAR to restrict materials and material type (Field Begru) per auth group MC.
What I have done was to make sure that the SU22 and SU24 looked the same and added the objects where necessary as CM.
I executed the transaction and ran a trace and the objects were not tested.
Advice I received:
The objects have to be added into the transaction's user exit to be checked.
or
To have the abappers update SU20 and SU21 with the objects.

PLEASE ADVISE WHICH IS THE BEST AND SIMPLEST WAY TO HAVE ANY OBJECTS CHECKED that the system is not currently checking.

Thanks
Confused but willing to try.....

Answer:
If the checks aren't switchable through config then it looks like using a user exit is the way to go for a proper solution (as long as you can drive the appropriate logic of course)

Answer:
You can't check an object that requires an authorization group unless you put authorization groups on the materials types, groups etc. If you do put authorization groups on them then the object will be checked.
_________________
bwSecurity

Answer:
bwSecurity-
The material type MC (SAP standard) has been put onto the material type, but the objects are still not checked.
I tried creating an auth group with table T134 for the specific groups that need to be restricted, but the system will not allow this as T134 'already exists' in auth group MC.
How do I get round this??
Thanks
Copyright ?2007 - 2008 www.jt77.com