Skip to Content

In this blog you will learn how to translate texts adapted using in-app extensibility via Key User tools as explained in Fiori for S/4HANA – Adapting Terminology in SAP Fiori apps via Key User toolsThis technique works for static texts that can be changed using in-app extensibility via Key User tools.

Once you have adapted the texts of your SAP Fiori app you may need to translate them. Once again there are some different ways to do this depending on which approaches you are using:

  • Translating texts adapted using In-app Extensibility via Key User tools
  • Translating texts adapted using CDS Views and Metadata Extensions
  • Translating texts adapted using SAPUI5 Extension Project

And you can also use the SAP Cloud Platform service SAP Translation Hub.

IMPORTANT: You might need to use more than one approach depending on the app and which texts you need to translate.

Currently texts from Key User Extensibility, CDS Views and Metadata Extensions can all be translated in SAP GUI transaction SE63.

In this blog you will learn how to translate texts adapted using in-app extensibility via Key User tools as explained in Fiori for S/4HANA – Adapting Terminology in SAP Fiori apps via Key User tools

You can use transaction SE63 with transport request-based worklist approach for translating texts adapted with In-app Extensibility via Key User tools.  This approach will let you translate the Layered Repository texts that the Key User tools impact.

IMPORTANT: In the Extensibility roadmap, SAP is planning a more intuitive approach for translating texts via In-app Extensibility using Key User tools.  Current thinking is this might be as simple as  logging on as the same user in a different language and using UI Adaptation at runtime to change the texts in the new language.  Please note that the exact solution and timelines are yet to be confirmed.

Prerequisites

In your SAPUI5 ABAP Repository, SAP Note 2596076 must be applied to ensure Transaction SE63 can be used with objects with mixed upper/lowercase ids.

SAP Note 2596076 – Translation through worklists fails for files of the layered repository (LRep)

Translating the Texts

Logon to SAP GUI and go to transaction SE63.

Use the My Worklist option to Create a Worklist

On the Transport Request tab enter the transport request you used for translating your texts.

IMPORTANT: You need to enter the transport request or transport request task where the adapted values are actually assigned.  You can check the content of each level of your transport request in transaction SE01.

IMPORTANT: Make sure you check all the Deactivation options and then press Load Objects.

You should see a list of the objects to be translated.

Select each entry, translate the texts, and save your translations.

You should see the status change from red to yellow as you translate each entry.  Your changes are added to the transport request.

VERY IMPORTANT: To test that your changes are working, you must first  invalidate the cache via transaction /UI2/INVAL_CACHES.

Login to the Fiori Launchpad in your target language and you will see your new texts.

 

When you check with the same user in your original language you can see the changes hold true to each language.

This technique works for static texts that can be changed using in-app extensibility via Key User tools.

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki

Brought to you by the S/4HANA RIG

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply