3632702 - Translation of the App tile of a Custom UI5 apps using Launchpad App Descriptor when using "Reuse text from app,” option

• The tile title defined in the Launchpad App Descriptor Item isn’t being localized to the portal’s language—it always displays in English.
  • The team tried populating the title in both our English and German system instances, but it appears this object isn’t language‑dependent.
• The team is using the ABAP Development Tools for Eclipse (ADT) with a creation wizard, where a user can do the editing and the feature: Resuse text from app is available
• Let the following be an example in the ADT.
  
  -----Start here-------
  

  -----tile 1.png-----

  Launchpad App Descriptor Item: ZAPPNAME_UI5R

  application type = SAPUI5 Fiori Application

  SAPUI5 component ID = yfxui.fpAPPNAMEpublic

  Target Mapping ID = ZAPPNAME_UI5_TM
  Semantic Object = ZAPPNAME
  Action: Display

  Tile details:
  - Reuse Text from application  <--Option Clicked

  ------tile 2 png------
  ADT Explorer:

  FP_APPNAME_PUBLIC
  |__i18n_en.properties

  #XTIT: Application name
  appTitle = App Name

  #YDES:Application Description
  appDescription=Application Description
  #XTIT: Main view title
  title=App Name

  ----tile 3 png-----
  Explorer:

  FP_APPNAME_PUBLIC
  |__i18n_de.properties

  #XTIT: Application name
  appTitle = Translated App Name

  #YDES:Application Description
  appDescription=Translated-AppName
  #XTIT: Main view title
  title=Translated App-Name

SAP S/4HAN Public Cloud

• Definition 1:  In the SAP Fiori Launchpad, a Launchpad App Descriptor Item describes how an application is started. It consists mainly of a target mapping and one or more tiles. The descriptor item is assigned to a technical catalog, allowing applications to be called from within the SAP Fiori Launchpad. These descriptors define key parameters like the Semantic Object, Action, and the application type, whether it's a SAPUI5 Fiori Application or a URL-based application.
  • Reference 1: Working with Launchpad App Descriptor Items | SAP Help Portal 
• Definition 2:  The Launchpad App Descriptor can be created using the ABAP Development Tools for Eclipse (ADT) with a creation wizard, where you specify essential details such as the Project, Package, Application Type, and Transport Request [2]. A user can create and edit these items using a source-based editor, allowing customization of properties and values related to the descriptor item [3]. 
  • Reference 2: Creating Launchpad App Descriptor Items | SAP Help Portal 
  • Reference 3: Editing Launchpad App Descriptor Items | SAP Help Portal 
• Definition 3:  LADI - stands for "Launchpad App Descriptor Item." In the context of the SAP Fiori Launchpad, LADI refers to the configuration that determines how an application is launched. It includes parameters such as additional parameters and device types that are suitable for the application, and it ensures that applications are correctly mapped and launched with the intended parameters 
• Cause 1: Translation of Launchpad Text, such as titles of tiles, target mapping, groups or catalogs, require PAGE Cache synchronization and this may not happen automatically or instantaneously, it may need to be scheduled manually (if the user is on Private Cloud or on-premise).
  • See definition of /UI2/PAGE_CACHE_SYNC or transaction /UI2/SYNC_PBC (for Private Cloud or On-Premise).
  • The assumption here is that this important synchronization was missed
• Cause 2: The translated text (other language than English), were not written to the Launchpad App Descriptor Item during deployment
  • Potential Causes: The ZAPPNAME_UI5R Custom Tile may have been a derivation from a SAP Technical Catalog (Ex: SAP_TC_XXXX where XXXX is a Standard Catalog); however, the version of this Custom Tile has some manual modification.  
    • By using TADIR R3TR -> UIAD -> ZAPPNAME_UI5R (Where APPNAME is the name of the custom application), the "edit" flag is enabled
      • This means that there were some users allowed to edit this tile
      • The theory on why this may fail is as follows:
        • The Reuse Flag of ADT is Reuse Text from application is bypassed by the Fiori Launchpad App Manager and this field is hidden when the /UI2/PAGE_CACHE_SYNC is ran  (This means this is not supported as a workaround to reuse text from application to do the translation)
          • This feature will be disabled on future hot fixes as it may be adding to the misused of the capability of the system
          • This means if the team is using this feature is to disable it.
• Cause 3: From Cause 2 above, the issue is tied to that the Launchpad App Descriptor (LADI) was created manually before it was deployed
  • Deploying the SAPUI5 app into an existing Launchpad App Descriptor (LADI) have a few side-effects
    • The step above may have caused a corrupted LADI

• For Cause 1: Try to run the /UI2/PAGE_CACHE_SYNC in your on-premise or private cloud instance.  For public cloud, please create a case to component: XX-S4C-OPR-INC (Cloud Operations team to run it) and send the link in Cause 1.  Please provide the actual client number that needs this transaction to be ran.
• For Cause 2 and 3:  Due to the Launchpad App Descriptor was manually created, the suggestion is to delete the Launchpad App Descriptor (as it contains a few side-effects) and deploy again
  • Additional reasoning: Due to it was manually created, deploying did not transfer the information needed including all the required translated texts to this LADI.
  • Best Recommendation: Simply deploy the SAPUI5 app to the system because it will create a LADI automatically and this will be updated when the app is deployed again

Fiori LADI, Fiori Launchpad App Descriptor, ABAP Development Tools ADT, Reuse Text from Application, /UI2/PAGE_CACHE_SYNC, /UI2/SYNC_PBC, Translation, Fiori Tile Translation, Fiori Translation English , KBA , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , Problem