Translate on-premised Fiori LaunchPad Tiles in different languages on the ABAP stack
Last time I was at a customer and he ask me to translate the static tiles of the launchpad in different languages. After a search on SCN I found that this topic wasn’t covered yet, so I decide to share my knowledge.
This document will bring you step by step to the translation.
Before we can start with the translation, we first must know the tile we want to translate. For this we will go to the Fiori LaunchPad Designer and search for the catalog of our tile.
In this example we will translate the text of the Google Search tile to Dutch. Important for the translation is the id of the catalog with is located in the left upper corner. In our example this is ‘ID : X-SAP-UI2-CATALOGPAGE:/NL4B/AppLauncherStaticUrlExample’
We need this catalog id later to find the right object to translate.
Most of the translations within the ABAP stack can be done in transaction SE63. This is also the starting point for our translation. In the top menu we choose Translation -> ABAP Objects -> Short Text or shortly press CTRL-F2. This will open a screen where we can select the type of object we want to translate.
In our case, we need the object type TABL Tables (Meta) which can be found below 00 Meta Object in NetWeaver stack 7.40 or higher. Before NetWeaver 7.40, you will find this object below A6 Table Entries.
After we select the object type we will get a selection screen, we need to fill in. All the static text of out Fiori Launchpad Tiles can be found in object ‘WDY_CONF_USERT2’. This is the object name we need to fill in and we have to specify our source and target language. In our example we will translate from US English, shortly enUS to Dutch shortly nlNL.
After clicking the Edit button, we will again get a selection popup. In this case we need to select the object we need to translate and in our case this is the Fiori LaunchPad Catalog. The Fiori LaunchPad Catalog objects are located as User Scope ‘A’ , Configuration Type ’07’ and a Configuration ID.
To find the Configuration ID, we can use the search help of this field. We can do this by selecting the Configuration ID and clicking the match code button or F4. Now you will get a list of all configurations.
You can find the right Fiori Launchpad Catalog in this list by clicking the button on the top. This will open the restriction screen. Now we need the catalog id of the preparation step. This id we fill in the description field.
The description field in the restrictions is restricted so properly you cannot copy the complete catalog id. In this case replace ‘ID : X-SAP-UI2-CATALOGPAGE:’ by a ‘*’. E.g. ‘ID : X-SAP-UI2-CATALOGPAGE:/NL4B/AppLauncherStaticUrlExample’ becomes ‘*/NL4B/AppLauncherStaticUrlExample’
Now you can select right Configuration ID and execute.
Now you can translate the Launch Pad Catalog text.
After the translation you need to press the save button, The translation is completed.
As a final step we now need to check the result. This can be done in the Fiori Launchpad or the Fiori Launchpad Designer by setting the url query parameter sap-language.
|Fiori LaunchPad Designer|