ABAP Texts Translation with SAP Translation Hub

SAP is being used all over the world and in almost all the languages and that brings an important aspect of Translation of Texts to all the required languages. We have been doing so in ABAP using transaction SE63 by maintaining translations to all required languages manually.

To accelerate and automate the process, SAP has launched SAP Translation Hub and Document Translation services.

Core features of SAP Translation Hub

• SAP Translation text repository
• SAP Machine Translations
• Possibility to integrate Own language Translations
• Over 40 languages supported
• Integration with SAP and non SAP systems

SAP Translation Hub offers following solution capabilities:

• User Interface Translations ( Using Translation Hub service)
• Document Translation ( Using Document Translation Service)

Apart from UI-Based workflows for translation, there are APIs available for Translation of short texts, Document translation etc. and more details can be checked on SAP API HUB

Check this for step by step process on how to Setup of Translation Hub Service on BTP.

Check  this for step by step process on how to set up Document Translation Service on BTP

Check this for how to translate document using Document Translation service

Check this for  how to translate SAP Fiori Apps using Translation Hub service

In ABAP also, we create text for for all the object types that we create, be it Data Elements, Domains, Selection Text, Forms etc. and we need to maintain translations for all those text in required languages in SE63.

SAP Translation Hub can be integrated with Backend on-premise systems to translate the text in a faster way. There are two ways to use Translation Hub for ABAP translations:

• Translate ABAP short texts via the SAP Translation Hub workflow

• Translate ABAP short texts with Report RS_LXE_MLTR_GET_TEXTS_FOR_OL

In this Blog, we are going to see how we can do translations using Translation Hub Workflow

Prerequisite

Translation Hub service is already enabled and Translation hub Workflow UI is accessible

Setting up Cloud Connector.

Cloud connector need to be set up to connect to the backend system  where we want to do translations and expose the LXE* Function modules to be used by translation hub to access the objects text.

Create a Destination in BTP Cockpit 

Once the cloud connector is connect and backend system is available, we need to create an RFC destination in Clod cockpit with desired authentication.

Create an ABAP Object List in Backend System.

Now we need to create a list of objects for which we want to translate the short texts. Follow the steps below :

• Navigate to transaction “LXE_MASTER” and click on “Object Lists” under Evaluations Tab

• Click on create new object list and give any name and save.

• There are multiple options to select the objects in the list like via collections, transports, Transportable objects etc. Lets add individual object

• Enter the Object details. In this case, I have select a program to translate the text elements for. Click Save

• Next, select the object list created and click on Schedule and select the server on which job need to be scheduled.

• We can see the Job status marked with “X” when completed. Now our object list is ready to be translated in Translation Hub

Create ABAP Project in Translation Hub UI.

• Navigate to the Translation Hub Workflow UI and create an ABAP Project

• Enter the Project Name, Source and Target language . Selected the ABAP system we connected to earlier and select the Object list created in backend and we want to translate.
• We can enable Post translation editing, review and approval process before pushing translations to backend if needed.
• Click on “translate without send“

• Once Translation is finished, we will get the message and the status will be updated in status field.
• If translation is successful, we can see translation under “Translations” tab. Click on Translations Tab.

• We can see the translated text and can modify post translation is enabled.
• We can also see the Translation Provider. In this case it is MTR ( Machin Translation). there could be SAP Translations and Company Specific translation (cMLTR) also if maintained.
• For each translation, there is Quality index also shown , to give an idea on the confidence on translation.
• If all good, click on “Send to ABAP” to push translations to backend.

• In the backend , go to the object and check translations

• We can see all the translation are updated in backend successfully.

So, this way we can translate the object list into multiple languages using translation hub.

Using the second option , we can connect to translation hub via HTTP connection and can translate using Standard report “RS_LXE_MLTR_GET_TEXTS_FOR_OL” directly in backend without using the Workflow UI. Check part 2 for details on using Report method.

Keep Learning & Keep Sharing.