You must translate SAPterm terminology entries in SAPterm itself. However, when you translate glossary entries, you have two options:
Translating Glossary Entries in SE63 Translation Worklists
Prerequisites
In order for the definition text to appear for translation in SE63, you must first translate the term's designation in SAPterm. The definition will not appear in your worklist for translation if the designation is not available for the header information.
Translate the term's designation as early as possible. If you translate it too late in the release cycle, the definition may not be included in the final worklist run.
Procedure
Result
The definition text will appear in your worklist after the next worklist run. You can use the split screen editor to translate the definition more easily, without running the risk of changing or deleting the source text. For more information, see
Functions in the Split Screen Editor.Translating Glossary Entries in SAPterm Manually
Use
If a glossary entry was not included in a worklist run or needs to be translated quickly, translate the definition text manually. You can copy and paste the source text into the definition field for the translation, then overwrite the source text with the translation.
Procedure
Do not make any changes or deletions to the definition text itself without the consent of the author.
You cannot create a glossary entry without saving the term first. The term and its application component ID serve as the header for the definition text.
Result
The definition text is translated and will not appear in your translation worklist unless it is changed between worklist runs. It then appears as a modified long text.