Skip to Content
3
Dec 02, 2022 at 02:35 PM

Should Components or Namespaces be blocked in SE06 transaction for a DEV environment?

207 Views

Hi,

As you might know in S/4 HANA the SSCR license key to modify standard objects is no longer supported, therefore a user with full S_DEVELOP authorization can modify any standard object. In certain cases I've observed there is not even the warning message displayed "Make repairs in foreign namespaces only if they are urgent".

To my understanding the best approach to protect the system from standard modifications is to control the S_DEVELOP authorizations and only allow temporary access to SAP namespaces for notes implementation or extremely special cases, but I was also considering the usage of SE06.

In the DEV system the "Global Setting" is Modifiable and then almost all of the components and namespaces are also modifiable. Do you think this should be adjusted in a development system for a 2nd layer of protection? It can just make notes implementation difficult by having to assign a special role + enable modification in SE06 every time, so I'm not sure if it's really a good practice. I'm just looking for opinions.