Full reference for SAP ABAP development transaction codes covering the ABAP Workbench, Data Dictionary, function modules, class builder, screen painter, debugging, and performance tools.
| T-Code | Transaction Name | Description & Usage Scenario | Type |
|---|---|---|---|
| SE80 | Object Navigator (ABAP Workbench) | Central development environment providing access to all repository objects: programs, classes, functions, tables, packages. Primary development workbench used by all ABAP developers. Provides organized access to all dev objects. | ★ Common |
| SE38 | ABAP Program Editor | Create, edit, activate, and test ABAP programs including reports, includes, and module pools. Most frequently used ABAP transaction. Used for all program development and debugging. | ★ Common |
| SE37 | Function Builder | Create, modify, test, and display ABAP function modules and function groups. Used to build reusable ABAP functions that can be called from any program or via RFC. | ★ Common |
| SE24 | Class Builder (ABAP OOP) | Create and maintain ABAP Objects classes, interfaces, and their methods, attributes, and events. Used for object-oriented ABAP development including BAdI implementations and service classes. | ★ Common |
| SE51 | Screen Painter (Dynpro) | Design and maintain screen layouts (dynpros) for SAP module pool programs. Used to build and maintain user interface screens for custom SAP transactions. | |
| SE41 | Menu Painter | Design and maintain menus, toolbars, function key assignments, and title bars for programs. Used in conjunction with SE51 to complete the GUI design for custom SAP applications. | |
| SE93 | Transaction Code Maintenance | Create and maintain transaction codes for SAP programs, function groups, or URLs. Used after creating a program to assign it a transaction code for user execution. | ⚙ Config |
| T-Code | Transaction Name | Description & Usage Scenario | Type |
|---|---|---|---|
| SE11 | ABAP Data Dictionary | Create and maintain database tables, views, data elements, domains, structures, type groups, and lock objects. Core development tool for all data modeling. Used daily by developers and Basis for schema management. | ★ Common |
| SE16 | Data Browser | Display the contents of any database table without writing ABAP code. Full selection and export capability. Most widely used data analysis tool. Used by all technical and functional consultants for data verification. | ★ Common |
| SE16N | General Table Display (Enhanced) | Enhanced version of SE16 with additional field selection, column layout, and download capabilities. Preferred over SE16 for its usability improvements and ability to display technical key information. | ★ Common |
| SM30 | Maintain Table Views | Maintain configuration table entries via generated view maintenance dialogs. Used to maintain customizing table data (e.g., country-specific settings, config tables). | ⚙ Config |
| SE17 | General Table Display (Simple) | Simple display of database table contents without selection options. Used for quick single-table content checks. Less powerful than SE16 but faster for simple lookups. | |
| SE14 | Database Utility (Table Activation) | Adjust database tables after dictionary changes: activate, convert, or create tables in the database. Used after changing table structures in SE11 to apply changes to the actual database schema. | ⚙ Config |
| T-Code | Transaction Name | Description & Usage Scenario | Type |
|---|---|---|---|
| SE30 | ABAP Runtime Analysis (Classic) | Classic version of the ABAP runtime analysis tool to measure program performance. Used by developers to profile program execution time and identify performance-critical code sections. | |
| SAT | ABAP Profiler (Modern) | Modern ABAP performance profiling tool replacing SE30 with enhanced visualization and drill-down. Used for comprehensive performance analysis of ABAP programs, includes call hierarchy and time breakdown. | |
| ST12 | ABAP Trace (Combined) | Combined tool for ABAP runtime analysis and SQL trace to identify all performance bottlenecks. Used when diagnosing programs with both ABAP and database performance issues simultaneously. | |
| ST05 | Performance Trace | Activate SQL trace, RFC trace, buffer trace, and HTTP trace to analyze system interactions. Used to capture and analyze database calls made by an ABAP program during a specific operation. | |
| SAAB | Breakpoints (System-Wide) | Maintain system-wide breakpoints for debugging in production or other restricted systems. Used by Basis when authorization prevents setting user-specific breakpoints in target systems. |
| T-Code | Transaction Name | Description & Usage Scenario | Type |
|---|---|---|---|
| SE09 | Transport Organizer (Workbench) | Create and manage workbench transport requests for ABAP development objects. Used by ABAP developers to collect changed objects and transport them to quality and production. | ★ Common |
| SE10 | Transport Organizer (All Types) | Manage all types of transport requests: workbench, customizing, transport of copies. Primary transport management transaction for both developers and consultants. | ★ Common |
| SE21 | Package Builder | Create and maintain development packages (formerly development classes) for object organization. Used to organize development objects into logical groups for transport and namespace management. |