SAP
SAP Transaction Code List: A Practical T-Code Index by Task
Use this SAP transaction code list to find common T-codes for materials management, invoice verification, database monitoring, system administration, and learning workflows.
On this page
- How to use this SAP transaction code list
- SAP transaction codes for materials management
- SAP transaction codes for inventory and goods movements
- SAP transaction codes for invoice verification
- SAP transaction codes for technical administration
- How T-codes differ across SAP releases
- A study method for learning SAP T-codes
- SAP transaction code troubleshooting checklist
- Conclusion
SAP transaction codes, commonly called T-codes, are shortcuts for opening tasks in an SAP system. The right code depends on the product release, activated scope, authorizations, and whether the system uses classic transactions, SAP Fiori apps, or both.
This independent-study index groups frequently referenced T-codes by task rather than presenting an exhaustive catalog. Use it as a starting point, then verify each transaction in your own system and process documentation.
How to use this SAP transaction code list
Start with the business task, not the code itself. For example, a goods movement may require MIGO, while invoice verification may involve MIRO. A system administrator may instead need a monitoring or configuration transaction.
- Identify the process or technical area.
- Confirm whether the task is for display, creation, change, posting, cancellation, or monitoring.
- Check the relevant organizational scope, such as company code, plant, storage location, or purchasing organization.
- Verify authorization and release-specific behavior in a non-production environment.
- Record the result and any follow-up document numbers or system messages.
A transaction code is an entry point, not a substitute for process controls. Posting authority and segregation-of-duties requirements still apply.
SAP transaction codes for materials management
Materials Management transactions support purchasing, inventory, goods movements, and invoice verification. The same business process can involve several documents, so avoid treating one T-code as the entire workflow.
| T-code | Typical purpose | Useful study question |
|---|---|---|
MM03 | Display material master data | Which views and organizational levels are relevant? |
ME23N | Display a purchase order | Which items, delivery data, and history should be checked? |
MIGO | Process goods movements | Which movement type and reference document apply? |
MB03 | Display a material document in systems where it is available | How do material and accounting documents relate? |
MIRO | Enter or verify an invoice | How do purchase order, goods receipt, and invoice quantities compare? |
MIR4 | Display an invoice document | Which invoice data and follow-on documents require review? |
MR8M | Cancel an invoice document where supported | What business reason and reversal controls are required? |
For a focused explanation of the goods movement entry point, see MIGO basic function. For invoice verification, consult the SAP Help documentation listed in the references.
SAP transaction codes for inventory and goods movements
Use inventory-related transactions to distinguish between a physical movement, a stock adjustment, and a display or analysis step. The exact movement type determines the business meaning of a posting.
| T-code | Typical purpose | Caution |
|---|---|---|
MIGO | Post or display supported goods movements | Confirm movement type, quantity, plant, and storage location. |
MB51 | List material documents | Filter carefully by posting date, plant, movement type, or material. |
MMBE | Display stock overview | Check the stock category and organizational level. |
MI01 | Create a physical inventory document | Follow the counting procedure and authorization rules. |
MI04 | Enter a physical inventory count | Confirm the correct inventory document before saving. |
MI07 | Post an inventory difference where supported | Review variance approval and accounting impact. |
A material document can have an associated accounting document, but the relationship and available follow-on displays depend on the posting and system configuration. Always validate the document flow in the relevant system.
SAP transaction codes for invoice verification
Invoice verification compares supplier invoice information with purchasing and receipt data. Common checks include quantity, price, tax, tolerances, payment blocks, and reference documents.
| T-code | Typical purpose | Study focus |
|---|---|---|
MIRO | Enter an invoice or credit memo | Understand reference selection and variance messages. |
MIR4 | Display an invoice document | Trace document status and related references. |
MRBR | Release blocked invoices where configured | Identify the reason for the block before release. |
MR8M | Cancel an invoice document where supported | Confirm reversal prerequisites and period controls. |
MIR6 | Review invoice document lists where available | Use selection criteria that match the investigation. |
SAP’s Online Invoice Verification documentation explains the process context. The transaction names and available functions can vary by release and implementation.
SAP transaction codes for technical administration
Technical T-codes are often used for monitoring, configuration, transport, jobs, users, and system health. Access is typically restricted, and a display transaction may be safer for initial investigation than a change transaction.
| T-code | Typical purpose | Operational note |
|---|---|---|
SM21 | Review system log entries | Correlate timestamps, users, and affected application servers. |
SM37 | Monitor background jobs | Check job status, logs, steps, and scheduling details. |
ST22 | Review ABAP runtime errors | Capture the short dump context before changing anything. |
SM50 | Monitor work processes on an application server | Treat termination or intervention as an authorized action. |
SM51 | Display application servers | Use it to understand the system landscape at a basic level. |
STMS | Access transport management functions | Follow the organization’s change and import process. |
SU01 | Maintain user master records where authorized | Apply identity, approval, and audit controls. |
RZ10 | Maintain profile parameters in supported scenarios | Test and document parameter changes carefully. |
DB02 | Monitor database-related status and data in supported environments | Interpret values with the database platform and release in mind. |
For database monitoring context, review SAP’s SAP/Oracle Database Monitor documentation and the related guide to T-code DB02.
How T-codes differ across SAP releases
A transaction can exist in one release and be replaced, restricted, or supplemented by another interface in a later release. SAP S/4HANA implementations may also expose the same business capability through SAP Fiori apps.
Before memorizing a code, check:
- SAP product and release
- Activated business scope
- User role and authorization objects
- Client and organizational assignments
- Classic transaction versus Fiori app availability
- Whether the transaction is intended for display, testing, or production posting
This is especially important for older inventory and financial workflows. A code shown in a training system may not behave identically in a configured production system.
A study method for learning SAP T-codes
Memorizing isolated codes is less effective than mapping each code to a process, document, and control point. Build a small study table with these columns:
| Field | Example |
|---|---|
| Business process | Goods receipt for a purchase order |
| Entry point | MIGO |
| Main input | Purchase order, movement type, quantity |
| Output | Material document and possible accounting document |
| Validation | Stock, document flow, and posting status |
| Control | Authorization, approval, or reversal rule |
Use a sandbox or training client to practice display functions first. Then document what changes after saving, which messages are generated, and how to reverse or correct the transaction according to the process design.
For broader preparation, combine this index with a SAP system administration study guide or a S/4HANA conversion learning roadmap.
SAP transaction code troubleshooting checklist
When a T-code does not work as expected, separate access problems from process or data problems.
- Confirm that the code is entered correctly and is available in the target system.
- Check the user’s authorization and assigned role.
- Review the selected company code, plant, storage location, or purchasing organization.
- Validate required master data and reference documents.
- Read the full system message and record its class or number when shown.
- Check whether the transaction is restricted by posting period, document status, or configuration.
- Reproduce the issue with a suitable test case before escalating.
Do not bypass authorization checks or alter production data merely to make a transaction complete. Escalate unclear results to the process owner or SAP support team.
Conclusion
A useful SAP transaction code list connects each T-code to a business purpose, expected document flow, authorization boundary, and release context. Start with the task, verify the transaction in your system, and maintain your own version of the index as configuration and interfaces evolve.