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

[dineshcbe]

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.

[claire_yang · Accepted solution]

Hi,

No.

We don't have such rules to define the tcode. You can also define your own tcode in SE93.

Regards,
Claire

[former_member182378]

Dinesh,

Members have posted interesting and informative replies!

There might not be an over-arching nomenclature (system) but looking at it from SD pov, the transaction codes start with V e.g. VA01, V/06 etc. There could be exceptions to this.

My technique is "chunking"...let us take a small portion as a chuck and it will be easier to find trends e.g. for copy control functionality -

order to order, VTAA

order to delivery, VTLF

order to bill, VTFA

delivery to bill, VTFL

here, order is named as A, delivery as L, bill as F; if you look into this chunck, you will find a system.

TW

[Former Member]

Dinesh,

Is the T-codes are defined with the same principles as above.....?

No.

Back in the day of SAP R2, you could get by using expert Lazlo's observations.  Now, however, ECC has more transactions that are exceptions to his rules than it has transactions that follow his rules.  For instance, a standard ECC system has over 3500 transactions beginning with 'C'; only a small portion of them are related to production planning.  We haven't even begun talking about SAP's non-ECC software offerings, which offer a bewildering array of non-intuitive transaction codes.

The more you become exposed to SAP's various software offerings, the more you realize that there is very little overall consistency in their transaction naming methods.

Better to use the menu, or create 'favorites'.

Best Regards,

DB49

[Laszlo_B]

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

[former_member38225]

Dinesh,

there is no standard but there are common guidelines that companies use. A typical one for example is the following and by no means is this the only, you can do a google search and find quite a few out there but they are similar.

customer Name Space Z or Y + module + a program name (Up to the 20 character limit of course)

for example

ZSD_ATPREPORT

Hope that gets you started, here is what we use

http://wiki.advsolutionpros.com/index.php?title=ABAP_Style_Guidelines#Transaction_Codes

Later.....