Authorization field for SAP Standard Field

[former_member761621]

Hello All,

I having a query on Authorization field creation.

We are having a field name "Follow Up Material" or NFMAT in MM01/MM02/MM03 Transaction under MRP4 Tab.

I have checked if there is some authorization field created for this field in SU20. But there is nothing on the name NFMAT.

Is there any standard authorization field for the same.

If not,what needs to be done?

Can some one guide.

Jacob

[Former Member]

Hi Jacob, what is that you are trying to achieve here. Trying to restrict the access to that field ? If you spell out what your objective is, may be people here would be able to help you better.

[former_member761621]

Hello Zaheer,

Exactly.

Business wants to restrict the access to this particular field.

Jacob

[Former Member]

Hi Jacob,

You are right, there is no NFMAT field or follow up material. I would say check with business again for more clarity, what exactly is the field or find the authorization object involved to restrict.

Thanks,

Kavitha Rajan.

[former_member761621]

Hello Kavita,

Thanks for your response.

Business only give me the requirement for restricting the access for the this field. So reverting back to business on this doesn't make sense.

Being a security administrator I should be able to get back to them with a solution

Since the field is not available in authorization fields, I am not sure how we can acheive it!!

Jacob

[former_member761621]

This message was moderated.

[former_member230681]

Hi Jacob

You can try using transaction "OMT0" and uncheck the field "Follow up material".

can be beneficial for better understanding

Thanks

Anika

[former_member761621]

Hello Anika,

Thanks for your valuable input.

What I understood from tthat link and you communication is that it will be remove the field totally. Means, If I Uncheck, the field won't be visible afterwards. Am I right?

But, In my case, I want that field. But only some users should have the access to edit this field.

Cheers

Jacob

[former_member761621]

Hello All,

I guess I have the answer with me now.

I had to create a custom Field via SU20 with this data element and Attach this to a customer object in SU21. After that update in SU24 for future reference.

Do let me know if the same approach is right.

Cheers

Jacob

[Former Member]

This message was moderated.

[Former Member]

You will still need to add this check on a field in a custom object to the code though.

If you debug the navigation to the tab and where the field is coming from than you will see the checks and customizing and enhancement/BADI options -> that is also solution skill sets for a security consultant or have a developer you can work with.

Honestly, if your business has a requirement and you need a solution then parking it on SCN and waiting is not a good horse to bet on if you have not tried yourself to work out what your options are in the code.

A little example: users with access to MM03 should be able to display planning, others not. Users who only create material master should do so without knowing what the planning is, unless they have access to planning anyway?

Also: You should mention your release / SP level / whether it should excluded in MM* tcodes or dependent on other authorizations and therefore user specific system behaviour in the same transaction.

Cheers,

Julius

[former_member761621]

Hello Julius,

Thanks for your wonderful explanation.

I am not a developer, so I need to take the help of a Developer in this.

They have came up with the requirement for restricting in MM* T-codes alone.

Currently we are on Release 740/ 06.

Though the design goes to a developer, I am thinking on how they will be able to make this out, As already there may 1000's of User who might be using this field for Material Master Maintenance..

If we need to restrict the access, the logic would be to develop a new custom object and User who having access for this object will be only able to edit and rest will see this see this field as In-active/ Greyed out.

Since our client authorization concept is more into User Specific authorizations, there is a huge chance for multiple users to report this as an error once the code is released.

Do we have any other option other than this?? Is this the right approach?

The requirement is under discussion with different stakeholders. That is the reason, I just put this up here .

Regards,

Jacob

[Private_Member_25738]

Hi Jacob,

If you need restrict the transactions MM01, MM02 and MM03 by NFMAT value, I think that it is not an standard, you need do the following:

- Add the field NFMAT into SU20 to use it into a Z authorization object.

- Create a Z authorization object with this new field created (in my case ZNFMAT).

- Add an authority-check (checking your authorization object created) into the corresponding user-exist/enhancement, etc. into the programs relationed with MM01, MM02 and MM03

I think that it is the best way to check the field that you need into the required transactions.
I hope that it can to be help.
Best regards.