Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 36 ยท SAP Architecture and Navigation

SAP Transaction Codes (T-Codes): Navigation Shortcuts and Common Examples

Learn what SAP transaction codes are, the command prefixes /n, /o, /nex and /i, naming patterns, essential codes for finance, purchasing and sales, and how to find any code.

A transaction code, or t-code, is a short name that starts a program or screen in SAP GUI. Instead of clicking through five menu levels, you type MM03 in the command field and press Enter to display a material. Experienced users know hundreds of them, and consultants use them daily. This lesson teaches how t-codes work, the prefixes that control sessions, the naming patterns that make codes guessable, and a starter set for the main modules.

Running a code

  1. Click the command field (top left) or press Ctrl+/ to put the cursor there.
  2. Type the code, for example ME23N.
  3. Press Enter.

If a screen is already open, SAP may ask you to finish it first. To jump from anywhere, use a prefix.

Command prefixes

You type Effect
/nMM03 Ends the current transaction without saving and starts MM03 in the same session
/oMM03 Opens MM03 in a new session (window)
/n Ends the current transaction and returns to the Easy Access menu
/o Opens the session overview (list of sessions to jump between or create)
/nex Ends all sessions and logs off immediately (unsaved data is lost)
/i Deletes the current session
/h Turns debugging on for the next step
/nend Ends the logon, with a confirmation prompt

Be careful with /n and /nex: unsaved entries are lost. Saving with Ctrl+S first is a habit worth building.

Naming patterns

Many t-codes follow patterns you can learn:

  • Two letters for the module, then a letter for the task and a number.
    • FB = finance posting, MM = material master, ME = purchasing, VA = sales, KS = cost center.
  • Final digits are often an action: 01 = create, 02 = change, 03 = display.
    • MM01 create material, MM02 change, MM03 display.
    • XK01 create vendor (old model), XK02 change, XK03 display.
    • VA01 create sales order, VA02 change, VA03 display.
  • Newer versions of a transaction add an N: ME21N is the "new" purchase order screen; MIGO is the goods movement transaction; FB50 is G/L account posting.

In S/4HANA many classic transactions are replaced by Fiori apps or by transactions that handle a whole object type. For example, vendors and customers are maintained in the Business Partner transaction BP instead of XK01 and XD01. Old codes may be hidden or return a message with the replacement.

Essential codes by area

General and navigation

Code Purpose
SU01 User maintenance (administrators)
SU3 Your own user settings
SE16 / SE16N Display table contents
SE11 ABAP Dictionary
SE38 ABAP editor for programs
SE80 Object navigator
SM37 Monitor background jobs
SM35 Batch input sessions
SPRO Customizing (IMG)
SM04 Users on the system

Finance

Code Purpose
FB50 Enter G/L account document
FB60 / FB70 Enter vendor / customer invoice
FS00 G/L account master data
FBL1N / FBL3N / FBL5N Line items: vendor / G/L / customer
F110 Automatic payment run
KS01 Create cost center

Purchasing and inventory

Code Purpose
ME51N Create purchase requisition
ME21N Create purchase order
MIGO Goods receipt and other goods movements
MIRO Enter vendor invoice (invoice verification)
MMBE Stock overview

Sales

Code Purpose
VA01 Create sales order
VL01N Create outbound delivery
VF01 Create billing document
XD03 / FD03 Display customer

You will meet each of these again in context; do not try to memorize the table now. Instead, learn the pattern and the lookup tools below.

Finding a code

  • Turn on technical names in the menu (see GUI and Fiori) so the tree shows codes.
  • System > Status shows the current program and screen, and the transaction code of the screen you are on.
  • Table TSTC lists all transaction codes, and TSTCT contains their texts. Display them with SE16 and filter by text, for example *Purchase*.
  • On the Easy Access screen, the search icon (Find) searches the menu tree.
  • In Fiori, the app finder shows the app and, in the app's About section, the technical name and the underlying details.
Python Stand-in: a t-code lookup

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Parsing a command

The command field accepts more than a code. The stand-in below mimics how the prefix decides the action.

Python Stand-in: command field parser

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Authorization: why a code may fail

You can only run a transaction if your user has the authorization object S_TCODE for that code (and often more objects checked inside). The message "You are not authorized to use transaction XYZ" means your role lacks it; ask the security team rather than looking for a workaround. Transaction SU53 shows the last failed authorization check, which you can send to the administrator.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the prefix /o do?

    /o opens a new session; /n replaces the current transaction without saving.
  2. 2. Which code displays a material master?

    Pattern: 01 create, 02 change, 03 display.
  3. 3. How can you find the code of the screen you are on?

    System > Status shows the current transaction, program and screen.
  4. 4. A message says you are not authorized for a transaction. What is the right step?

    Authorizations come from roles; SU53 shows the failed check to help the administrator.

Summary

  • A transaction code starts a program or screen from the command field.
  • /n replaces the current transaction (unsaved data is lost), /o opens a new session, /nex logs off.
  • Patterns help: modules prefix the code, 01/02/03 mean create/change/display.
  • TSTC/TSTCT, the Status dialog and the Easy Access search help you find codes.
  • Authorization (S_TCODE, roles) decides whether you may run a code.

Next: Master data and transaction data