Make customer master fields uneditable

[former_member645378]

Hi Team,

The business has the requirement to make most of the fields of the customer master in Display mode for certain set of Users. These fields should be editable when logged in with the firefighter account for emergency maintenance purpose.

There is a list of 346 standard sap fields which is to be made un-editable for the transactions XD02, FD02, VD02 and XD99. The fields are to be made un-editable only if the account group is not RB01, RB02 (So for total 174 account group it should be uneditable) . ABAP team suggestion is to try and do it through some configuration as otherwise it will be very complex.

I cannot make a direct change in the account groups as it will be a global change and then firefighter ID will also be restricted.

Transaction variant creation would be a very cumbersome process.

Please suggest the best approach to achieve this.

Regards,

Aditya

[former_member645378]

The customer master will be created through a 3rd party tool in SAP, the list of field which are to be made un-editable will be passed through the interface in SAP so the business do not want these to be manually edited by the users directly in SAP.

Not giving the option to any user is not an option.

[VeselinaPeykova]

Even if the master data is created via a 3rd party tool, there is no need to provide access for XD02 to business users- in most companies the end users place a request to correct the master data via a ticketing system, this goes via approval process and the activity is performed by support consultants if there is no dedicated MD team. Business users get display-only authorizations in most cases for customer/material master data for plenty of reasons. Edit authorizations are granted to very few people, who understand what, when and why to modify. Such approach worked quite well in all companies, where I have been, I still don't understand why this cannot be an option for your client.

Another option, which I have seen, was some form of self-service portal, with a web-based application, where users submit the request for MD corrections (they get the possibility to change only a few fields, depending on the account group and other factors), this triggers a workflow and after review/approval the data is actually updated in the back-end. Designing screens/fields in a web application, based on specific criteria is probably easier, compared to what your client is asking.

[VeselinaPeykova]

Business users should not have XD99, MASS etc. authorizations.
To be more precise, only a few people (usually a part of a dedicated Master Data team), might need change authorizations for customer master data.
In a past project, we had a special case, where part of the customer data had to be adjusted by the logistics team and placing master data change requests was not a good option. We got a custom transaction for the logistics department, which allowed the maintenance of a subset of all available fields (most of the ones, which they needed were from an addon, and in 2-3 screens).

Instead of ending up with even more complex requirement for XD02, VD02, FD02 (there will be new fields and account groups added to the mix... you will see), why don't you discuss with your colleagues that master data change transactions should not be granted to just anyone in a production system. Consultants work with Firefighter, where the activities are recorded, so no issues in this case.