Translating standard SAP Fiori apps into your own language
SAP is rapidly developing a great number of SAP Fiori Tiles. Users are delighted about the functionality, but unfortunately not all languages are supported.
For example, Dutch language is not provided for the standard Tiles.
Still, customers would like to have their Tiles available in their own language. How to handle?
There are actually 3 steps:
- 1. Tile title
- 2. Tile text elements
- 3. Messages
I’ll explain the steps using the standard SAP Tile Customer Invoices.
Step 1 – Tile title
The Tile title is actually defined in the tile catalog. To translate the tile, you need to start the Launchpad Customizing. The URL is http://<yourserver>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?scope=CUST
You need to logon in the language to which you want to translate.
- 1. Create new catalog by using existing standard catalog and dragging it to left bottom.
In the pop-up screen enter the name of the new catalog:
- 2. Rename all tiles to your description (Dutch in this case)
Enter Title and Subtitle. Don’t forget to save.
- 3. Create new catalog group
First click om Groups on top left. Then click on button ‘+’ on bottom.
Create a new group with a clear description and ID and save it.
- 4. Add tiles by clicking on ‘+’ in tiles
First select the catalog to choose from. This is the catalog you created in the first two steps.
All tiles are presented. Click on the ‘+’ under each tile you want to add to your group.
When you’re done, go back to the group screen.
Now your new Fiori Catalog Group is created.
- 5. Create new PFCG role for your new Fiori Catalog Group and add this to your user
In Gateway, create new single role in transaction PFCG.
Enter the name of your role and a description.
Click on tab Menu.Click on button and choose SAP Fiori Tile Group
Add your newly created Tile Group from step 4.
Click on button and choose SAP Fiori Tile Catalog. Add your newly created Tile Catalog from step 1.
Save your new role and add this to your user.
Logon to your Fiori Launchpad again. Your new group will be available now on your homepage.
Your tiles now all have your own description (in your own language).
However, your tile itself is still not in Dutch:
Step 2 – Tile Labels
There may be more ways to translate tiles, but I’ll be using the solution by enhancing the BSP application and adding a new properties file for your own language to the BSP application.
To find the name of the BSP application, you can go to the SAP Fiori Reference Library.
In the Implementation Information, you can find the name of the BSP application under header Configuration and then SAPUI5 Application.
- 1. Start transaction SE80 in your Gateway system.
Under the folder Page Fragments, open the folder i18n.
- 2. Copy existing properties file to a new file for your own language
Select one file and right click on it and select option Copy
Enter the new name under Page. The format is:
i18n/i18n_<iso code for your language>.properties
In our case this is i18n/i18n_nl.properties
System will now ask for an object key. Request this via SSCR keys via http://support.sap.com/sscr
Now edit all texts to your own needs. Save and activate the changes.
The texts will still not appear in your own language. You need to clean up your cache first.
- A. On gateway execute program /UI2/INVALIDATE_GLOBAL_CACHES
- B. On Gateway clear cache via transaction SMICM à Goto à HTTP-PlugIn à Server Cache à Invalidate Globally
- C. Restart your browser
Now your Tile is translated.
Step 3 – Tile Messages
We’re almost there. Now we still need to translate some messages that pop-up dynamically.
These message are located in a message class on your backend system. In this case, it is SAP ERP.
- 1. Start transaction SE91 and enter message class
For our Tile, the message class is CM_SRA021_INVOICE.
- 2. Select the messages and translate each individual text via Goto ->Translation
After the translation is done, refresh your browser. Now the message is also displayed in Dutch.
You can also try the transaction SE63.
Translating Tiles, Catalogs, and Groups in the Customizing Layer - SAP Fiori Launchpad - SAP Library
Thank you so much for the valuable information.
I've seen your reply for UI5-relevant questions else where, and they are all wonderful. 😎
Hope I can see your comment more often. 🙂
Which is the recommended way for doing the translations?
From the Launchpad Designer or from the SE63 t-code?
I understand that if I create the translations from the se63 t-code, I will have the same "Catalog identifier" for the original and the translated catalog, while if I do the translation from the Launchpad Designer, I would have two different identifiers and I would have to assign one of this two catalogs depending on the country the sap user uses the erp system.
Instead, If I use the se63 t-code I could assign the same catalog for all the different users worldwide that use the same fiori app.
Is that correct?