General Guidelines for Dialogues and Texts
Although the R/3 System has a graphical user interface, texts, mainly single words, still play a very important role in R/3. Words give the screens and dialogues a "meaning", they tell what a screen is about and what it is good for. So, if you use some computer jargon or SAP jargon the users may not understand the screen, and they may not find for the things they want to do. As a result, they may not get their work done.
The ISO 9241 and many other regulations on user interfaces require that software systems are self-descriptive. This means among others that the system speaks the user's language and not some technical jargon. This aspect of user interfaces is far too often underrated. However, it comes up as a constant problem in user testing of the R/3 System. The following general guidelines should help you minimize terminology problems.
Speak the User's Language!
This is the most general guideline for designing field names, error messages, dialogues etc. Keep this guideline always in mind. Write it on a sticker and place it on your monitor!
Use Consistent Terminology!
Do not confuse users with different terms for the same thing. Do not name different things alike. It is also very important to keep terminology consistent between different applications and even between application areas.
Use Approved Terminology!
One means to keep terminology consistent between application areas is the SAP terminology database. This database is being constantly updated.
If there is an approved term in the terminology data base, use this term even if you personally dislike it. Users are familiar with this term and expect it in your application, too.
Think of the Context of Use and the Context of Translation!
Discussing interface terms often leads to heated debates, where personal preferences prevail. Often, the context in which a term is used is not taken into account. There may be similar terms in other applications or application areas with quite a different meaning. In some cases a term may already be used for other objects or actions. Sometimes the second best choice may be in the end the best one, provided all aspects are considered. The R/3 System is such a large system that you seldom can discuss a term in the context of a single application.
Translation is another important aspect that is often overlooked. Sometimes it is necessary that for instance English and German terms be quite different or even divergent. Different terminology may already have been established in these languages. Sometimes a direct translation has a different or even unexpected meaning in the other language. Often translators have to translate terms without reference to context of use. This may lead to a wrong translation if the terms in the original language have not been chosen carefully and unique.
Source: SAP R/3 Style Guide