SAP TCodes hub

Rather than drilling menus, experienced users jump straight to a function by code, VA01 to create a sales order, ME21N for a purchase order, FB50 to post a G/L document. Learning the codes for your area is one of the biggest productivity gains in SAP, and TCode lookups are among the most-searched SAP topics.

• Prefixes hint at area: V* sales, ME* purchasing, F*/FB* finance, MM* materials, SE* development, SM*/SU* admin.
• Variants: many come in create/change/display sets (e.g. MM01/MM02/MM03).
• Command-field prefixes: /n new, /o new session.

A short list beats a long one, because the codes you use daily become muscle memory and the rest are looked up. These are the ones practitioners actually reach for.

Sales. VA01, VA02 and VA03 create, change and display a sales order. VL01N creates the delivery, VF01 the billing document.

Purchasing. ME51N for a requisition, ME21N, ME22N and ME23N for the purchase order, MIGO for the goods receipt, MIRO for the invoice.

Materials. MM01, MM02 and MM03 for the material master, MMBE for the stock overview.

Finance. FB50 posts a G/L document, FB60 a vendor invoice, FB70 a customer invoice, F110 runs the payment program, FB03 displays any document.

Development. SE11 for the data dictionary, SE38 for programs, SE80 for the object navigator, SE37 for function modules, SE93 for transaction codes themselves.

Administration. SU01 for users, PFCG for roles, SM37 for background jobs, SM21 for the system log, ST22 for short dumps, SM59 for RFC destinations, SM12 for locks.

Roughly thirty codes cover most of what most people do. Learn the ten for your own area first and the rest arrive on their own.

Each TCode page gives purpose, key fields, tips and common errors, exactly what practitioners search for. Learn the handful for your role first, then expand. Tables TSTC/TSTCT list all codes and their texts.

Two command field prefixes are worth committing to memory because they save a great deal of navigation. Typing /n before a code leaves the current transaction and starts the new one; typing /o before it opens the new one in a second session, leaving the first where it is. Working with two sessions open, one for the document and one for the configuration behind it, is how experienced people work and it is invisible to anybody who has not been shown it.

Three ways, in increasing order of effort.

The status bar. If you are already on the screen, the system tells you which transaction you are in. Setting the status field to show the transaction code permanently is a one time change worth making on day one.

Search the menu. The SAP menu is searchable by text, and the technical names setting displays the code beside every entry. Turning that setting on is the single fastest way to learn codes, because you see them constantly without looking anything up.

The tables. TSTC lists every transaction code in the system and TSTCT holds their descriptions in each language. A text search against TSTCT finds the code when you know roughly what the function is called. SE93 is the maintenance transaction and shows what a code actually starts, which is how you find out that two codes are the same program with different parameters.

• Menu-hunting instead of using codes.
• Wrong variant (create vs display).
• Not knowing the codes for your own area.

Version note: transaction codes are alive and well on S/4HANA, and the strategic interface is Fiori. Both are true at once, and in practice most implementations run both, with power users on transactions and occasional users on applications. Some transactions have been retired where the underlying function was simplified away, and the code will tell you so when you enter it. See VA01, VA02, VA03 and WE02 for individual pages in this set.