# ABAP Developer Transaction Codes Reference

> Source: https://netray.co/tools/abap-developer-transaction-codes-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A searchable cheat sheet of development, debugging, transport and monitoring transaction codes used by ABAP developers.

## Category

sap

## Erp

SAP ABAP

## Audience

- ABAP developer
- SAP Basis administrator
- SAP technical consultant

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### T-code

**Key:** tcode

**Type:** text

#### Name

**Key:** name

**Type:** text

#### Area

**Key:** area

**Type:** text

#### What ABAP developers use it for

**Key:** use

**Type:** text

**Rows:**

#### ABAP Dictionary

**Tcode:** SE11

**Area:** Development

**Use:** Create and display tables, views, data elements, domains, structures

#### Data Browser

**Tcode:** SE16

**Area:** Data

**Use:** Display table contents with selection conditions

#### General Table Display

**Tcode:** SE16N

**Area:** Data

**Use:** Display table contents with a newer selection screen

#### Function Builder

**Tcode:** SE37

**Area:** Development

**Use:** Create, test and display function modules

#### ABAP Editor

**Tcode:** SE38

**Area:** Development

**Use:** Create, edit and execute reports and includes

#### ABAP Program Execution

**Tcode:** SA38

**Area:** Development

**Use:** Run a program by name, also used in authorization checks

#### Object Navigator

**Tcode:** SE80

**Area:** Development

**Use:** Browse packages, programs, classes and objects in one tree

#### Class Builder

**Tcode:** SE24

**Area:** Development

**Use:** Create and display global classes and interfaces

#### BAdI Builder, definitions

**Tcode:** SE18

**Area:** Enhancement

**Use:** Display classic BAdI definitions

#### BAdI Builder, implementations

**Tcode:** SE19

**Area:** Enhancement

**Use:** Create and maintain classic BAdI implementations

#### Screen Painter

**Tcode:** SE51

**Area:** Development

**Use:** Design dynpro screens and flow logic

#### Menu Painter

**Tcode:** SE41

**Area:** Development

**Use:** Maintain GUI status and GUI title

#### Message Maintenance

**Tcode:** SE91

**Area:** Development

**Use:** Create message classes and message texts

#### Transaction Maintenance

**Tcode:** SE93

**Area:** Development

**Use:** Create custom transaction codes

#### Repository Information System

**Tcode:** SE84

**Area:** Search

**Use:** Search for objects by name, package or type

#### Database Utility

**Tcode:** SE14

**Area:** Data

**Use:** Activate and adjust database tables after dictionary changes

#### Translation

**Tcode:** SE63

**Area:** Development

**Use:** Translate texts for multi-language systems

#### Table Maintenance

**Tcode:** SM30

**Area:** Data

**Use:** Maintain customizing and custom table entries

#### Transport Organizer

**Tcode:** SE09

**Area:** Transport

**Use:** Display and release your workbench and customizing requests

#### Transport Organizer (Extended)

**Tcode:** SE10

**Area:** Transport

**Use:** Display requests of any user, create transports of copies

#### Transport Organizer (Extended view)

**Tcode:** SE01

**Area:** Transport

**Use:** Manage and search transport requests and tasks

#### Transport Management System

**Tcode:** STMS

**Area:** Transport

**Use:** Import queues, transport routes, import status

#### Client Administration

**Tcode:** SCC4

**Area:** Basis

**Use:** Check client role and change protection settings

#### Set Up Transport Organizer

**Tcode:** SE06

**Area:** Basis

**Use:** Check the system change option

#### ABAP Runtime Error (Dump) Analysis

**Tcode:** ST22

**Area:** Analysis

**Use:** Read short dumps and see where the program stopped

#### System Log

**Tcode:** SM21

**Area:** Analysis

**Use:** Review system messages and errors

#### Application Log Analysis

**Tcode:** SLG1

**Area:** Analysis

**Use:** Read logs written with the application log API

#### Job Overview

**Tcode:** SM37

**Area:** Background

**Use:** Monitor and analyse background jobs

#### Define Background Job

**Tcode:** SM36

**Area:** Background

**Use:** Schedule background jobs and steps

#### Process Overview

**Tcode:** SM50

**Area:** Analysis

**Use:** See running work processes on the application server

#### Lock Entries

**Tcode:** SM12

**Area:** Analysis

**Use:** Display and delete enqueue locks

#### Update Requests

**Tcode:** SM13

**Area:** Analysis

**Use:** Check failed or pending update tasks

#### RFC Destinations

**Tcode:** SM59

**Area:** Integration

**Use:** Maintain and test RFC connections

#### Performance Trace

**Tcode:** ST05

**Area:** Performance

**Use:** Trace SQL, enqueue, RFC and buffer calls

#### ABAP Trace

**Tcode:** SAT

**Area:** Performance

**Use:** Runtime analysis of programs and calls

#### Code Inspector

**Tcode:** SCI

**Area:** Quality

**Use:** Run static checks on custom objects

#### ABAP Test Cockpit

**Tcode:** ATC

**Area:** Quality

**Use:** Run ATC check variants and review findings

#### Authorization Check Display

**Tcode:** SU53

**Area:** Security

**Use:** See the last failed authorization check

#### Authorization Objects

**Tcode:** SU21

**Area:** Security

**Use:** Display authorization objects and their fields

#### Role Maintenance

**Tcode:** PFCG

**Area:** Security

**Use:** Maintain roles and authorization data

#### IDoc Display

**Tcode:** WE02

**Area:** Integration

**Use:** Display IDocs and their status records

#### IDoc Test Tool

**Tcode:** WE19

**Area:** Integration

**Use:** Create and process test IDocs

#### Status Monitor for ALE Messages

**Tcode:** BD87

**Area:** Integration

**Use:** Select and reprocess IDocs by status

#### SAP Gateway Service Builder

**Tcode:** SEGW

**Area:** Integration

**Use:** Build OData services in the classic gateway model

#### HTTP Service Hierarchy

**Tcode:** SICF

**Area:** Integration

**Use:** Activate and maintain ICF services

#### SAP Directories

**Tcode:** AL11

**Area:** Basis

**Use:** Browse files on the application server

#### ABAP Documentation and Examples

**Tcode:** ABAPDOCU

**Area:** Help

**Use:** Read the ABAP keyword documentation and run examples

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the list

**Body:** 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

**Body:** 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.

**Bullets:**

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

#### Authorizations and system settings

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is the difference between SE38 and SA38?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

abap t codes list, sap development transaction codes, se38 se80 se11 se37, st22 dump analysis, sm37 job overview, sap abap cheat sheet, sap basis transaction codes, slg1 application log

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
