SAP follows any std Nomenclature while defining a T-code....?

Question

Dear Friends :
Usually industries follow some std while define their Materials, Drawings etc., called "NOMENCLATURE"
for e.g., see the,
Material Number : LT123456
where,
First 2 Digits says their CUSTOMER
Second 4 Digits says model of the PRODUCT
Last 2 Digits says PRODUCT LINE to which the material belongs.
MY QUESTION IS :
Is the T-codes are defined with the same principles as above.....?
Thanks With Regards,
Dinesh Kumar V.

Answer 1

Hello Dinesh,
although such standards / rules really do not exist, you might get a rough idea what the transaction is about based on the first (two?) characters of the transaction code.
Unfortunately there are a lot of "counter-examples", but:
transactions starting with 'S' are usually related to System / Basis related programs: SP01 = Spool request administration; ST01: System Trace; SM50: overview of spool wokrprocesses; etc.
transactions starting with 'M' are usually related to Material Management: MIGO = Goods Movement; MM02 = Change Material; etc.
transactions starting with 'C' are usually related to Production Planning: COGI = Postprocess Faulty Goods Movements; CM25 = Capactiy leveling: Variable; etc.
The problem with this theory is that there are a lot of "counter-examples", for example: I18N is responsible for internationalization yet the transaction code does not start with 'S'; transaction CG3Y allows the download of files from the R/3 server to the frontend yet this transaction has nothing to do with Production Planning, etc.
Aside from these, you can see a pattern in a lot of transaction codes.
Best regards,
Laszlo