How to get a list of All SAP Transaction codes in Excel
In a similar vein to my previous posting about extracting the IMG in Excel, you may also want to get a list of Transaction codes out of SAP into Excel to allow for various management tasks. I have used these to track the development of BPP’s assist in designing authorization roles etc, and general project management.
Anyhow this is a much more simple process than extracting the IMG as we’re just extracting a table to Excel.
Basically the transaction code and description information is held in a transparent table TSTCT to get the descriptions in all languages maintained. Using transaction SE16N you can query the table directly and extract to excel. Limit the display to show only the language you are interested in
This table holds a lot of entries (over 100k in each language) so you may want to perform multiple extracts for different areas. For simplicity I am going to extract only the ME* transactions in materials management of which there are 310 in this example
Make sure that if you check the number of entries you should enter that number in the maximum number of hits (if its higher)
Now you have a list of transaction codes with their descriptions that you can easily export to excel
from within the results press the export icon then local file (depending on the version of the sapgui and the version of excel you can directly press the spreadsheet option, but I have encountered problems with office 2007 using this method)
from the local file menu select spreadsheet
give the file a name and save it to the desired location
compared to the IMG extract there is very little clean up required
I like to remove the white space and language column then format it as a table
Another table you can use instead of TSTCT is TSTCV this also has the program name and screen number which you may find useful (or not)
I have seen copies of this list being sold as a PDF on ebay and elsewhere, when it really only takes five minutes to get your own list. (maybe a bit longer if you want to run this report for all transaction codes and not limit it in any way.
Anyway, if you find this article useful please let me know via the comments

That breaks down in ECC 6.0; too many rows for Excel.
I download to a text file, open with a word processor or text editor, take out the irrelevant T-codes (depending on the situation), then move it to Excel.
-BobSchenot
Hi Bob, yes Excel 2003 won’t be able to support the numerous rows, however excel 2007 does.
Very good informaTION
Ok I had a great deal of requests for the pdf version of this post which I was offering only to twitter followers but here is a link for you to download the file without following me on twitter
http://www.consulting.mungapen.com/downloads/1
Great tip!
I just ran this with our querySHUTTLE tool against our ECC Ides system. am using Excel 2007 and it extracted 81557 records in 22 seconds!