If you’ve supported SAP users for any length of time, you’ve answered some version of this question more times than you’d like: “What’s the T-code to do X again?”
It comes from new joiners, from finance people who occasionally need an MM transaction, from supply chain folks who dip into WM. And from consultants too, when we step outside our home module. SAP’s transaction-code system spans tens of thousands of codes across MM, SD, FI, CO, PP, HR/HCM, PM, QM, WM, PS, Basis, ABAP, CRM, SRM, BW, and the rest. Nobody memorizes all of it, and nobody should have to.
What’s changed over the last couple of years is the way teams answer that question. Not because anyone has gotten better at memorizing, but because the tooling around T-code discovery has improved. I want to share what I’ve seen working on a few recent projects, and what hasn’t.
Why the old approaches stopped scaling
Most teams cycle through the same lookup methods, roughly in the order they adopt them.
Printed cheat sheets and PDFs. Every SAP project I’ve joined had one floating around. They’re useful on day one and stale by month three. The moment SAP renames a transaction, splits one in two, or marks something as “do not use in S/4HANA,” the cheat sheet starts misleading people.
The SAP Easy Access menu and Favorites. Complete in theory, unbrowsable in practice for anyone who doesn’t already know the menu path. I’ve watched experienced users scroll for two minutes looking for something they could have typed in four characters, if only they remembered which four.
SE93 (Maintain Transaction Codes). Useful when you know part of the code or want to inspect the underlying program. Less useful when all you know is what the business process is called in plain English.
Internal wikis and Confluence pages. These work right up until the person who curated them leaves, or until S/4HANA introduces Fiori-app equivalents that nobody backfilled into the wiki.
Generic web search. Returns an ocean of forum posts of varying ages, half of them referencing transactions that have been deprecated or replaced. You usually find the answer. It just takes a lot of clicking for a four-character payoff.
What all of these methods share is an unspoken assumption: that the user already knows enough SAP vocabulary to translate intent into transaction code. For cross-functional users and new joiners, that assumption is exactly where the wheels come off.
What’s different now
Two things changed recently that make the problem more tractable.
The first is that the SAP Fiori Apps Reference Library has gotten noticeably better. SAP recently relaunched it at fal.cloud.sap (the older URL fioriappslibrary.hana.ondemand.com still works for now). You can search by classic T-code and see the corresponding Fiori app or apps, the business role, the line of business, and the product version. For S/4HANA migration work, this has saved me a lot of guessing. It’s the authoritative SAP source for the ECC-to-Fiori mapping question.
The second is that AI-assisted search has reached the point where natural-language queries actually work. Vector embeddings let a phrase like “create a purchase order” land in the same semantic neighborhood as ME21N, even though the two share no keywords. LLM re-ranking then surfaces the most likely match at the top of the list with a short explanation. Together, those two pieces produce a search experience that works for people who don’t already speak SAP.
I’ve tried a few community-built tools in this space. One I keep coming back to is TCodeAI (tcodeai.vercel.app), a free web app that lets you search either by code (MIRO) or by intent (“post a vendor invoice”) and ranks the results with a short note on why each match was suggested. It also includes Fiori-app mappings alongside the classic codes, which helps during the dual-stack ECC/S/4HANA period most teams are living through. I’m not affiliated with it. I find it a useful complement to the official Fiori Apps Library when I want a faster, conversational lookup.
Other tools are moving in the same direction, including SAP’s own Joule copilot work and various module-specific search add-ons. I expect the space to keep maturing.
A few caveats are worth keeping in mind for any AI-assisted T-code tool:
- Always verify against your own system before sharing a code with end users. What’s available depends on your release, your activated business functions, and your authorizations.
- Treat AI explanations as starting points, not gospel. These tools are good at narrowing the field, less good at understanding your specific configuration.
- Deprecated and S/4HANA-restricted transactions are a moving target. Cross-check anything critical against the SAP S/4HANA Simplification List or the Simplification Item Catalog in the SAP ONE Support Portal.
A practical workflow for 2026
If I had to describe what a healthy T-code lookup workflow looks like today, it would be roughly this:
- For Fiori and S/4HANA mapping questions, start with the SAP Fiori Apps Reference Library.
- For “I know what I want to do but not what it’s called,” use whatever AI-assisted search tool fits your team’s comfort level. TCodeAI is one option, but it isn’t the only one.
- For deep validation, including release behavior, deprecation status, and replacement guidance, use the SAP S/4HANA Simplification Item Catalog and the linked SAP Notes via the SAP ONE Support Portal.
- Keep your team’s internal cheat sheet small. Focus it on the codes specific to your customizations and Z-transactions.
The broader point is this. We’ve spent a long time treating T-code memorization as a kind of rite of passage in SAP. It doesn’t have to be. The tooling has caught up enough that new joiners can focus on understanding the process and look up the codes the way the rest of us look up everything else.
I’d be curious to hear what others are using. If you’ve landed on a workflow that’s cut down on “what’s the T-code for…?” interruptions in your team, leave a note in the comments.
Â
  Read More Technology Blog Posts by Members articlesÂ
#abap