Translating Tiles, Catalogs, and Groups in the Customizing Layer

You want to change the translated text of custom tiles, catalogs, or group titles in the SAP Fiori launchpad. This is possible using the standard SAP translation tools.

Context

An end user of the launchpad has reported an issue with a translated text in a custom tile, catalog, or group title.

To find the text in the translation system and correct it, translators require the text ID and the configuration ID. To retrieve these IDs, you use Fiori Launchpad Checks (transaction /UI2/FLC).

To translate the texts, you access the standard SAP translation environment. The translation follows the standard ABAP translation process. This is the same process as for translating Web Dynpro customizing.

Caution To translate texts, only start SAP Fiori launchpad in the original language. Otherwise, you receive an error message when saving the configuration.

Procedure

To find the relevant texts in the translation system, determine the configuration ID and the text ID:
1. In the system in which you run the SAP Fiori launchpad (on the front-end server for SAP Fiori launchpad), start Fiori Launchpad Checks (transaction /UI2/FLC).
2. (Optional) In the Catalog ID field, enter the ID of the catalog.
3. In the Adaptation Layer section, choose Customization.
4. Mark the With Text ID checkbox.
  
  This option displays a text ID for tiles, catalogs and groups (e.g. M : 1, P : 2).
5. Choose Execute.
  Note the entry in one of the following fields:
  - Tile Title Text ID
  - Catalog Title Text ID
  - Group Title Text ID
6. Depending on the first part of the text ID, proceed as follows:
  - M: Copy the configuration ID from the Main WD Config Key field.
  - P: Copy the configuration ID from the Property WD Config Key field.
In the system in which you run the SAP Fiori launchpad (on the front-end server for SAP Fiori launchpad), start Initial Screen: Translation Editor (transaction SE63).
Choose Translation ABAP Objects Short Texts .
The Object Type Selection (Object Groups) dialog box appears.
Expand the 00 Meta Objects node and select the meta object type TABL Tables.

The ABAP Short Texts: Tables (Meta) screen appears.
Use the value help to search for *WDY_CONF_USERT2* in the Object Name field.
Select the required source and target languages.
The language of the transported table entries is defined in the data dictionary as a property of the table. The texts you create will only be transported if the language is the same as defined in the data dictionary.
Choose Edit. Enter the following data in the table that appears:
1. Enter A for the User Scope to change only the texts for objects in the Customizing scope.
2. Enter 07 as the Configuration Type to limit the result set to texts relevant for the SAP Fiori launchpad.
3. Enter the configuration ID you copied before (see step 1.6).
Choose Execute.

This takes you to the standard translation environment.

To find the relevant text in the result list, search for the number given in the second part of the text ID (see step 1.4).
(Optional) After the translation is completed, an administrator needs to invalidate the back-end caches for all users for which texts may still be stored in the wrong language. To do this, call transaction SE38 and run the report /UI2/INVALIDATE_GLOBAL_CACHES in execution mode. Administration authorization is required to run this report (authorization object: /UI2/CHIP, field ACTVT: 06).

Note
This step is only necessary for systems, in which the launchpad is actually used. It is not necessary for systems used only for translation.

Results

Your custom tiles, catalogs, or group titles are displayed with the intended text in SAP Fiori launchpad.

Note

You can transport text table entries in Customizing for SAP Fiori launchpad in different languages using transaction CUS_ORIGLANG.