SAPFree referencePDF, Excel, Word exportSAP ABAP

ABAP Developer Transaction Codes Reference

ABAP development is a lot of jumping between tools: dictionary, editor, class builder, dump analysis, job monitor, transport organizer. This reference lists the transaction codes developers use every day, grouped by area, so new team members and cross-trained consultants can find the right screen quickly.

Download:

T-code	Name	Area	What ABAP developers use it for
SE11	ABAP Dictionary	Development	Create and display tables, views, data elements, domains, structures
SE16	Data Browser	Data	Display table contents with selection conditions
SE16N	General Table Display	Data	Display table contents with a newer selection screen
SE37	Function Builder	Development	Create, test and display function modules
SE38	ABAP Editor	Development	Create, edit and execute reports and includes
SA38	ABAP Program Execution	Development	Run a program by name, also used in authorization checks
SE80	Object Navigator	Development	Browse packages, programs, classes and objects in one tree
SE24	Class Builder	Development	Create and display global classes and interfaces
SE18	BAdI Builder, definitions	Enhancement	Display classic BAdI definitions
SE19	BAdI Builder, implementations	Enhancement	Create and maintain classic BAdI implementations
SE51	Screen Painter	Development	Design dynpro screens and flow logic
SE41	Menu Painter	Development	Maintain GUI status and GUI title
SE91	Message Maintenance	Development	Create message classes and message texts
SE93	Transaction Maintenance	Development	Create custom transaction codes
SE84	Repository Information System	Search	Search for objects by name, package or type
SE14	Database Utility	Data	Activate and adjust database tables after dictionary changes
SE63	Translation	Development	Translate texts for multi-language systems
SM30	Table Maintenance	Data	Maintain customizing and custom table entries
SE09	Transport Organizer	Transport	Display and release your workbench and customizing requests
SE10	Transport Organizer (Extended)	Transport	Display requests of any user, create transports of copies
SE01	Transport Organizer (Extended view)	Transport	Manage and search transport requests and tasks
STMS	Transport Management System	Transport	Import queues, transport routes, import status
SCC4	Client Administration	Basis	Check client role and change protection settings
SE06	Set Up Transport Organizer	Basis	Check the system change option
ST22	ABAP Runtime Error (Dump) Analysis	Analysis	Read short dumps and see where the program stopped
SM21	System Log	Analysis	Review system messages and errors
SLG1	Application Log Analysis	Analysis	Read logs written with the application log API
SM37	Job Overview	Background	Monitor and analyse background jobs
SM36	Define Background Job	Background	Schedule background jobs and steps
SM50	Process Overview	Analysis	See running work processes on the application server
SM12	Lock Entries	Analysis	Display and delete enqueue locks
SM13	Update Requests	Analysis	Check failed or pending update tasks
SM59	RFC Destinations	Integration	Maintain and test RFC connections
ST05	Performance Trace	Performance	Trace SQL, enqueue, RFC and buffer calls
SAT	ABAP Trace	Performance	Runtime analysis of programs and calls
SCI	Code Inspector	Quality	Run static checks on custom objects
ATC	ABAP Test Cockpit	Quality	Run ATC check variants and review findings
SU53	Authorization Check Display	Security	See the last failed authorization check
SU21	Authorization Objects	Security	Display authorization objects and their fields
PFCG	Role Maintenance	Security	Maintain roles and authorization data
WE02	IDoc Display	Integration	Display IDocs and their status records
WE19	IDoc Test Tool	Integration	Create and process test IDocs
BD87	Status Monitor for ALE Messages	Integration	Select and reprocess IDocs by status
SEGW	SAP Gateway Service Builder	Integration	Build OData services in the classic gateway model
SICF	HTTP Service Hierarchy	Integration	Activate and maintain ICF services
AL11	SAP Directories	Basis	Browse files on the application server
ABAPDOCU	ABAP Documentation and Examples	Help	Read the ABAP keyword documentation and run examples

Availability depends on release and authorizations. Some transactions are replaced by Fiori apps or ADT (ABAP Development Tools in Eclipse) in S/4HANA, and ATC is usually reached through ADT or the ATC transaction on your release.

AI help for SAP dumps and logs

Optional: see how a private assistant could explain ABAP dumps and application logs using your own documentation.

Optional. The tool and every export work without this. No spam.

How to use the list

Search by code, by name or by a task word such as dump, trace, job or transport. The Area column groups codes into development, data, transport, analysis, performance, quality, security and integration. Enter a code in the command field with a leading /n to open it in the current session or /o to open it in a new one. Export the list to Excel or PDF to give a new developer a starter sheet for onboarding.

A typical developer day in transaction codes

You change a table in SE11, write or fix a report in SE38 or a class in SE24, and test it in SE37 or by running the program. When something breaks you read the dump in ST22 and the log in SLG1, and check the job in SM37. You trace slow SQL in ST05 or ABAP runtime in SAT, run SCI or ATC before release, then release the request in SE09 and watch the import in STMS. Knowing this chain is the core of working in an SAP landscape.

Build: SE11, SE38, SE24, SE37, SE80
Debug and analyse: ST22, SLG1, SM21, SM50
Performance: ST05, SAT
Release: SE09, SE10, STMS

Authorizations and system settings

Many of these codes need developer keys, a change-enabled client and a suitable system change option, and in production they should be locked down. If a transaction fails with an authorization error, SU53 shows the last failed check and the object and fields involved. Clients are set to allow or block changes in SCC4, and transport settings in SE06. Do not ask for broad debug-and-replace authorizations in production; use controlled firefighter access instead.

Fiori and ADT in S/4HANA

Modern SAP development increasingly happens in ABAP Development Tools in Eclipse rather than SE80, and many classic monitors have Fiori app equivalents. The transaction codes above still work in the SAP GUI on most systems and remain the common language between consultants. Learn both, and treat the code list as a map of capabilities rather than a promise that each screen exists unchanged in your release.

Frequently Asked Questions

What is the difference between SE38 and SA38?

SE38 is the ABAP Editor where you create, change and run programs. SA38 only executes a program by name and is usually the one given to end users. Authorization for running programs is controlled by object S_PROGRAM and related checks, so SA38 is safer to expose.

Which transaction shows why a program crashed?

ST22 shows ABAP runtime errors (short dumps) with the error type, the source line and the variable values at the time. Use the date, user and program filters to find your dump, and read the Active Calls section to see how the program reached the failing statement.

How do I find which transaction runs a given program?

Look the program name up in table TSTC in SE16N, or search in SE93 by program. For standard SAP, use SE84 or the Where-Used list of the program in SE38. Some transactions call function modules or classes, so a program name may not appear.

Do these codes work in S/4HANA?

Most of them do in the SAP GUI. SAP is steering development toward ABAP Development Tools in Eclipse and Fiori apps, and some classic tools are deprecated, so check your release. The codes remain a useful common vocabulary across ECC and S/4HANA projects.

If you spend hours reading dumps and logs, Netray can discuss a private AI assistant that explains ST22 and SLG1 output using your own system documentation, kept on your infrastructure.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools