Glossary in SAPterm
Use
A glossary entry contains the definition of the concept to which the term refers.
To see glossary entries as they are displayed on the documentation CD, choose in any system.
Which Terms Require Glossary Entries?
-
Terms that appear only in SAP products and that are not defined anywhere else.
-
Terms with variant meanings in different contexts need to be defined in an SAP context in order to avoid misunderstandings.
-
Many (but not all) specialist terms in business, specific industries, or information technology must be defined in an SAP context in order to relate them to the use of SAP products.
What Is Not a Glossary Entry?
-
Terms defined by other companies for their products.
-
Terms with generally understood meanings and usage ( computer, accounting). Term entries may be necessary to standardize a translation; glossary entries, however, are superfluous.
Glossary Links
SAPterm assigns each terminology concept a globally unique identifier (GUID) in the background to distinguish the entry from all other entries. The GUID is 32 characters long and thus unique.
When you create a link to a glossary entry, the link uses the GUID to display the appropriate glossary entry based on the contextual information in the object. For example, a glossary link in English-language documentation displays the English glossary entry. Other contextual limitations would include release, country, and industry.
All glossary entries exist simultaneously as identical SAPscript and HTML files. This allows you to set links from SAP System documentation and from Knowledge Warehouse (KW) documentation.
SAPscript glossary entries are created immediately in a database table to be distributed to other systems as part of the language transports from the translation system. You can thus create links from system objects to new entries if the table is available in the system you are working in. For more information, see Links to other Objects.
HTML glossary entries are replicated in the Info Repository within a few minutes or in an automatic, overnight background job if you choose to wait. You can create links from KW documentation to new entries as soon as the HTML exists in the Info Repository.

