For the purchase requisitions there is now the extra information that transaction code ME51n can be used for "Create", ME52n for "Change" and ME53n for "Display".
Is there a system behind the transaction codes?
That may sound cryptic but in many cases a certain logic shows through when you look more closely. As an example here are some transaction codes with their German and English meaning:
|FB01||Beleg buchen||Post Document|
|FB02||Beleg ändern||Change Document|
|FB03||Beleg anzeigen||Display Document|
|MB01||Materialbeleg buchen||Post Material Document|
|MB02||Materialbeleg ändern||Change Material Document|
|MB03||Materialbeleg anzeigen||Display Material Document|
|ME21||Bestellung anlegen||Create Purchase Order|
|ME22||Bestellung anlegen||Change Purchase Order|
|ME23||Bestellung anzeigen||Display Purchase Order|
|ME21n||Bestellung hinzufügen||Create Purchase Order|
|ME22n||Bestellung ändern||Change Purchase Order|
|ME23n||Bestellung anzeigen||Display Purchase Order|
Table 1: Examples of transaction codes in SAP®
A system can be detected from the examples in this table, three cases of which I want to illustrate. These are not (!) generally valid – for that purpose SAP® is too extensive and powerful. But you find them running like a thread at many points and in different SAP® modules.
1. Meaning of last digit in transaction codes
Often you can see from the last digit what possibilities a SAP® transaction offers the user. If it ends with "1", it is often a transaction with which things can be created or posted. A "2" often stands for transactions by which existing elements can be changed, and a "3" is characteristic of display transactions (cf table above).
2. Meaning of leading letters
A certain system can sometimes be recognized in the leading letters. Thus in the above table the T-codes beginning with MB are relevant for transactions on material documents, and those with FB for transactions on financial documents. In other words, MB is "Material" and FB "Financial".
3. Transactions ending with "n"
There may be two T-codes that only differ by an "n" added to the end. So you can have a purchase order displayed by the SAP® transaction ME23 and also by ME23n. As an aide-memoire the "n" stands for a "new version" of the transaction, often easier to work with and clearer than the old version.
This enables simple interpretation of analysis results based on transaction codes without having to be an SAP® specialist. Even if in talks it is a matter of the meaning and use in the process, you already have an indication of the contents of the particular code at the time of analysis. That allows well-placed questions and better understanding.
I hope this article has given you some useful background information of a general nature on SAP® transaction codes, and some useful points for approaching your own analytics by explaining the contents and the TSTCT table.
For any comments on this article, feel free to write us at email@example.com.