MDR now includes options to control users making changes to the technical settings of MDR runs and being able to add authority checks, coded to your own requirements via exits.
The “Defaults for Technical Settings” screen through the /BTR/MDR transaction now offers two options for functionality restrictions, “Lock Technical Settings” and “Lock Expert Mode”. These work at a program level and once set they will apply for every user.
Lock Technical Settings
This options allows to lock all input fields for Technical Settings. This is useful if when a program can repeatedly run with the same default values and users should not change those values. When this option is set, the Expert Mode in the Run History will be locked as well.
This restriction applies at program level and not at user level. That is, once set the Technical Settings will be locked for all users. Restrictions at user level can be implemented with the MDR enhancement spots (see MDR Enhancement Spots document).
Lock Expert Mode
This option is similar to “Lock Technical Settings”. The only difference is that on the Technical settings screen only the input fields under “Distribution” are locked. This allows the user to change settings like label name while protecting the more critical job distribution section from potential misuse. This option applies at program level as well. Restrictions at user level can be implemented with see the MDR Developers Guide Authority Checks
MDR also provides enhancement spots to allow developers to apply customer specific authority checks. This can be used to restrict technical as well as administrative settings at user and at program level. To implement authorizations into MDR the following steps allow you to control which users can control the technical parts of MDR, either in the technical settings popup or the expert mode in the MDR Run History, using normal SAP authorization objects.
For more information refer to the section Authority Checks in the MDR Developers Guide.