6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 11: Security AdministrationSecurity LayersTo Unlock a Client (Modifiable):6. Under Changes and transports forclient-dependent objects, selectAutomatic recording of changes.7. Under Client-independent objectchanges, choose and select Changesto Repository and client-ind.Customizing allowed.8. Under Protection: Client copier andcomparison tool, choose and selectProtection level 0: No restriction.9. Choose Save.6978“Dangerous transactions” could: Damage or corrupt the system Present a security risk Adversely impact performanceIf users accidentally access these transactions, they could corrupt or destroy the R/3 System. In a production system:Access to dangerous transactions is more critical in the production system than thedevelopment or test systems. This criticality is because of live data and the company’soperational dependency on the R/3 System. In a developmental system:Certain transactions should be locked in the production system, but not in thedevelopment, test, or training systems. Standard security normally prevents access tothese transactions, but some administrators, programmers, consultants, and functionalkey users could access them depending on which system they are. In these cases, thetransaction lock provides a second line of defense.System Administration Made Easy11–17