Create custom MM01 to create only specefic material types.

[Former Member]

Hello all,

I need to create ZMM01 simmilar to mm01 but the only diffrence is that in case of zmm01 has access to create only few material typeas and not all as in the case of MM01

Kindly provide help in this issue.

Thanks

Arjun

[Former Member]

Hello all,

I need to create ZMM01 simmilar to mm01 but the only diffrence is that in case of zmm01 has access to create only few material typeas and not all as in the case of MM01

Kindly provide help in this issue.

Thanks

Arjun

[Former Member]

i think you can make an enhancement for the material type.

why do you have to create the other "zmm01"?

tks.

[Former Member]

Hi,

Thanks for the reply but we want some users to be able to create onle few material types wheras some users have access to create materials of any material type.

Thanks

Arjun

[Former Member]

Hello,

You can search the corresponding BADI. Enter se24, class cl_exithandler, breakpoint at the first call function and then enter MM01 and find the name of the BADI in the exit name. Then you can enter a method and write the code where you select which user will be allowed to pass to the next screen.

Efren

[Former Member]

Arjun,

I am not sure of any BADI presence for MM01, I remember of not finding any, long time back when I needed, but there are few user-exits available for sure which can help you put required validation. Use those exits for your need.

Block the material types there which you don't want to allow by MM01, for some users and corresponding material types, use authorisation/role concept to validate.

BR,

Diwakar

[Former Member]

Hello All,

Thanks for the suggestion of using exit/enhancement to put a check on user and authorize and it would work fine in this case but if we need to make custom MM02 where few user's can editonly specified fields of the material type and remaining fields are uneditable(grayed out) depending on material type. Please suggest how this could be done.

Thanks

Arjun

[Former Member]

Hi,

Kindly dont create a custom MM02/MM01 tcode, that could give problem in future/while up gradation.

I can remember that, there is tcode in MM where we can set fields attribute ( I am not sure, is it possible for user wise).

Pl. Check with MM functional guys.

Regards,

S.Senthilkumar

[deepak_dhamat]

Hi ,

I think you can make use of Validation using GGBO transaction .

Generally this is done by Functional person .

in that validation rule you can restrict user

regards

Deepak.

[Former Member]

Create transaction variants for the screens that need control limits in MM02. In your variants, make the fields that you don't want edited hidden or display only. Some people may not even need to see cost values, for example.

You can create these transaction/screen variants with transaction SHD0, by walking though the MM02 transaction end-to-end during transaction variant create step, saving all the screens, the going into the variants and screen-by-screen, set the display-only or hide checkboxes as needed. You can also control the drop down menus and gui functions/push buttons, etc., here.

Better yet, show your functional support person how to do this, and let them set up all the screen variants.

Create a variant transaction ZMM02 that always uses that MM02 transaction variant. Allow some users access to MM02, other to only ZMM02, via security.

Run the variant transaction and edit in SHD0 and adjust each screen's setting until you have what you want.

Please do NOT copy and whack and hack on MM programming. That's amateurish, IMHO. If you do, you can bet that SAP probably will not honor warranty (or give you free support to fix it) if/when your company discovers that the database is royally fouled up by custom programming! And, if you upgrade your system to a new release, you may find that your custom code no longer works (or fouls up the database), and you have to start all over again.

[Former Member]

Hi Dave,

Thanks for the reply but issue is that we have fields to be made uneditable dependent on the material type i.e. it is not same for all material types. Thus if create screen variants according to our requirement it would be same for all the material types.

Please suggest how this could be handled

Thanks

Arjun

[Former Member]

My employer doesn't use logistics modules, so I can't really check on this, but since you have this requirement, I think I would look for a BADI where I could control the screen-input value for each fieldname, based on some logic (material type) and the screen number. One could also check for implicit enhancement area in PBO modules, to see if you could do a loop at screen, check for specific fieldnames and set input = 0 there.