Ten ABAP Transaction You Will Probably Use Most

SE80 – Object Navigator
SE80 is the most important transaction for the ABAP programmer. It’s the entry point for the workbench. From SE80 you can for example create new packages, classes, programs, dictionary objects (database tables) etc.

SE11 – Dictionary
Using SE11, you can create and maintain database objects such as Database tables, data types, and lock objects.

SE30 – Performance
SE30 is used for testing performance. Want to compare two bits of code that do the same thing and see which one runs quicker? SE30 is the place to do it.

SECATT – Extended Computer Aided Test Tool
Extended Computer Aided Test Tool (or ECATT) is a built-in tool to test SAP system. By using eCATT you can:
• Test transactions, reports, and scenarios
• Call BAPIs and function modules
• Test remote systems
• Check authorizations (user profiles)
• Test updates (database, applications, GUI)
• Test the effect of changes to customizing settings
• Check system messages

SU01 – User Maintenance
This is the place to maintain user data such as personal data, roles, logon data (passwords) etc. It’s kind of like SAP’s Java WAS’s User Management Engine (UME).

SE81 –Application Hierarchy
SE80’s less famous sister, SE81 allows you to browse SAP applications. Clicking on a node (application) on SE81 opens that application in SE80.

SE91 –Message Classes
SE91 allows creating and maintaining message classes.


SM12 –Lock Entries
Using this transaction you can see which lock objects are used by which user for a table of your desired. See the postregarding lock entries for more information...

SM30 – Maintain Table Views
Using this transaction you can maintain table views, manually adding, editing and removing information from existing tables for which you created a table view.

For a more extended list of frequently used ABAP Transactions, visit the list of ABAP transaction codes, courtesy of SAPTechies.com