This document shall help you identify some fiori launchpad texts and give helps how to identify the underlying resources to identify a translation key.
Texts displayed in the Fiori Launchpad
Texts displayed in the FLP stem from different repositories. Thus distinguishing the texts to identify the underlying storage is the first task:
Let’s introduce some names:
Catalogs, Groups and Tiles
are part of the Business content and defined with the Fiori Launchpad Designer. (FLPD).
Corresponding texts can be found in the Fiori Launchpad designer.
There are three ways described below:
- Identifying from FLPD
- Identifying from PageSet Request of FLP
- Identifying using /UI2/FLC
Identifying from FLPD
one can use the FLPD to determine the technical key (e.g. Catalogname, groupname) containing the entry.
The following documentation describes how to obtain the translation key from the technical key. .
Identifying text from PageSet Request
If one does not have access to the Fiori Launchpad designer, the technical key can be determined by inspecting the Pageset request as described below for a group title:
presume we have to identify the technical group name of the group tile “Operação diária”:
Opening the developer tools (F12), refresh page(Press F5), on the network tab filter for “Pageset”.
Double click on the pageset request to open it in it’s own tab.
then search in this content for the text:
In the vincinity you will find the technical group name:
Given the technical key, use
to determine the technical translation key.
Note: The actual response of the pageset request is compact. You may use an extension like JSONView to format the response. Alternatively you can copy it to a text editor of your choice and format.
Identifying Texts using /UI2/FLC or /UI2/FLT
The Fiori Launchpad check tool allows to identify the texts of the Fiori Launchpad.
See below in the Appendix.
Application Title (UI5)
Identify the App by looking for the respective Component-preload.js request occuring when starting the app the first time. The following blog gives you additional hints http://scn.sap.com/docs/DOC-74096
The application path typically correspoind to the bsp repository name
The frontend application texts and typically exposed via an i18n properties files
In newer releases ( UI5 1.38+ ), the application title itself may also be part of the manifest.json request if retrieved from the lrep. The origin of this text is typically still an i18n file in the bsp repository.
This file can be located in the BSP repository (for Applications) or Mime repository (for ui5 resources /SAP/PUBLIC/BC/UI5/LIBRARIES/VER/1.4x/ …)
Details on the UI5 translation process can be found here:
Application title, WebGUI
In the catalog, select Target Mappings, the proper line ( alternatively you can search in the top right search field for the technical target mapping id.
Then click “configure”.
This article focuses on Fiori Launchpad content texts.
Texts displayed within application screens depend on the applciation technology.
- WDA /Personas
- Webgui /Personas
- UI5 Applications
Backend UI Technologies (WDA, WebGui, Personas)
WDA and WebGUI texts are maintained on the application backend (Suite system, not the ABAP FES) running the application.
(If personas is used, additional texts may be stored in the Personas repository).
In e.g. an(* en_US.properties) file as described above.
Some texts like error messages or application data are retrieved from the backend via OData calls and thus part of the Suite system.
If in doubt, analyze the content of the network trace to determine the origin of the actual text.
Appendix: Using /UI2/FLC (/UI2/FLP_CONTCHECK) or /UI2/FLT to identify translation keys for FLP(D) texts
Texts of Catalogs, Groups, Tiles and Targetmappings are stored in the WebDynpro Repository.
With /UI2/FLC texts can be identified and the corresponding text keys determined:
Run the transaction /UI2/FLC (identical to /UI2/FLP_CONTCHECK), with “With Text ID” checked on the appropriate layer.
In newer releases, you can run /UI2/FLT which puts all texts in a single column.
Pick an appropriate ALV Layout displaying the TextID Columns ( 2SAP_TRANS)
Identify the respective catalog or group,
The m:2 column indicates the catalog title is nr 2 in the Main WD Config Key entits.
For tile titles, the Property WD Config Key has to be used:
Clicking on the “Catalog Title” columns takes you to a screen list
all (title) texts relevant to this Catalog (Catalog title texts, Tile title, and TM Title texts)
Group and Catalog Titles are stored in the MAIN WD CONFIG KEY. (orange)
Effective Tile and Target Mappings are stored in the Property WD CONFIG KEY! (green)
/UI2/FLT This transaction extends /UI2/FLC and allows selection by text and drilldown into the display for effective texts. It may not be present in older releases.
It allows drilldown from a text to the corresponding definition in case of references (e.g. from a group tile to a catalog or from a reference tile/tm to the actual definition).
Subsequently it allows to drilldown into all relevant texts for a catalog, highlighting the text under investigation.
Note that this catalog exists on both CUST and CONF layer,
with some Tiles/TMs only existing on CUST layer or beeing different on CUST layer.
Note that the Usage ID (Tile or TM ID is unique to a layer!).
But MAIN WD Config Key and Property WD Config Key is the same between the two layers.
Texts from CUSTOMIZNG are stored in table WDY_CONF_USERT2 (!)
Texts from CONFIGURAITON are stored in table WDY_CONFIG_COMPT (!)
Beware, as shown below, Tile and Target Mapping tests are erroneously also redundantly stored in the MAIN WD CONFIG KEY, translating those has no effects.
For details, please refer to https://help.sap.com/doc/saphelp_nw751abap/7.51.0/en-US/d6/c587a7c973479a8bcb7024406fae8e/frameset.htm
Another great blog with less technical details: