Home | Translation of SAP FIORI

Translation of SAP FIORI

Translating SAP Fiori Tiles, Catalogs, and Groups in the Customizing Layer

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

Context

The translation follows the standard ABAP translation process. This is the same process as for translating Web Dynpro Customizing.

To translate the texts, you access the standard SAP translation environment.

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

Procedure

  1. To find the texts of the tiles and target mappings of a specific catalog such as MY_CATALOG, determine the configuration ID (CONFIG_ID) of this catalog. Depending on the system version you are using, proceed as follows:
    • For SAP NetWeaver 7.02 and higher:

      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).

        See Checking Launchpad Content.

      2. In the Adaptation Layer section, choose Customization.

      3. Choose Execute.

      4. Choose an entry in the Main WD Config Key field to display the configuration of Web Dynpro component /UI2/PB_EDM_PAGE_LAYOUT for the catalog. Choose an entry in the Property WD Config Key field to display the configuration of Web Dynpro component /UI2/ADAPTATION_PAGE.

    • For SAP NetWeaver 7.0 and 7.01:

      1. In the system in which you run the SAP Fiori launchpad (on the front-end server for SAP Fiori launchpad), start the Data Browser (transaction SE16).

      2. Enter table WDY_CONF_USERT for the Table Name field and choose Table Contents.
      3. In the Data Browser: Selection Screen, enter the following:

        Table 1:

        Field

        Value

        USER_ID

        A

        CONFIG_TYPE

        07

        DESCRIPTION

        ID:X-SAP-UI2-CATALOGPAGE:<catalog id>, for example, ID:X-SAP-UI2-CATALOGPAGE:MY_CATALOG

      4. Choose Execute.

        The configuration ID is displayed in the CONFIG_ID column.

  2. Copy the CONFIG_ID for later use in Initial Screen: Translation Editor (transaction SE63).
  3. In the system in which you run the SAP Fiori launchpad (on the front-end server for SAP Fiori launchpad), start transaction SE63.
  4. Choose Start of the navigation path Translation Next navigation step ABAP Objects Next navigation step Short Texts End of the navigation path.
    The Object Type Selection (Object Groups) dialog box appears.
  5. Depending on the system version you are using, proceed as follows:
    • For systems up to SAP_BASIS 7.31:

      Expand the A6 Table Entries node and select the meta object type TABL Tables.

      The ABAP Short Texts: Tables screen appears.

    • For systems higher than SAP_BASIS 7.31:

      Expand the 00 Meta Objects node and select the meta object type TABL Tables.

      The ABAP Short Texts: Tables (Meta) screen appears.

  6. Use the value help to search for *WDY_CONF_USERT2* in the Object Name field.
  7. 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.
  8. 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 CONFIG_ID you copied before.
  9. Choose Execute. This takes you to the standard translation environment where you can change the texts as needed.
  10. (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.

Source

https://help.sap.com/saphelp_uiaddon10/helpdata/en/4c/9eb085d3884bdca468d7ec284be2e2/content.htm

Summary

As a summary, you can translate SAP Fiori transactional app tiles via SE63 -> TABL -> WDY_CONF_USERT2.

Fiori analytics app translation is done via KPI modeler by ADDING ‘langauge’ in the Definition, the Evaluation parameters and in visualization.

Leave a Reply

Your email address will not be published. Required fields are marked *