In SAP R/3 there are more than 50000 english transaction codes. Some of these transactions are very dangerous and user access to such transactions should be restricted. So what exactly are dangerous transactions in SAP R3. Dangerous T-Codes can corrupt or damage the SAP system. Such transactions also present a security risk and haev an adverse impact on the SAP system performance.
Usually, access to such dangerous SAP transactions should be restricted to the production system. Development and test systems do not pose that much of a risk. The production system is important because it contains live data and the entire company's operations are dependent on such data. Restricting access to dangerous SAP transactions can be done in two ways. The first way is to restrict the user through standard SAP security to such transactions. The second line fo control is to lock such transactions at the client level. Once locked such transactions cannot be accessed by any user. Critical transaction codes from each SAP module should be locked after thorough consultation with the functional process owners.
- Refer SM01 - Transaction Codes [Lock/ Unlock]
- How to Unlock the sm01
- What is the SAP Basis Certification and Course code?
- Transaction code for CRM documentation
- Transaction code MK01 not working
- Shipment With Transaction Code VT01N
- SAP_ALL Access and Locked Tcode SM01 from all Users
- Frequently used Transaction Codes in CRM
- User Lock Appears for Transaction Code CJ9BS
- Transaction code J_1IG_INV Error for STO