Emergency Changes in the Productive System 

Generally, users should not have programming, debugging with replace, or transport authorizations in your productive system. As previously mentioned, changes should occur in a single system, namely the development system. The table below shows those authorizations that apply to development and transport which you should not give to users in your productive system.

Authorizations for Development and Transport

Authorization Object	Purpose	Comment
S_DEVELOP	Authorizations for the ABAP Workbench (programming and debugging transactions – SExx)	With activity 02 (change) for development object types PROG and DEBUG, or activity 16 (execute) for all object types.
S_TRANSPRT	Authorizations for the Change and Transport Organizer
S_LOG_COM	Authorization to execute logical operating system commands

For more information, see SAP Notes 13202 and 65968.

If you do have to make emergency changes in the productive system, define a procedure to make the changes where you have supervised control over what happens. Give a single user temporary authorizations for transaction SE38 and make sure that someone approves these changes. Once the user has made the changes, remove the authorization!