
You display a screen, and notice a text that you want to change or correct. The text is a translation, rather than a text in the original language. You therefore need to use transaction SE63 to call up the translation object to which the text is mapped, and then change the existing translation. To access an object directly for translation, you need to know the following:
A typical screen consists of various development objects, all of which contain their own texts. There is no 1:1 mapping of transport object types to translation object types, which can make it difficult for you to find the required translation object.
The translation object detective makes it far easier for you to find translation objects that you want to call up in transaction SE63.
The following example illustrates how you can use the translation object detective to find a translation object that you want to call up in transaction SE63.
Example
Data element COAT_VALUE contains the following five texts under language key DE (German):
Under language key EN (English), data element COAT_VALUE contains the following five texts:
After you have activated the translation object detective, data element COAT_VALUE contains the following five texts under technical language key 1Q:
DTEL (data element) is the translation object type.
COAT_VALUE is the technical name of this specific translation object.
You can log onto the system with technical language key 1Q, call up a screen on which the text Wert appears under logon language DE (or Value under logon language EN), and see at a glance that the text is in fact mapped to a translation object with the object type DTEL (data element) and technical name COAT_VALUE. This information enables you to call up the translation object in transaction SE63, and change translations as necessary.