In case your environment uses multiple languages, you will have to deal with translating any text for custom screen elements such as new fields, buttons etc. that are not part of the underlying transaction. This post will summarize the steps necessary to complete the translation.
Let’s start with a simple test flavor, containing a few labels and buttons:
Translation is initiated from the Personas admin transaction:
Click on the + sign to select the flavors you want to translate. At this point you may receive an error message complaining about a missing package, unless this was already taken care of earlier (so this is a one-time activity):
This is because Personas translation works by creating Online Text Repository objects and these are categorized as development workbench objects which must belong to a package. So if this happens, head to the IMG and go to Personas configuration: Cross-Application Components –> SAP Screen Personas –> Maintain Personas Global Settings. Here, enter the name of an appropriate package for your OTR objects:
I usually designate (create) a specific package for Personas development objects. This could be also used for WebRFC function modules for instance.
Return to the Personas admin transaction and now you should have no problem with selecting the flavors you’d like to translate. When you add a flavor, the transaction will grab all associated text elements that are relevant for translation. Click on the ‘Create OTR Objects’ button:
The system is going to ask for a transport request, so assign the OTR objects to one:
You will get a confirmation message:
Now you are ready to take care of the actual translation. This is done using transaction SE63. In the menu, navigate to Translation -> ABAP Objects -> Transport Object. Here, you have to individually identify all the text elements that were included in your transport. In order to do this, use transaction SE10 to display the transport request you just created, it will contain the OTR object key specifications:
Copy/paste the transport entry fields for each text listed here into the corresponding SE63 fields, specify the source- and target language, click on ‘Edit’, then enter the translation:
Hit the pencil/paper symbol and on the next screen click on the button ‘Status S’. At this point, you should see this:
Save your translation, then go back (F3) to the selection screen and repeat the same steps with all OTR objects in your transport request.
Once all of them are translated, you can test the result by logging out of Personas, then back in with your target language. You should see the translated texts in the flavor. In my case, only Object Number was translated, the rest is still in English: