Naming conventions should be considered carefully.
Naming Object Rules
For attribute names, the following rules apply:
If you are in a customer environment, where attributes have clear and unique semantics, don't use a prefix, for example, PRDID.
If you are in a demo/test environment, where different people/teams have to work together, use a prefix, for example, SM1PRDID.
Models (master data types and planning area) should have a three-letter prefix, for example, SM1, CP1, and so on.
This is usually the company’s Ticker symbol.
Master data types should start with a three-letter prefix, for example, SM1PRODUCT.
Planning areas should start with a three-letter prefix, for example, SM1.
Planning levels and key figures should not have a three-letter prefix.
Naming Object Issues
Do not use any short forms when naming master data types. For example, use CP1PRODUCT instead of PRD.
You can use short forms when defining attributes, for example, CP1PRDID, SP1CUSTID, and so on.
It is good practice to name an attribute identifier with the suffix ID. For example, SM1CUSTID is the identifying attribute of CUST.
Identify descriptions’ attributes using the suffix DESCR. For example, SM1PRDDESCR is a description attribute for product.
Do not mix different synonyms for an attribute. For example, do not use PRDID, MATERIALDESC, PRODUCT, or SKU (all referring to product).
Use SM1PRDID, SM1PRDDESCR, SM1PRDFAMILY, and so on, as attributes, if the master data type is SM1PRODUCT.
Additional Naming Object Issues
Avoid situations where the master data type name is also the attribute name.
Avoid marking non-key attributes as required.
Do not use special characters, for example, underscore and space, in any ID field.
Good Practices
Key figure names should not be long. Keep names less than 25 characters in length.
Key figure ID naming should be meaningful. Use the full name or the abbreviated form as much as possible, for example, SALESFORECASTQTY. A bad example is SLFCQTY.
Key figure naming should clearly represent what is quantity versus value key figure, for example, SALESFORECASTQTY versus SALESFORECASTREV.
Descriptions of attributes and names of key figures should be short, so they are more readable in planning views.
Additional Good Practices
Use the planning level ID to clearly represent the master data types involved. For example, MTHPRODCUST represents period, product and customer.
Start all helper key figures with the prefix H.
Do not use the term SELECT anywhere. The following are bad examples: an attribute MCK1SELECT, a key figure B1SELECT, and a planning area CL1SELECT.
Avoid using time profile ID 1, as it is an SAP-delivered sample.
Do not use special characters when defining a template or favorite.