Hi Nikhil,
Please try out below options. This might be useful for you.
option 1-
● OTR short texts: object type LIMU SOTT
● OTR long texts: object type LIMU SOTU
You can, however, also transport all texts that belong to a package, independently of an object. To do this, create a transport request:
● For OTR short texts, use the object type R3TR SOTR
● For OTR long texts, use the object type R3TR SOTS
Enter the respective package name as the object name. The OTR texts are thus transported in their respective original language.
If, however, you only want to transport texts in a particular language, create a transport request as follows:
● For OTR short texts, use the object type LANG SOTR
● For OTR long texts, use the object type LANG SOTS
Enter the respective package name as the object name. In this case, the system asks you which language you want to transport the texts in.
2 nd Option:
Firstly before you start attempting to translate, you would want to make sure that the translation language is set. In order to do this, in transaction SE63 -> Utilities -> Settings
Now you have your language set up, so translation can begin.
1. Run Transaction SE63 - Under the header menu choose Translation -> ABAP Objects -> Short Texts. Often SE63_OTR does not work and gives an error "Coding is now obsolete. Use transaction SE63 instead"
2. This gives you a list of objects including OT - OTR (SOTR - OTR Short Texts)
Important Note: At times after transporting OTR's they do not display the changed text. In such cases, in Tcode SE38 > run program SOTR_DEFAULT_CONTEXT_FLAG_SET and then reset the OTR buffer using /$OTR
Bluesky
