Header Ads Widget

Responsive Advertisement

Critical Tcodes which should not be given in SAP

These are some of the highly critical tcodes which should not be given to end users in SAP. Recommended that some of these tcodes must be locked in the system. To find how to lock a tcode in the system

TcodedescriptionRecommended Action
SE38 One can bring down the whole SAP system with this tcode..
Highly critical. One can debug in production if he has this tcode, which hits the performance severly
To be locked in Production
SA38Same functionality as SA38 except that one cannot debug or view source code of programs here, but can run virtually any report and hit the system performanceTo be restricted to privileged ID's or SUPER USERS
SE16 Not that critical but you credit card details can be viewed if the user has the tcode. DATA PRIVACY is at risk if this tcode is given to users. It can cause huge load on system if a user tries to view a table having large amount of data. One can even change table data using SE16To be restricted to few critical Users
SCC5Deletion of client. Really !!. Give this tcode to end user. You can close you shutter and sleep at home!!. no need to do any more business. This is to be restricted to only few or one or two persons in the project and it must be locked always.To be locked always

Post a Comment

0 Comments

SPAM/SAINT Support Package and Stack Upgrade in SAP