SAP T-code Naming

Most SAP transaction names follow a practical pattern: prefix + number (+ optional suffix). Prefix is usually connected to a functional area, while numbers separate actions inside the same family.

Example: ME21N and ME22N are in one MM purchasing family: create and change purchase order.

How to read common prefixes

• ME* - purchasing documents in MM (Materials Management).
• MB* - material movements and stock reports in MM.
• MI* - invoice verification and inventory-related operations (MM/FI intersection).
• VA* - sales order transactions in SD (Sales and Distribution).
• VL* - outbound delivery flow in SD.
• VF* - billing and invoice output in SD.
• FB* and F-* - financial postings and payments in FI (Financial Accounting).

Why this matters for consultants

• Faster root-cause analysis: prefix tells you where to start.
• Better communication with key users: you can map issues to transaction families.
• Cleaner training plans: learn flows by prefixes instead of random isolated codes.

Mini FAQ

Is naming always strictly logical? Not always. SAP has historical naming, so there are exceptions.

Does suffix N always mean new? Often yes in classic GUI context, but treat it as convention, not universal rule.

Can one process use multiple prefixes? Yes. End-to-end flows frequently cross MM, SD, and FI.