Skip to Content
Personal Insights
Author's profile photo Sudhan Nagarajan

Translating a standard/custom Fiori tile using Fiori Launchpad App Manager

Problem statement:

Whenever we create a custom tile for a standard or a custom Fiori application, we need to handle the translation part of the tile. This translation is usually done in SE63 for the business catalogs. Let’s talk about a scenario where the app needs to be assigned to ten different business catalogs. In this case, doing translation for all the the ten might be tedious and repetitive.



To overcome this, we can translate the tile that will be present in the technical catalog. As this tile will be referenced in all the other business catalogs, the translations will also be carried out.



For this scenario, I have taken a custom tile that calls a standard Fiori app F2332 – Cash Flow Analyzer. As I have added a keyword (Same as app ID) during the creation of the tile in english, it will not be available in other languages. The requirement now is to translate the tile (Keyword to Spanish).


The transaction ‘/N/UI2/FLPAM’ (Fiori Launchpad App manage – It is alternative to transaction /N/UI2/FLPD_CUST as it’s obsolete) is launched and the respective technical catalog is opened.



Post this, the desired app is selected using the checkbox and the dropdown ‘Translate with language selection’ is clicked.



This will take us to the screen similar to SE63 with the unique ID of the catalog prefilled. Change the target language of the translation. In this case, its Spanish. Then click on ‘Edit’ button.


Here the catalog is displayed as the leaf nodes. We need to double click to select the catalog and to view the list of texts that can be transported.


Now I have my texts that can be translated. In my case, I needed my Keyword to be translated. Hence I would be needing to provided the keyword in the highlighted area.


I have provided the same keyword in Spanish as well as the app ID is not going to change.


Then clicking on ‘Save’ will capture the translation changes.


Note: You need to capture the translations using the transaction SLXT in a transport and move it across if you need these translations to be available in Quality and Prod.


Now, the logon language has been changed to Spanish and the app ‘F2332’ has been searched. The app has been found as shown.


Feel free to add more info to the blog in the comments!


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.