USER GUIDE PUBLIC Document Version: SAP Translation Hub SAP SE or an SAP affiliate company. All rights reserved.

Transcription

1 USER GUIDE PUBLIC Document Version: SAP SE or an SAP affiliate company. All rights reserved. THE BEST RUN

2 Content What's New for Release Notes Getting Started Concepts Enterprise and Trial Accounts Glossary Language of UIs for Regions and Hosts Supported Languages Tutorials User Authentication and Authorization APIs Building Base URL of domains API languages API suggestions API texttypes API translate API Testing the APIs Integration of with SAP Hybris Cloud for Customer Translation Workflow Scenarios Access UI for Translation Workflow Scenarios ABAP Systems Git Repositories Files Managing Post-Editing and Review Steps Working with Translation Projects Translation Project FAQ Integrating Your Own Language Data Prerequisites for Integrating Your Own Language Data Access UIs for Integrating Your Own Language Data Upload Language Data Create a Company MLTR Prepare a Company MLTR Activate a Company MLTR P U B L I C Content

3 Translate Texts with a Company MLTR Update a Company MLTR Troubleshooting Content P U B L I C 3

4 1 enables you to translate texts by accessing records in a multilingual database and by using machine translation. To provide users of software in a global market with texts in their own language, translations are required. SAP Translation Hub enables you to satisfy the demands of a global market by translating short texts into more languages quickly and easily. By using, you can draw on SAP's translation experience across multiple products and languages to propose translations for short texts. You can use in the following ways: Consume APIs to propose texts in English or to translate texts that you create when you develop applications Translate texts as part of translation workflow scenarios that you manage on a user interface (UI) Related Information Getting Started [page 16] - FAQ APIs [page 30] Translation Workflow Scenarios [page 61] Videos about on YouTube 1.1 What's New for This page lists the release notes of for To see the release notes for the previous year, visit Release Notes [page 8]. 4 P U B L I C

5 10 August New Support for Additional Target Languages You can now use SAP Machine Translation to translate texts from German into the following target languages: Bulgarian Hungarian Italian Slovakian For more information, see Supported Languages [page 23]. New Support for SAP HANA Text Bundle Files You can now translate SAP HANA text bundle files (.hdbtextbundle) by using a translation project for files. For more information, see Files [page 101]. 18 May New Support for Additional Git Repositories All customers with all account types can translate.properties files that are stored in a Git repository hosted on the Web or an on-premise Git repository hosted by your enterprise. It is no longer restricted to customers with an enterprise account that take part in the early adopter program. For more information, see Git Repository Hosted on the Web [page 95] and Git Repository Hosted By Your Enterprise [page 87]. New Storage of Git Credentials in You no longer need a destination to save your Git credentials; it is now possible to save the credentials directly in SAP Translation Hub. For all three Git scenarios, you can store the credentials when you create a translation project or when you start the translation process for a given translation project. For more information, see Git Repositories [page 77]. P U B L I C 5

6 New Support for Additional Target Languages You can now use SAP Machine Translation to translate texts from German into the following target languages: Chinese Croatian Czech French Polish Romanian Russian Serbian (Latin) Slovenian Spanish For more information, see Supported Languages [page 23]. New Support for Android XML Files You can now translate Android XML files by uploading files using a translation project for files. For more information, see Files [page 101]. New Statistics in Translation Projects You can now view the following details: Total number of translations per language in the translation project header Number of translations in a given lifecycle status, such as In Review, on the Translations tab New buttons enable you to visualize the sequence of lifecycles statuses and to filter the translations by a given lifecycle status. For more information, see Working with Translation Projects [page 111]. Change Translation Workflow Scenario for ABAP systems We have improved the handling of large object lists that you create in on-premise ABAP systems. For more information about the translation workflow scenario for ABAP systems, see ABAP Systems [page 62]. 6 P U B L I C

7 Change Documentation The documentation for now contains the following: A more detailed explanation of the domain concept (see Domains [page 17]) Additional examples for the translate API (see translate API: More Code Examples [page 52]) 2 March Change Neural Machine Translation (NMT) SAP Machine Translation (SAP MT) now uses NMT for all translations involving English as the source or target language. Note, quality index scores are available for selected languages only. For more information, see Supported Languages [page 23], and Quality Index [page 19]. Change Quality Index for Dutch Translations Quality index scores are now available for translations from English into Dutch. For more information, see Quality Index [page 19]. New Source Languages other than English Trial account users can now use languages other than English as the source language for translations. Note, not all combinations of source and target languages return translations, as this is dependent on the translation provider. For more information, see Supported Languages [page 23]. Change Translation Volumes for Trial Accounts Translation volumes for trial accounts are now limited to 500,000 characters. For more information, see Enterprise and Trial Accounts [page 20]. New Enhanced Integration with SAP Cloud Platform Web IDE For new users of coming from SAP Web IDE, destinations are now configured automatically. For more information, see Use in SAP Web IDE Full-Stack. P U B L I C 7

8 Archived Release Notes Release Notes [page 8] Release Notes The following information outlines key features and change for in For details of features available in the latest release, see What's New for [page 4]. 20 December Change Source Languages other than English You can now translate texts from any of our supported languages into your target languages. This applies to all translation workflow scenarios and to your own language data. Note, machine translation (MT) support is not yet available for all languages. For more information, see Supported Languages [page 23]. Change Language of the User Interface for Enhanced user settings make it easier to select the UI language for. You can choose the required language in the settings menu; you access this by choosing the cog icon in the top right of the screen. For more information, see Language of UIs for [page 22]. Change Integrate Your Own Git Repository It is now possible to integrate your own Git repository, hosted either on the Web or on premise. The integration of non-sap Cloud Platform Git repositories is not available for trial accounts, and can only be activated for enterprise accounts in our early adopter program. If you are interested in activating this feature, mail us at translationhub@sap.com or contact your Account Executive. 8 P U B L I C

9 Change Meaningful Project Names for Translation Projects You can specify meaningful project names for all translation projects. The Project Name field is now fully independent of Application Name and is available for all translation projects, including those using Git repositories. For more information, see Create Translation Projects for Git Repository on SAP Cloud Platform [page 80]. Change Connect to Multiple ABAP Systems You can now connect multiple ABAP systems to and choose which of the connected ABAP systems you want to use during the translation process. A new field on the UI for ABAP translation projects enables you to choose the required ABAP system. To connect multiple ABAP systems, you create one RFC connection for each ABAP system on subaccount level in SAP Cloud Platform Cockpit. The changes are backwards compatible, so any ABAP systems that you configured using the previous pattern on subscription level will continue to work. For more information, see Create Translation Projects for ABAP Short Texts Using an RFC [page 72] and Prerequisites for Translating ABAP Short Texts Using an RFC [page 63]. Change Company Data Integration: Integrating Your Own Language Data You can now choose from multiple company MLTRs for your own language data You can base company MLTRs on XLIFF files or on object lists in your ABAP systems You can activate multiple company MLTRs and select the company MLTR that you want to use in a translation project or in the translate API For more information, see Integrating Your Own Language Data [page 113] and translate API [page 47]. Change translate API You can translate texts with reference to a company MLTR. To do this, you use a new parameter (companymltrid) in the request payload. For more information, see translate API [page 47]. P U B L I C 9

10 New Unicode Escape Sequences in Downloaded Translation Files You can now choose to show machine-readable formats for translation files. The downloaded translations file then contains Unicode escape sequences for non-ascii characters ( \uxxxx). This is only required when your translations involve Java properties files which use ISO encoding, and you need to interpret the content. To create translation files which contain ASCII escape sequences, choose the <Escape Non-ASCII chars> option when creating your translation file. For more information, see Create Translation Projects for Git Repository on SAP Cloud Platform [page 80] and Create Translation Projects for Files [page 103]. Change Enhanced Neural Machine Translation (MT) Additional Neural MT engines are available to translate German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian and Chinese into English, and vice versa. 26 October Change UI Improvements for Translation Projects You can now see the following metadata about the texts on the Translations tab in translation projects: Context information about each text in the form of comments that developers enter in their development environment The text type, such as XFLD for field labels The maximum number of characters that each translated text can have For more information, see Working with Translation Projects [page 111]. Change Support for ios XLIFF Files You can translate ios XLIFF files with the.xliff extension when you use the translation workflow scenario for files. For more information, see Create Translation Projects for Files [page 103]. 10 P U B L I C

11 Change Integration of Your Own Language Data When you upload XLIFF files that contain your own language data to, there are more detailed checks on the structure of the XLIFF files. The resulting UI messages have been improved to make it easier to pinpoint the issues in XLIFF files. For more information, see Integrating Your Own Language Data [page 113]. 3 August New Customer Language Data To get more accurate translations in your specific industries and use cases, you can integrate your own language data in the translation processes that supports. For more information, see Integrating Your Own Language Data [page 113]. Change translate API You can translate texts from languages other than English. To do this, you use a new parameter (sourcelanguage) in the request payload. For more information, see the following: Supported Languages [page 23] translate API [page 47] Change Quality Index If uses SAP Machine Translation as the translation provider, you can now see a quality rating for translations into Chinese, Italian, and Japanese. This feature applies to translations that you get from the translate API and to the translation workflow scenarios. For more information, see the following: translate API [page 47] Translation Workflow Scenarios [page 61] Quality Index [page 19] The calculation of the quality index for the existing languages has been improved, too. P U B L I C 11

12 Change languages API The response now contains ISO codes compliant with the Best Current Practice (BCP) 47 for the languages that SAP Translation Hub supports. For more information, see languages API [page 36]. New Notifications You can display notifications that the team publishes on the UI for translation projects. New Language of UIs translates : we used to translate the English UIs into the following languages: Chinese, French, German, Japanese, Russian, Portuguese, and Spanish. 8 June New Parallel Processing of Translation Projects When you translate texts in a translation project, you can now work on other translation projects at the same time. This feature comprises the following points: On the main project screen and in the project list on the left, there's a progress bar for each translation project On the main project screen, you see details of the processing status and which user last started the translation workflow process New Selection of Properties File in Translation Projects When you create a translation project to translate properties files stored in the Git repository on SAP Cloud Platform, you no longer have to enter the path to the properties file manually. You can now select the required properties file from a dropdown. For more information, see Create Translation Projects for Git Repository on SAP Cloud Platform [page 80]. 12 P U B L I C

13 New General UI Improvements The filter and sort buttons on the Translations tab in translation projects are now directly visible on the UI, rather than being accessed from an additional button. The buttons for translating the ABAP and Git repository translation projects now more accurately reflect the process steps and terminology for the individual translation workflow scenarios. For more information, see Create Translation Projects for ABAP Short Texts Using an RFC [page 72] and Create Translation Projects for Git Repository on SAP Cloud Platform [page 80]. Change Translation Quality for MLTR Translations We've improved the algorithms that uses to get translations from the multilingual text repository (MLTR), which means translations are more accurate. More accurate translations mean that less effort is required for post-editing. Change Quality Index If uses SAP Machine Translation as the translation provider, you can now see a quality rating for translations into the following languages: French, German, Russian, Spanish, and Portuguese. This feature applies both to translations that you get from the translate API and to the translations that you get when you create a translation project. For more information, see the following: translate API [page 47] Translation Workflow Scenarios [page 61] Quality Index [page 19] Change suggestions API By using the new maxlength parameter, you can search for texts up to a specific number of characters. If you use the suggestions API in conjunction with ABAP systems, you can now use the texttype parameter to specify ABAP-specific object types, such as DTEL for data elements. You can now use domain groups as well as individual domains in the suggestions API. For more information, see suggestions API [page 37]. New Support for XLIFF Files for SAP Smart Business Services You can now use to translate XLIFF files for SAP Smart Business services by uploading files using a translation project for files. For more information, see Create Translation Projects for Files [page 103]. P U B L I C 13

14 13 April Change Translation Project We ve consolidated the list of domains that you choose from when you create a translation project. The previous list of domains has been replaced by a list of 7 domain groups. You can now check and adjust the translations that provides by using different lifecycle statuses to manage the post-editing and review steps for each translation in a translation project. For more information, see Managing Post-Editing and Review Steps [page 106]. The translate API now contains the quality index, an estimate of the translation quality, in the response. For more information, see translate API [page 47]. Change translate API The structure of the request payload has changed as follows: The request no longer contains the bundles level; the units key is now on the root level. There are two new keys on the root level: enablemt enabletranslationqualityestimation The structure of the response has been updated to reflect the changes to the structure of the request payload. Furthermore, the domain key in the response has moved from the root level to the units key. For more information, see translate API [page 47]. Change Quality Index You can now decide whether you want to calculate a quality index for translations into German that the SAP Machine Translation solution provides. This feature applies both to translations that you get from the translate API and to the translations that you get when you create a translation project. For more information, see the following: Translation Workflow Scenarios [page 61] (then choose the translation project that you are interested in) translate API [page 47] Quality Index [page 19] New Support for ios XLIFF Files You can now use to translate ios XLIFF files by uploading files using a translation project for files. For more information, see Create Translation Projects for Files [page 103]. 14 P U B L I C

15 Change Translation Projects for ABAP Short Texts When you search for an object list in an ABAP system, you can now search for the ID or description of the object list. For more information, see Create Translation Projects for ABAP Short Texts Using an RFC [page 72]. The Translations tab now shows the object name and object type from the ABAP system, as well as the maximum length for each field, as defined in the ABAP system. For more information, see Translate ABAP Short Texts Using an RFC [page 74]. Change domains API You can use a new parameter, onlygroups, to display the new domain groups, which comprise the existing translation domains. For more information, see domains API [page 34]. New SAP API Business Hub To try out the API and read the API reference information, you can call the content directly from the service description in the SAP Cloud Platform cockpit. Change Documentation The documentation now contains the following: A glossary to explain the concepts used in. For more information, see Glossary [page 21]. An overview of the SAP Cloud Platform landscapes on which is available. For more information, see Regions and Hosts [page 23]. 17 February Change translate API The translate API now contains the quality index, an estimate of the translation quality, in the response. For more information, see translate API [page 47]. Change ABAP Translation Process When you translate short texts from ABAP systems, now considers the maximum length that is defined for the texts of ABAP objects. For more information, see Translate ABAP Short Texts Using an RFC [page 74]. P U B L I C 15

16 1.2 Getting Started is an SAP Cloud Platform service that is available in the Neo environment. At the center of are the following translation providers: A database of multilingual texts from SAP applications. The multilingual texts are stored in an SAP HANA database called the multilingual text repository (MLTR). SAP Machine Translation (SAP MT), which was trained on a large number of translations that were verified by SAP-certified language experts. (Optional) If you upload your own language data to, you can use your own repository of texts as a first-choice translation provider. This repository is called a company MLTR. You can translate texts using a set of integrated workflow scenarios on a dedicated UI in. You can also translate texts and get suggestions for source texts during the software development phase by consuming a set of APIs. The following figure shows an overview of : Related Information Environments Glossary [page 21] Integrating Your Own Language Data [page 113] APIs [page 30] Translation Workflow Scenarios [page 61] Using Services in the Neo Environment Videos about on YouTube 16 P U B L I C

17 1.2.1 Concepts This topic describes the concepts that are used in Domains To cater for situations in which a source text must be translated differently depending on the business context, uses a concept called domains. Even if you don't use domains or a similar concept in your development environment, you must specify a domain when you create translation projects as part of the translation workflow scenarios in SAP Translation Hub. Background Information In certain business contexts, industries, or applications, a given source text might need to be translated in a specific way. To determine which translation to use in a given context, some contextual information about the text is required. gets basic context information about texts by using a domain that you specify in a translation project or in the translate API. The texts in the SAP multilingual text repository (SAP MLTR) are assigned two-character domains from their origins in SAP's translation and terminology processes. Example One of the English source texts that you want to translate is application. If there's no information about the business context in which the text is used, the translations that you get might not work in the specific context. If the text is used in a human resources (HR) context, it is likely to mean job application. If the text is used in a technology component, however, it is likely to mean software application. If you provide information about the context in the form of a domain, you improve the chance of getting the right translation. Domains and Domain Groups To make it easier to choose a domain in, the two-character domains are consolidated in a list of domain groups. P U B L I C 17

18 The following domain groups are available: Name of Domain Group ID of Domain Group Examples of Business Context or Applications Analytics 06 Data analysis and business intelligence. Financials 05 Financial accounting, controlling, and finance management. General 08 The remaining application areas. Industries 09 SAP industry solutions, such as automotive, aerospace and defense, and insurance. Logistics 03 Logistics execution, materials management, and plant maintenance. People Management 04 Human capital management (HCM), learning solutions. Sales 02 Sales and distribution and customer relationship management (CRM). Technology 07 SAP technology components, such as SAP NetWeaver. Tip To see a complete list of domains, see domains API. Use in When looks for translations in the SAP MLTR, it uses the domain assignment to look for the most accurate translation in a given business context. In, you use domains and domain groups as follows: In the translation workflow scenarios, you choose a domain group. In the translate API, you can specify an individual, two-character domain or a domain group. Related Information domains API [page 34] 18 P U B L I C

19 Quality Index To estimate the quality of translations, uses a quality rating called the quality index. The higher the number on a scale of 0-100, the better the quality. Background Information calculates the quality index for translations that are provided by the multilingual text repository (MLTR) and SAP Machine Translation (SAP MT). If you do not use to translate some or all of the texts in a translation project, does not calculate a quality index for these texts. This situation applies when you import existing translations into a translation project, such as translations from a.properties file in the Git repository of SAP Cloud Platform or from an ABAP system. Depending on the translation provider, uses different methods to calculate the quality index. Translation Provider: Company Multilingual Text Repository If your company multilingual text repository (company MLTR) provides translations, the quality index is 100. If a translation in the company MLTR is too long for a given field label, truncates the text and sets the quality index to 1. Translation Provider: SAP Multilingual Text Repository If the SAP multilingual text repository (SAP MLTR) provides translations, the quality index is based on the following: Quality assessments When language specialists save the translations that are stored in the SAP MLTR, they assess the quality of translations by assigning a quality rating to each translation. Occurrences analyzes the number of instances in which the combination of a source text and a particular translation occurs in the SAP MLTR. The more often a given combination of source text and translation occurs, the more confident we are that the translation is good. P U B L I C 19

20 Translation Provider: SAP Machine Translation If SAP Machine Translation solution provides translations, the quality index is based on the results of a machine learning technique called quality estimation (QE). The results of QE enable you to see at a glance which of the translations require the most or least effort to review. QE currently provides a quality rating for translations from English into the following languages: Name of Language Chinese Dutch French German Italian Japanese Portuguese Russian Spanish ID of Language zh nl fr de it ja pt ru es Related Information Glossary [page 21] Enterprise and Trial Accounts The availability of is determined by the type of global account that you use. Restriction Trial accounts enable you to test and evaluate key features. You should not use SAP Cloud Platform trial account features productively, as any productive use of these features is at the customer's own risk, and SAP shall not be liable for errors or damages caused by their use. Details Enterprise Trial Purpose Used for productive purposes. Used for evaluation or testing purposes only. 20 P U B L I C

21 Details Enterprise Trial Translation volume Translation volumes are agreed in your enterprise agreement. Allows up to 500,000 characters to be translated; when this limit is exceeded, further translations are not possible. In, characters are used to measure translation volumes. Chararacters include spaces and multibyte characters. Multibyte characters are counted as one character. Related Information Feature Scope Description for What's New for [page 4] Glossary A glossary of definitions for concepts used in. Company multilingual text repository (company MLTR) Domain A storage location for your own specific language data that you upload to SAP Translation Hub. The repository runs on an SAP HANA database. Organizes translations according to a specific application or business context. The assignment of texts to a domain helps to ensure that texts can be translated correctly and consistently in applications that logically belong together from a terminology point of view. Providing the context information about the application or business context enables the same source text to be translated differently, depending on the business context or application in which the text is used. Example One of the English source texts that you want to translate is application. If there's no information about the business context in which the text is used, the translations that you get might not work in the specific context. If the text is used in a human resources (HR) context, it is likely to mean job application. If the text is used in a technology component, however, it is likely to mean software application. If you provide information about the context in the form of a domain, you improve the chance of getting the right translation. P U B L I C 21

22 SAP multilingual text repository (SAP MLTR) Quality estimation (QE) A storage location for translations provided by language specialists and official SAP terminology entries. The repository comprises a text in its original language and one or more translations for that text. The repository also includes the SAP translation domain and text type assigned to the text. The repository runs on an SAP HANA database. A machine learning technique that predicts the quality of nonhuman translations, for example, machine translations. QE is a supervised machine learning technique that learns from the following: Good and bad examples of machine translations The effort needed to make a machine translation comparable to a human translation The statistical model that results from the machine learning technique can predict the quality of new translations by calculating a score. This score enables you to see which of the translations require the most or least effort to review. SAP Machine Translation (SAP MT) Translation project Software that translates text into another language automatically. SAP MT was trained on a large number of translations that were verified by SAP-certified language experts. SAP MT is specialized to translate SAP-related content and differs from open source MT systems in terms of better domain adaptation and terminology coverage. An entity in that you use to manage translations in the translation workflow scenarios that supports. A translation project comprises metadata, such as the location of the texts that you want to translate and the required target languages Language of UIs for The UIs are available in multiple languages. The following list shows the available languages: Chinese English French German Japanese Portuguese Russian Spanish Specifying the Language of UIs To change the language of the UI for your translation projects, choose the required language in the settings menu; this you access by choosing the cog icon in the top right of the screen. In some browsers, such as Google Chrome and Mozilla Firefox, the language of the UI may be determined by your browser settings. In other browsers, such as Internet Explorer (prior to version 11), the 22 P U B L I C

23 language of the operating system determines the language of the UIs. From Internet Explorer 11, the language setting can be changed for using the settings menu Regions and Hosts This section shows in which SAP Cloud Platform regions is available. Neo Region Global Account Type Enterprise account (Operated by SAP) Australia (Sydney) Host ap1.hana.ondemand.com Europe (Rot) hana.ondemand.com eu1.hana.ondemand.com Europe (Amsterdam) eu3.hana.ondemand.com US East (Ashburn) us1.hana.ondemand.com US East (Sterling) us3.hana.ondemand.com Trial account US West (Chandler) Europe (Rot) - Trial us2.hana.ondemand.com hanatrial.ondemand.com Related Information Regions and Hosts on SAP Cloud Platform Supported Languages supports a number of different languages. The translations are provided by the SAP multilingual text repository (MLTR) or SAP Machine Translation (SAP MT). You can use all languages that supports as source and target languages. Depending on the translation provider that uses for a particular text, not all combinations of source and target languages return translations. For details, see the tables in the following sections. P U B L I C 23

24 Translation Provider: SAP Multilingual Text Repository If the SAP MLTR is the translation provider, you can use all languages in the following table as a source and a target language. To get the latest list of languages, call the languages API. For information about the base URL, see Building Base URL of. Language Name Arabic Bulgarian Catalan Chinese Chinese (Traditional) Croatian Czech Danish Dutch English (Great Britain) English Estonian Finnish French French (Canada) German Greek Hebrew Hindi Hungarian Indonesian Italian Japanese Kazakh Korean Latvian Lithuanian Malay Norwegian Persian - pilot language Language Code ar bg ca zh zf hr cs da nl 6n en et fi fr 3f de el he hi hu id it ja kk ko lv lt ms no fa 24 P U B L I C

25 Language Name Polish Portuguese Portuguese (Portugal) Romanian Russian Serbian Serbian (Latin) Slovak Slovenian Spanish (Colombia) Spanish Swedish Thai Turkish Ukrainian Vietnamese Language Code pl pt 1p ro ru sr sh sk sl 0s es sv th tr uk vi Translation Provider: SAP Machine Translation If SAP Machine Translation (SAP MT) is the translation provider, the following pairs of source and target languages are supported. Quality index scores are provided for selected languages. Source Language Name Source Language Code Target Language Name Target Language Code Chinese zh English en English en Arabic ar English en Bulgarian bg English en Catalan ca English en Chinese zh English en Chinese (Traditional) zf English en Croatian hr English en Czech cs English en Danish da English en Dutch nl English en Estonian et P U B L I C 25

26 Source Language Name Source Language Code Target Language Name Target Language Code English en Farsi - pilot language fa English en Finnish fi English en French fr English en German de English en Greek el English en Hebrew he English en Hindi hi English en Hungarian hu English en Italian it English en Japanese ja English en Kazakh kk English en Korean ko English en Latvian lv English en Lithuanian lt English en Malay ms English en Norwegian no English en Polish pl English en Portuguese pt English en Romanian ro English en Russian ru English en Serbian (Latin) sh English en Slovak sk English en Slovenian sl English en Spanish es English en Swedish sv English en Thai th English en Turkish tr English en Ukrainian uk English en Vietnamese vi French fr English en German de Bulgarian bg German de Chinese zh German de Croatian hr German de Czech cs 26 P U B L I C

27 Source Language Name Source Language Code Target Language Name Target Language Code German de English en German de French fr German de Hungarian hu German de Italian it German de Polish pl German de Romanian ro German de Russian ru German de Serbian (Latin) sh German de Slovakian sk German de Slovenian sl German de Spanish es Italian it English en Japanese ja English en Korean ko English en Portuguese pt English en Spanish es English en Arabic ar English en Bulgarian bg English en Catalan ca English en Czech cs English en Danish da English en Greek el English en Estonian et English en Farsi - pilot language fa English en Finnish fi English en Hebrew he English en Hindi hi English en Croatian hr English en Hungarian hu English en Kazakh kk English en Lithuanian lt English en Latvian lv English en Malay ms English en Dutch nl English en P U B L I C 27

28 Source Language Name Source Language Code Target Language Name Target Language Code Norwegian no English en Polish pl English en Romanian ro English en Russian ru English en Serbian (Latin) sh English en Slovak sk English en Slovenian sl English en Swedish sv English en Thai th English en Turkish tr English en Ukrainian uk English en Vietnamese vi English en Chinese (Traditional) zf English en Related Information languages API [page 36] Quality Index [page 19] Tutorials Follow a tutorial to get familiar with the features of. To learn about How to create an SAP Fiori app in SAP Web IDE and translate it using How to translate an ios app using How to set up Eclipse to develop a Java app and translate the app using See Create and translate an SAP Fiori app with SAP Translation Hub Translate an ios app Create and translate a Java app with Related Information Tutorial Navigator 28 P U B L I C

29 1.2.8 User Authentication and Authorization An authorization process controls access to. To be able to consume the APIs and features of, you set up authorizations for the users on SAP Cloud Platform who are to access. Prerequisites The users who need to access have account logon information in SAP Cloud Platform Identity Authentication service. If you have an S user that you use to log on to platforms like SAP Jam, you can use the same user ID to register for a trial account on SAP Cloud Platform. The resulting account name on SAP Cloud Platform is <s user>trial. Process When you enable in the SAP Cloud Platform service catalog, the system automatically assigns your SAP Cloud Platform user to the required role. No further assignments are required for your user. If you want to enable other users to use the service, assign the required users to the User role as follows: 1. Choose the tile in the SAP Cloud Platform cockpit. 2. Choose Configure Service. 3. In the pane on the left, choose Roles. 4. In the User section, choose Assign and enter the user ID of the required users, as shown in the following screenshot: P U B L I C 29

30 For role assignments to take effect, close all browser sessions and open a new session or log out from the cockpit and log on again. Related Information SAP Cloud Platform Identity Authentication Service 1.3 APIs comprises a set of APIs that applications can consume to translate texts using a multilingual text repository (MLTR) and machine translation. You can use the APIs to translate texts, for example, from an app that you develop or enhance, or through a translation tool that you create in an integrated development environment (IDE). This section explains how to consume the APIs on SAP Cloud Platform. 30 P U B L I C

31 The following APIs are available: domains languages suggestions texttypes translate Access You access the APIs through the HTTPS protocol. Standard functions of SAP Cloud Platform Identity Authentication service manage user authorizations for the APIs. When you consume the APIs, you use basic authentication (user and password). To be able to consume the APIs, work through the following items: 1. Have you got a license on SAP Cloud Platform? If you have, proceed to the next step. If you don't, no worries. It takes just a moment to request a free developer license at If you have an S user that you use to log on to platforms like SAP Jam, you can use the same user ID to register for a trial account on SAP Cloud Platform. The resulting account name on SAP Cloud Platform is <s user>trial. 2. If you've heard about before, maybe you've already enabled the service for your account? If you have, you're good to go. If you haven't, complete the next couple of steps: 1. In the SAP Cloud Platform cockpit, choose Services in the navigation tree. 2. Choose Enable. For more information about enabling services, see Using Services in the Neo Environment. You don't need to configure any destinations. 3. If several people need to access the APIs, assign the user IDs of those users. For more information about role assignments, see User Authentication and Authorization. URL of APIs To access the APIs, you need the base URL of plus the API name and API-specific parameters. For information about the base URL, see Building Base URL of. P U B L I C 31

32 Parameters To filter or modify the response, the APIs that don't have a body for the payload use query parameters that are located in the query part of the URL. Example <base URL>/v1/languages?search=<query_parameters> Content The APIs use JSON as the content of the HTTPS request or response. All of the API responses that contain JSON have the JSON content type application/json; charset=utf-8. Error Handling Error Codes Error 400 Bad Request Content-Length: Not Found Description This error occurs if not all of the required query parameters are specified or an invalid value type is sent in the request. This error occurs if the wrong URL is used to call an API. Content-Length: 0 Related Information SAP API Business Hub Building Base URL of [page 33] domains API [page 34] languages API [page 36] suggestions API [page 37] texttypes API [page 45] translate API [page 47] Testing the APIs [page 59] Troubleshooting [page 125] User Authentication and Authorization [page 29] Using Services in the Neo Environment 32 P U B L I C

33 1.3.1 Building Base URL of The base URL is the main part of the URL that you use to access the APIs. You use the base URL with additional parameters that are specific to the individual APIs. The following table summarizes the parts of the base URL: Global Account Base URL Sample Base URL Trial Enterprise <subaccount name>.hanatrial.ondemand.c om/translationhub/api subaccount name>- <subscription subaccount name>.<region host>/ translationhub/api translationhub/api om/translationhub/api Tip To get your base URL, open the service description for in the SAP Cloud Platform cockpit and choose Go To UI for Translation Workflow. Copy the URL from your browser's address bar, and replace ui/ at the end of the address with translationhub/api. For details about the name of the API and the query parameters that you add to the base URL, see the documentation for the individual APIs. Related Information domains API [page 34] languages API [page 36] suggestions API [page 37] texttypes API [page 45] translate API [page 47] Regions and Hosts SAP Cloud Platform Cockpit P U B L I C 33

34 1.3.2 domains API This API enables you to view the domains that are available in. Usage SAP product terminology and translations are organized by domains. Domains are used to determine the correct translation for a given text in a specific application or business context. Tip Are you new to the concept of domains in the context of translation with SAP software? For an explanation and some examples, check out Domains. The domains API returns a list of the domains and domain groups that are available in. You can combine the domains API with the translate API to more accurately reflect the subject area of your texts. Request Access URL HTTP method Authorization <base URL>/v1/domains GET Basic authentication (user and password for SAP Cloud Platform) Request Parameters To check whether a specific domain or domain group is available, you can add the following parameters to the URL: Parameter Description Type search Shows whether a particular domain is available in SAP Translation Hub. For example: <base URL>/v1/domains? search=<domain_name> You can enter all or part of the name of a domain or domain group, for example, account. Optional 34 P U B L I C

35 Parameter Description Type onlygroups Shows a list of the domain groups that supports. To list the domain groups, enter true as the value for this parameter. You can use the ID of a domain or a domain group to specify a particular subject area in the translate API. Optional Request Body Example <base URL>/v1/domains?search=financial Response The result is a JSON object that contains the following key-value pairs: Key Description Part of Response? id name The ID of a domain or a domain group, depending on whether you use the onlygroups parameter in the request. The short description of a domain or domain group, depending on whether you use the onlygroups parameter in the request. Always in response Always in response Response Body Example Sample Code "domains":[ } ] }, }, }, }, }, } "id":"fi", "name":"financial Accounting" "id":"fs", "name":"financial Services" "id":"fb", "name":"financials Basis" "id":"fn", "name":"financials" "id":"1f", "name":"business ByDesign Financial Accounting" "id":"fb", "name":"financials Basis" P U B L I C 35

36 Related Information Building Base URL of [page 33] Domains [page 17] languages API This API enables you to view the languages that supports. Usage Returns a list of the languages that are available as target languages in. Request Access URL HTTP method Authorization <base URL>/v1/languages GET Basic authentication (user and password for SAP Cloud Platform) Request Parameters To check whether a specific language is available, you can add the following parameter to the URL: Parameter Description Type search Determines whether a particular language is available in SAP Translation Hub. For example: <base URL>/v1/ languages?search=<language_name> You enter the name of a language, for example, Chinese, not the code for Chinese. Optional Request Body Example <base URL>/v1/languages?search=Bulgarian 36 P U B L I C

37 Response The result is a JSON object, and contains the following key-value pairs: Languages Key Description Part of Response? id The language code. Always in response name The name of the language. Always in response bcp-47-code The ISO code of the language, compliant with Best Current Practice (BCP) 47. Always in response Response Body Example Sample Code } "languages": [ "id": "bg", "name": "Bulgarian", "bcp-47-code": "bg" } ] Related Information Building Base URL of [page 33] Testing the APIs [page 59] suggestions API This API enables you to get suggestions for short texts during the development process. Usage Provides suggestions for short texts based on complete or partial texts and their translations. You can, for example, use the suggestions API to propose texts while you type in a development environment. The texts that the API proposes are already available in additional languages in the SAP multilingual text repository (SAP MLTR). P U B L I C 37

38 Request Access URL HTTP method Authorization <base URL>/v1/suggestions GET Basic authentication (user and password for SAP Cloud Platform) Request Parameters You can use the following parameters by adding them to the URL: If you want to use multiple parameters, prefix each parameter name with an ampersand (&). If you want to enter multiple parameter values for a given parameter, enter a comma between each parameter value. Parameter Description Type search Searches for a text in. For example: <base URL>/v1/suggestions?search=<text>. If you want to enter a text in a language other than English, enter the text in the required language here and specify the language in the searchlanguage parameter. You can enter a complete text or part of a text. Required searchlanguage language Determines the language of the text that you search for in. This parameter enables you to search for a text in any of the languages that supports. Specify the language using the language code, for example, de. Searches for a text that has translations in the specified language(s). For example, you can search for texts that have translations in German (de) and French (fr). Optional Optional domain B2) or logistics (03). texttype Searches for texts assigned to the specified text type(s). For example, you can search for terms that are assigned to the text type for field labels (XFLD). If you use the suggestions API with ABAP systems, you can specify a four-character object type, such as Searches for texts in the specified domain(s) or domain group(s). For example, you can search for terms that are assigned to the domain for Customer Relationship Management (DTEL for data elements, in this parameter. Optional 38 P U B L I C

39 Parameter Description Type maxlength Searches for texts up to the specified number of characters. For example, if a UI element can accommodate only 5 characters, you can search for texts that comprise 5 characters or fewer. If the suggestion API cannot find any texts that match the length criteria, the response is empty. Optional Request Body Example Searches for texts in the specified domain(s) or domain group(s).assume you want to search for entries that contain the English word User Settings. More specifically, you want instances of this text that are used in field labels (XFLD) within the CRM (B2) domain, and that have translations in French and German. To find such texts, enter the following: <base URL>/v1/suggestions?search=User Settings&texttype=XFLD&domain=B2&language=de,fr For examples that include other parameters, see suggestions API - More Code Examples. Response The response of the suggestions API has a JSON root object. The response contains the following key-value pairs: Parameter Description Part of Response? id value A key that uniquely identifies the text's entry in the database. The text that the suggestions API looks for in the SAP MLTR, based on the text that you enter in the search parameter in the request. If you want to search for cancel by entering part of that word, for example, canc, in the request, the value parameter in the response contains the full text, cancel. Always in response Always in response domainid The ID of the domain assigned to the translations of the text entered in the request. If you specify the ID of a domain group in the request, the response always contains the ID of an individual domain. Depends on request P U B L I C 39

40 Parameter Description Part of Response? domainname The name of the domain assigned to the translations of the text entered in the request. If you specify the ID of a domain group in the request, the response always contains the name of an individual domain. Depends on request texttypeid The ID of the text type assigned to the text entered in the request. If you use the suggestions API with ABAP systems and the API returns an object type instead of a text type, this parameter shows the four-character ID of the object type. Depends on request texttypename The name of the text type assigned to the text entered in the request. If you use the suggestions API with ABAP systems and the API returns an object type instead of a text type, this parameter shows the name of the object type. Depends on request Always in response availablelanguages availablefilteredlanguages englishvalue If you search for a text in English, the content of this parameter is the same as the value parameter. If you search for a text in a language other than English, this parameter contains the English translation of the text in the value parameter. The English translation of the text - in English - entered in the request. The total number of languages, including English, in which there are translations of the requested text in SAP Translation Hub. If you use the language parameter in the request, this parameter shows the number of languages in that parameter in which translations of the text was found. For example, if you specify French (FR) and German (DE) in the language parameter of the request, but there are translations of the requested text only in French, the value of this key is 1. If there are translations in both French and German, the value of this key is 2. Always in response Depends on request 40 P U B L I C

41 Parameter Description Part of Response? textspace Indicates length specifications of the text entered in the request. textspace comprises multiple parameters see next table. This parameter is supported only for texts that you search for in English or German. This means the searchlanguage parameter is English or German, or you do not enter the searchlanguage parameter in the request. Depends on request textspace Parameter Description Part of Response? inputchars minrecchars minrecem The number of characters contained in the text entered in the request. The minimum recommended number of characters to set aside in the UI to accommodate a potential length increase in translations. The minimum recommended length to set aside in the UI to accommodate a potential length increase in translations. It is measured in em. Always in response Always in response Always in response Response Body Example Sample Code "suggestions": [ "id": , "value": "User Settings", "domainid": "B2", "domainname": "Customer Relationship Management", "texttypeid": "XFLD", "texttypename": "Label", "englishvalue": "User Settings", "availablelanguages": 30, "availablefilteredlanguages": "2", "textspace": "inputchars": 13, "minrecem": 17, "minrecchars": 26 } }, "id": , "value": "User Session Settings", "domainid": "B2", "domainname": "Customer Relationship Management", "texttypeid": "XFLD", "texttypename": "Label", "englishvalue": "User Session Settings", "availablelanguages": 30, "availablefilteredlanguages": "2", "textspace": "inputchars": 21, "minrecem": 21, P U B L I C 41

42 } ] } } "minrecchars": 32 Related Information suggestions API: More Code Examples [page 42] Supported Languages [page 23] suggestions API: More Code Examples To better understand the individual parameters that you can use with the suggestions API, see the examples in this document. Searching for Texts in a Language Other Than English Request Body Example Assume you want to search for entries that contain the German word Auftrag anlegen and have the following attributes: Used in button texts (XBUT) Assigned to the Basis (BC) domain Have translations in Polish (pl) and Russian (ru) To find such texts, use the following request: <base URL> /v1/suggestions?search=auftrag anlegen&texttype=xbut&domain=bc&language=pl,ru&searchlanguage=de Response Body Example Sample Code "suggestions" : [ "id": , "value": "Ad-hoc-Auftrag anlegen", "domainid": "BC", "domainname": "Basis", "texttypeid": "XBUT", "texttypename": "Button text", "englishvalue": "Create Ad-Hoc Request", "availablelanguages": 36, "availablefilteredlanguages": 2, "textspace": 42 P U B L I C

43 ] } } } "inputchars": 22, "minrecem": 22, "minrecchars": 33 Searching for Texts up to a Specific Length Request Body Example Assume you want to search for entries that contain the French word envoyer and have the following attributes: Used in button texts (XBUT) Assigned to the Logistics - General (LO) domain Have translations in simplified Chinese (zh) and Japanese (ja) Contain no more than 10 characters To find such texts, use the following request: <base URL> /v1/suggestions? search=envoyer&texttype=xbut&domain=lo&language=zh,ja&searchlanguage=fr&maxlength=1 0 Response Body Example } "suggestions" : [ "id": , "value": "Envoyer", "domainid": "LO", "domainname": "Logistics - General", "texttypeid": "XBUT", "texttypename": "Button text", "englishvalue": "Submit", "availablelanguages": 39, "availablefilteredlanguages": 2 } ] To see the impact of using the maxlength parameter, try changing the value to 30, for example. P U B L I C 43

44 Searching for Texts in an ABAP Object Type Request Body Example Assume you want to search for entries that contain the English word summary and have the following attributes: Used in data element texts (DTEL) in ABAP systems Assigned to the Basis (BC) domain Have translations in Italian (it) and Spanish (es) To find such texts, use the following request: <base URL> /v1/suggestions?search=summary&texttype=dtel&domain=lo&language=it,es Response Body Example } } "suggestions": [ "id": 0, "value": "Summary", "domainid": "BC", "domainname": "Basis", "texttypeid": "DTEL", "texttypename": "Data Elements", "englishvalue": "Summary", "availablelanguages": 39, "availablefilteredlanguages": 2, "textspace": "inputchars": 7, "minrecem": 12, "minrecchars": 18 } }, "id": 0, "value": "Feed Summary", "domainid": "BC", "domainname": "Basis", "texttypeid": "DTEL", "texttypename": "Data Elements", "englishvalue": "Feed Summary", "availablelanguages": 39, "availablefilteredlanguages": 2, "textspace": "inputchars": 12, "minrecem": 16, "minrecchars": 24 } } ] Searching for Texts in a Domain Group Request Body Example Assume you want to search for entries that contain the English word print and have the following attributes: 44 P U B L I C

45 Used in message long texts (YMSG) Assigned to the Technology (07) domain group To find such texts, use the following request: <base URL> /v1/suggestions?search=print&texttype=ymsg&domain=07 Response Body Example } "suggestions": [ "id": 0, "value": "Close print preview mode", "domainid": "MD", "domainname": "Master Data Management", "texttypeid": "YMSG", "texttypename": "Message text (long)", "englishvalue": "Close print preview mode", "availablelanguages": 22, "textspace": "inputchars": 24, "minrecem": 24, "minrecchars": 36 } }, "id": 0, "value": "Could not set image print size", "domainid": "MD", "domainname": "Master Data Management", "texttypeid": "YMSG", "texttypename": "Message text (long)", "englishvalue": "Could not set image print size", "availablelanguages": 22, "textspace": "inputchars": 30, "minrecem": 30, "minrecchars": 45 } } ] texttypes API This API enables you to access the text types that are available in. Usage Short texts, for example, those used on user interfaces (UIs), in SAP products are characterized by various text types. The type of a specific text is determined by the UI element that it describes. For example, button texts are described by the text type XBUT. The texttypes API returns a list of the text types that are available in. You can combine the texttypes API with the suggestions API to narrow down the results of the suggestions API. P U B L I C 45

46 Request Access URL HTTP method Authorization <base URL>/v1/texttypes GET Basic authentication (user and password for SAP Cloud Platform) Request Parameters To check whether a specific text type is available, you can add the following parameter to the URL: Parameter Description Type search Shows whether a particular text type is available in SAP Translation Hub. For example: <base URL>/v1/ texttypes?search=<text type name> You can enter all or part of the name of the text type, for example, message. Optional Request Body Example <base URL>/v1/texttypes?search=message Response The result is a JSON object, and contains the following key-value pairs: Key Description Part of Response? id The ID of a text type. Always in response name The short description of a text type. Always in response Response Body Example Sample Code "texttypes": [ "id": "MSAG", "name": "Message Classes" }, "id": "XMSG", "name": "Message text" } ] 46 P U B L I C

47 } Related Information Building Base URL of [page 33] translate API This API enables you to translate short texts into the languages that supports. Usage Provides translations of short texts based on multiple translation providers. The API looks for suitable translations from translation providers in the following sequence: 1. Company multilingual text repository (company MLTR) - if available; see Integrating Your Own Language Data [page 113] 2. SAP multilingual text repository (SAP MLTR) 3. SAP Machine Translation (SAP MT) Request Access URL HTTP method Authorization <base URL>/v1/translate POST Basic authentication (user and password for SAP Cloud Platform) Request Parameters The API requires a JSON request payload and the request content type: application/json; charset=utf-8. If you do not use this content type, the API call fails. The JSON request contains an array of units JSON objects. The following tables show the different key-value pairs in the JSON request: To better understand the keys of the JSON request shown in the following tables, see the sample code for the request body below the tables. P U B L I C 47

48 Root Key Description Type targetlanguages sourcelanguage The codes of the target languages in which you want the API to return translations of texts. To view the codes of the supported languages, call the languages API. If you do not specify any target languages, the API returns the texts in all available target languages. Enables you to specify a source language other than English. You can enter the code of any of the languages that SAP Translation Hub supports as a source language. If you do not use this parameter, the API assumes that the source language is English. To see which combinations of source and target languages are possible, see Supported Languages. Optional Optional enablemt enabletranslationqualityesti mation domain Determines whether translates texts using SAP Machine Translation (SAP MT) in addition to the multilingual text repository (MLTR). By default, SAP MT is active. If you want to deactivate it, enter false as the value of this parameter. Determines whether the response contains a quality index for selected target languages that are provided by the SAP machine translation solution. If you want to include the quality index for translations that are provided by SAP MT in selected languages, set the value of this parameter to true. For more information about the quality index and the languages for which a quality index is available, see Understanding the Quality Index. The ID of a translation domain (such as B2 for CRM) or the ID of a domain group (such as 02 for sales). If you do not specify a domain or domain group, the API searches for translations in all available domains. It is not possible to enter multiple domains. Optional Optional Optional companymltrid Enables you to specify a company MLTR as translation provider. Tip To get the ID of a company MLTR, see the address bar of the UI for company MLTRs. For more information, see Access UIs for Integrating Your Own Language Data. Optional units Describes a single text that you want to translate. The units key comprises multiple property keys - see the next table. Required 48 P U B L I C

49 Units Key Description Type texttype The ID of a text type, for example, XFLD for a field label. It is not possible to enter multiple text types. Optional key A key that helps you to uniquely identify a particular text and its subsequent translations in the units key. SAP Translation Hub stores this key with the text in the API request to make it easier to identify specific texts and their translations than by using the texts alone. For example, if you specify a key for each text in a properties file that you want to translate, you can use the key to identify the translations for each text in the target properties files. The key is stored only to make it easier to identify the text in the units key; it is not stored for future reference in the multilingual text repository. Optional value The text to be translated. To see the request payload required to translate multiple texts, see translate API: More Code Examples. Required searchdata A parameter that allows you to specify the translation of a UI text in one of the requested target languages. You use this parameter if you know that there are multiple possible translations for a given source text, and you want to restrict the results to a specific translation. Example Let's take the word Cancel. The German translation could be Abbrechen or Stornieren. If you know that the German translation in a given instance should be Abbrechen, you can specify Abbrechen so that the API returns the correct translation in German (and in other languages). This parameter has two properties that are required: language (the language code provided by the languages API) and value (the text in the target language). Optional Request Body Example Below is one piece of sample code that contains some of the possible keys in the payload. To see some more code examples that include other keys in the payload, see translate API - More Code Examples. P U B L I C 49

50 Sample Code } "targetlanguages": [ "de", "fr", "ru" ], "enabletranslationqualityestimation": true, "domain": "B2", "units": [ "texttype": "XFLD", "key": "LOGIN_USERNAME_FIELD", "value": "User Name" } ] Response The translation response is in JSON format. The response contains an array of units keys; each units key in the response corresponds to a units key in the request. If there is more than one units key, the sequence of these keys from the request is retained. The response contains the following key-value pairs: Root Key Description Part of Response? units Describes a single text that you want to translate and additional context information. The units key comprises multiple keys - see the next table. Always in response Each units key in the response corresponds to a units key in the request, and contains the following keys: Units Key Description Part of Response? texttype The ID of the text type, for example, XFLD. Depends on request domain For translations that are assigned a domain, this entry shows the ID of the translation domain that is assigned to the translation that the API provides, even if you specify a domain group in the request. Depends on request and availability of domain assignment key A key that uniquely identifies a text in the units key. The key is stored only to make it easier to identify the text in the units key; it is not stored for future reference in the multilingual text repository (MLTR). Depends on request value The text to be translated. Always in response translations Describes the translated text. The translations key comprises multiple keys - see the next table. Always in response 50 P U B L I C

51 For each target language that is specified in the targetlanguages key in the request, there is a set of translations keys in the response. If you specify a value for the searchdata key in the request, the translation is based on the text in the value parameter that you specify in the request. If a translation does not exist in one of the target languages specified in the request, the set of translations keys for that target language is not part of the response. If there are no translations of the text, the translations array is part of the response, but is empty. Translations Key Description Part of Response? language The code of the target language in which the text is translated. Depends on request value The translation of the text. Depends on request translationprovider qualityindex The source of the translated texts: 0 = SAP multilingual text repository (SAP MLTR) 1 = SAP Machine Translation (SAP MT) 5 = company MLTR The quality index helps you to judge the quality of translations. The higher the number on a scale from 0-100, the better the quality. For more information, see Quality Index. Always in response Depends on translation provider and request: If an MLTR is the translation provider, always in response If SAP MT is the translation provider, in response only if you set the value of enabletranslationquality Estimation in the request to true and only for selected languages. For more information, see the SAP machine translation section in Understanding the Quality Index. Response Body Example Sample Code "units": [ "texttype": "XFLD", "domain": "B2", "key": "LOGIN_USERNAME_FIELD", "value": "User Name", "translations": [ "language": "de", "value": "Benutzername", "translationprovider": 0, "qualityindex": 92 P U B L I C 51

52 } ] } ] }, }, } "language": "ru", "value": "Имя пользователя", "translationprovider": 0, "qualityindex": 92 "language": "fr", "value": "Nom de l'utilisateur", "translationprovider": 0, "qualityindex": 77 Related Information Access UIs for Integrating Your Own Language Data [page 121] Building Base URL of [page 33] Integrating Your Own Language Data [page 113] languages API [page 36] Supported Languages [page 23] Testing the APIs [page 59] translate API: More Code Examples [page 52] Quality Index [page 19] translate API: More Code Examples To better understand the individual parameters that you can use with the translate API, see the examples in this document. Translating a Text With a Minimum of Parameters Assume that you want to translate the word purchase order into French and Italian. You just want a quick translation without any additional features. For example, you don't use the domain concept or differentiate between text types. Based on these requirements, you use the following request payload: Request Body Example Sample Code "targetlanguages": [ 52 P U B L I C

53 } "fr", "it" ], "units": [ "value": "Purchase Order" } ] Response Body Example Sample Code } "units": [ "domain": "MM", "value": "Purchase Order", "translations": [ "language": "fr", "value": "Commande d'achat", "translationprovider": 0, "qualityindex": 91 }, "language": "it", "value": "Ordine d'acquisto", "translationprovider": 0, "qualityindex": 91 } ] } ] Translating Multiple Texts Assume that you want to translate the words user name, password, and sales order into French, Italian, and Spanish. Based on the app in which your texts are used, you want the translations to meet the following requirements: Used in the text type for field labels (XFLD) Assigned to the translation domain for CRM (B2) To judge the quality of the translations, you also want to see a quality rating for the translations. Based on these requirements, you use the following request payload: Request Body Example Sample Code "targetlanguages": [ "fr", "it", P U B L I C 53

54 } "es" ], "enabletranslationqualityestimation": true, "domain": "B2", "units": [ "texttype": "XFLD", "key": "LOGIN_USERNAME_FIELD", "value": "User Name" }, "texttype": "XFLD", "key": "PWD_FIELD", "value": "Password" }, "texttype": "XFLD", "key": "SALES_ORDER_FIELD", "value": "Sales Order" } ] Response Body Example Sample Code "units": [ "texttype": "XFLD", "domain": "B2", "key": "LOGIN_USERNAME_FIELD", "value": "User Name", "translations": [ "language": "it", "value": "Nome utente", "translationprovider": 0, "qualityindex": 94 }, "language": "es", "value": "Usuario", "translationprovider": 0, "qualityindex": 82 }, "language": "fr", "value": "Nom de l'utilisateur", "translationprovider": 0, "qualityindex": 77 } ] }, "texttype": "XFLD", "domain": "B2", "key": "PWD_FIELD", "value": "Password", "translations": [ "language": "es", "value": "Clave de acceso", "translationprovider": 0, "qualityindex": P U B L I C

55 } ] }, } ] }, }, } "language": "fr", "value": "Mot de passe", "translationprovider": 0, "qualityindex": 96 "language": "it", "value": "Password", "translationprovider": 0, "qualityindex": 98 "texttype": "XFLD", "domain": "B2", "key": "SALES_ORDER_FIELD", "value": "Sales Order", "translations": [ "language": "es", "value": "Pedido cliente", "translationprovider": 0, "qualityindex": 88 }, "language": "it", "value": "Ordine cliente", "translationprovider": 0, "qualityindex": 88 }, "language": "fr", "value": "Commande client", "translationprovider": 0, "qualityindex": 98 } ] Specifying a Particular Translation Assume that you want to translate the word cancel into Chinese, French, German, and Japanese. Your colleagues in the French subsidiary have already told you that the word cancel can be translated in several ways in French. In the app in question, the required translation of cancel is annuler. Furthermore, you want the translations to meet the following requirements: Used in the text type for field labels (XFLD) Assigned to the translation domain group for sales (02) To judge the quality of the translations, you also want to see a quality rating for the translations. You want to use only those translations that are in the MLTR, and don't want to use machine translation. P U B L I C 55

56 Based on these requirements, you use the following request payload: Request Body Example Sample Code } "targetlanguages": [ "de", "fr", "zh", "ja" ], "enablemt": false, "domain": "02", "units": [ "texttype": "XFLD", "key": "CANCEL", "value": "Cancel", "searchdata": "language": "fr", "value": "annuler" } } ] Response Body Example Sample Code "units": [ "texttype": "XFLD", "domain": "HC", "key": "CANCEL", "value": "Cancel", "translations": [ "language": "fr", "value": "annuler", "translationprovider": 0, "qualityindex": 88 }, "language": "de", "value": "stornieren", "translationprovider": 0, "qualityindex": 75 }, "language": "ja", "value": " 中止 ", "translationprovider": 0, "qualityindex": 77 }, "language": "zh", "value": " 取消 ", "translationprovider": 0, "qualityindex": 98 } 56 P U B L I C

57 } ] } ] Translating Texts from a Language Other Than English Assume that you want to translate the German word Benutzerdaten into English, Chinese, and Japanese. If possible, you would like translations that are used in the area of CRM, (domain B2). To judge the quality of the translations, you would like to see a quality rating for the translations. Based on these requirements, you use the following request payload: Request Body Example Sample Code } "targetlanguages": [ "en", "ja", "zh" ], "sourcelanguage": "de", "enabletranslationqualityestimation": true, "domain": "B2", "units": [ "key": "USER_DATA", "value": "Benutzerdaten" } ] Response Body Example Sample Code "units": [ "domain": "B2", "key": "USER_FRIENDLY", "value": "Benutzerdaten", "translations": [ "language": "zh", "value": " 用户数据 ", "translationprovider": 0, "qualityindex": 100 }, "language": "en", "value": "User Data", "translationprovider": 0, "qualityindex": 96 }, P U B L I C 57

58 } ] } ] } "language": "ja", "value": " ユーザデータ ", "translationprovider": 0, "qualityindex": 100 Translating Texts with Reference to a Company MLTR Assume that you have prepared a company MLTR (the ID of which is 325) that you would like to use as the first choice for translations in a particular project. For all other translations, you'd like to use the SAP MLTR and SAP MT within the area of CRM (domain B2). Based on this requirement, you use the following request payload: Request Body Example Sample Code } "targetlanguages": [ "de", "fr" ], "enabletranslationqualityestimation": true, "companymltrid": 325, "domain": "B2", "resultlimit": 10, "units": [ "value": "Cancel" }, "value": "Add" }, "value": "Username" } ] Response Body Example The following response shows that the company MLTR has been used (the value of the translation provider is 5). Sample Code "units": [ "value": "Cancel", "translations": [ 58 P U B L I C

59 } ] }, }, } ] }, } "language": "de", "value": "Stornieren", "translationprovider": 1, "qualityindex": 32 "language": "fr", "value": "Annular", "translationprovider": 1, "qualityindex": 36 "domain": "B2", "value": "Add", "translations": [ "language": "fr", "value": "Ajouter", "translationprovider": 0, "qualityindex": 100 }, "language": "de", "value": "Hinzufügen", "translationprovider": 0, "qualityindex": 99 } ] "domain": "BC", "value": "Username", "translations": [ "language": "de", "value": "Benutzernamen", "translationprovider": 5, "qualityindex": 100 }, "language": "fr", "value": "Identifiant", "translationprovider": 0 } ] Testing the APIs To test the individual APIs, for example, the translate API, you can use SAP API Business Hub or a REST service client. P U B L I C 59

60 Using SAP API Business Hub To try out the APIs without needing to paste the payload and API attributes manually into a REST service client, you can use SAP API Business Hub. In SAP API Business Hub, you can view the request and response models and, if you log on, try out the APIs in one central console. Using a REST Service Client To test the APIs, you can use a REST service client, for example, one of the clients that you can install as an extension to a Web browser. 1. In the REST service client, enter the URL specified in the API documentation. 2. Ensure that you specify the following attributes correctly for each API: Method value: GET or POST Content-Type parameter in the header: application/json; charset=utf-8 To consume the APIs, you enter the user and password for your account on SAP Cloud Platform. Depending on the REST service client that you use, you are asked to enter the user and password after sending the request. Alternatively, you store the user name and password as an attribute in the request header. For more information, see the documentation for the REST service client that you are using. 3. As a starting point, use the sample code provided in the API documentation, and adapt the API calls using the optional parameters as required. The following video shows how to test the translate API in a REST service client: Related Information on SAP API Business Hub Integration of with SAP Hybris Cloud for Customer The integration of in SAP Hybris Cloud for Customer for translating user interface texts is an example of how to integrate with other products. You can use the Language Adaptation work center in SAP Cloud for Customer to translate work center texts that are proposed by. 60 P U B L I C

61 Assume that you use SAP Hybris Cloud for Customer and want to expand your operations to a country whose language is currently not supported by SAP Hybris Cloud for Customer. In this scenario, you can translate work center texts into one of the languages that supports, but that SAP Hybris Cloud for Customer does not support as standard. Related Information Supported Languages [page 23] SAP Hybris Cloud for Customer SAP Hybris Cloud for Customer Administrator Guide Extend your Solution Translate and Adapt User Interface Texts 1.4 Translation Workflow Scenarios You can use to translate texts as part of integrated workflow scenarios. The scenarios enable you to translate texts, edit translations, and update the source location of texts. To manage the translation workflow scenarios, requires some information about the texts that you want to translate, such as the location of the texts you want to translate and the required target languages. You record this information in a translation project that is specific to a particular translation workflow scenario. You can use workflow scenarios for texts that reside in the following locations: ABAP Systems [page 62] Files [page 101] Git Repositories [page 77] Main Steps of Translation Workflow Scenarios When you start the translation process for one of the workflow scenarios, does the following: 1. Reads the translation project. 2. Gets translations from the following sequence of translation providers: 1. Company multilingual text repository (company MLTR) P U B L I C 61

62 2. SAP multilingual text repository (SAP MLTR) 3. SAP Machine Translation (SAP MT) 3. Enters translations in the source Git repository, ABAP system, or in a file that you download. Related Information Access UI for Translation Workflow Scenarios [page 62] Create Translation Projects for ABAP Short Texts Using an RFC [page 72] Create Translation Projects for Files [page 103] Create Translation Projects for Git Repository on SAP Cloud Platform [page 80] Glossary [page 21] Working with Translation Projects [page 111] Translation Project FAQ [page 113] Access UI for Translation Workflow Scenarios You use a dedicated UI to manage translation projects as part of the translation workflow scenarios and to subsequently review and edit translations. You access the UIs as follows: 1. In the SAP Cloud Platform cockpit, choose Services. 2. Choose the tile. 3. Choose Go to UI for Translation Workflow. Related Information Language of UIs for [page 22] ABAP Systems You can use to translate texts in ABAP systems. In your ABAP system, you enter the objects that contain the texts you want to translate in an object list. The object list represents the source of texts for. In, you manage the translation process by creating a translation project specific to ABAP systems. accesses the texts in your ABAP system using a remote function call (RFC). The communication between the two systems comprises three main parts: An RFC destination in the SAP Cloud Platform cockpit 62 P U B L I C

63 The Cloud Connector RFC-enabled function modules in the ABAP system The following graphic shows the main parts of the setup for ABAP systems: Related Information Blog About Setting Up the ABAP Scenario Create Translation Projects for ABAP Short Texts Using an RFC [page 72] Prerequisites for Translating ABAP Short Texts Using an RFC [page 63] Prerequisites for Translating ABAP Short Texts Using an RFC To use to translate short texts that you create in ABAP systems, several prerequisites are required. Recommendation To make it easier to make the required settings in the different systems, carry out the steps in the following sequence. 1. ABAP Back-End System [page 63] 2. Cloud Connector [page 67] 3. SAP Cloud Platform Cockpit [page 71] ABAP Back-End System To use to translate short texts that you create in ABAP systems, several prerequisites are required. The following sections contain the steps required as part of the ABAP translation workflow scenario. We recommend that you work through the steps in the following sequence. P U B L I C 63

64 1. Check Unicode code page Check whether your system is a Unicode system. If you don't know, use one of the following options to find out: Call transaction code SNLS. Choose System Status... SAP System Data. 2. Install RFC-enabled function modules To enable to read texts in development objects in your ABAP system, RFC-enabled function modules are required in your ABAP system. The required function modules are included in SAP Note Since the updates in the SAP Note might already have been implemented in your system, implement the SAP Note only if the required Support Package (SP) has not been installed and the SAP Note has not been implemented using the Note Assistant (SNOTE) transaction. Check these points as follows: The Support Package (SP) level of the SAP_BASIS software component in your system is lower than the SP specified for your version of SAP_BASIS in the SAP Note. Example The version of SAP_BASIS installed in your system is 740 and the SP level is 15: choose Status... System. In the SAP System Data section, choose the button to the right of the Product Version field. On the Support Packages tab in the SAP Note, you see that the updates are part of SP 16 (SAPKB74016). Since the SP level in your system (15) is lower than the SP that includes the required updates (16), check whether the SAP Note has been implemented using the Note Assistant (SNOTE) transaction. If the SP level in your system is lower than the SP level specified in the SAP Note, you won't have received the updates via an SP, but the SAP Note might have been implemented manually. To check, call the Note Assistant (SNOTE) transaction in your system and search for SAP Note If you don't find the SAP Note in SNOTE, implement it manually. 3. Create a technical user To enable to communicate with the ABAP system via the Cloud Connector, you need a technical user of type Communications Data in your ABAP system. For more information, see User Administration. 64 P U B L I C

65 4. Assign authorizations to the technical user The technical user requires generic authorizations and authorizations that are specific to. For general information about authorizations and role administration, see Reference Documentation for User and Role Administration or the corresponding documentation for the version of SAP NetWeaver that is installed in your system. Tip To help join the dots in the big picture, this is the user that you enter when you create the RFC destination in the SAP Cloud Platform cockpit: see the table in SAP Cloud Platform Cockpit [page 71]. We recommend that you assign authorizations via a role in the Role Maintenance (PFCG) transaction. The generic documentation for creating a role and assigning the required authorizations is at Creating Roles. This is a generic procedure; the specifics for are as follows: Since the role is for a technical user, don't make the settings that relate to the Menu tab. 1. In the Role Maintenance (PFCG) transaction, enter a technical name for the role and choose Single Role:. 2. Enter a description and save the role. 3. On the Authorizations tab, choose Change Authorization Data:. In the subsequent dialog box, do not select a template. 4. To add authorization objects to the role, choose Manually: 5. Enter the authorization objects S_RFC and S_ADMI_FCD. 6. Customize the authorization objects using the data in the following table.. P U B L I C 65

66 Tip To customize each authorization object, expand the folders until you see the technical names of the individual entries in the authorization object, such as the following:. Authorization Object Details S_RFC RFC_TYPE: FUNC (Function Module) RFC_NAME: LXE_STH_GET_OBJECT_LISTS, LXE_STH_READ_OBJECT_LIST, LXE_STH_READ_TEXTS, LXE_STH_WRITE_TEXTS, DDIF_FIELDINFO_GET, RFC_GET_FUNCTION_INTER FACE, RFCPING, SYSTEM_RESET_RFC_SERVER ACTVT: 16 (Execute) S_ADMI_FCD Check that the field proposed by the system is S_ADMI_FCD (System Administration Function and specify activity TRNR (Translation Administration SLWA/SLWB). 7. Ensure that all traffic lights are green. If they are not, check your entries. 8. To generate an authorization profile for the authorizations, choose Generate:. You are prompted for an authorization profile name. The system proposes a valid name in customer namespace. Confirm the entry or enter your own name and description. 9. Leave the tree display for authorizations by going back to the role overview screen. 10. Choose the User tab and assign the role to the technical user that you created in the Create a technical user section. To assign the role, enter the user ID of the technical user. 11. Save the role. 5. Create an object list Create an object list that contains the objects that you want to translate and schedule the object list report. For information about object lists and the translation setup in ABAP systems, see SAP Help Portal at help.sap.com/viewer/p/sap_netweaver. 66 P U B L I C

67 Under SAP NetWeaver Platform, choose your version of SAP NetWeaver, for example, SAP NetWeaver 7.5, and search for creating object lists Cloud Connector To make your ABAP system reachable from, you use the Cloud Connector. The following sections describe the steps that are required to install and configure the Cloud Connector. 1. Familiarize yourself with the Cloud Connector If you're new to the Cloud Connector, we recommend that you take some time to understand the purpose and general concepts. For more information, see Cloud Connector. 2. Install the Cloud Connector and perform initial configuration 1. Ensure that you have met the prerequisites described in Installation. All examples in the documentation are based on a Microsoft Windows installation. 2. Follow the installation instructions for your operating system. 3. In the Next Steps section, continue with the initial configuration: log in, change the administrator password, and choose an installation type. 4. Finalize the initial setup by entering details about the subaccount that you want to use, as described in the Set Up Connection Parameters and HTTPS Proxy section of the initial configuration. Ensure that the user you enter for the subaccount is assigned the Cloud Connector Admin role, as described in Set Up Connection Parameters and HTTPS Proxy. 5. Save your entries and proceed with the Configure access control for RFC section further down this page. 3. Configure access control for RFC To allow to access your ABAP back-end system, configure the Cloud Connector to use the RFC protocol. The steps comprise two parts: 1. Exposing a channel to your ABAP system (see A. Exposing intranet systems). 2. Creating a whitelist of function modules that can be accessed (see B. Granting access to function modules). P U B L I C 67

68 A. Exposing intranet systems 1. If you are not still logged on from earlier steps, log on to the Cloud Connector. 2. In the menu on the left, expand the required subaccount and choose Cloud To On-Premise. 3. On the ACCESS CONTROL tab, configure the Cloud Connector to expose an internal channel to your onpremise ABAP system. Choose the plus (+) sign. 4. Work through the steps in the Add System Mapping dialog box. In the Add System Mapping dialog, you choose whether you want to use load balancing. Since each option requires different entries, we've created a section for each option. Choose whichever option you use for your ABAP system. The option that you select influences the settings that you make in the SAP Cloud Platform cockpit. With load balancing (system ID and message server) Step A Field Back-End Type Entry ABAP System Step B Field Protocol Entry RFC 68 P U B L I C

69 Step C Field Connection Type Entry With load balancing (system ID and message server) Step D Field Message Server System ID SAProuter (optional) Entry Enter the message server listed in the properties of the system entry in your SAPGUI logon window. Enter the three-character system ID of your ABAP system. Entry is optional Step E Field Virtual Message Server Virtual System ID Entry Leave the default entry. Leave the default entry. Step F Field Description Entry Optional: to make it easier to record the purpose of your settings, enter a description. On the final screen, a summary of your entries appears. If you want to check the connection at this stage, select Check Internal Host. Choose Finish. Without load balancing (application server and instance number) Step A Field Back-End Type Entry ABAP System Step B Field Protocol Entry RFC Step C Field Connection Type Entry Without load balancing (application server and instance number) Step D Field Application Server Entry Enter the message server listed in the properties of the system entry in your SAPGUI logon window. P U B L I C 69

70 Field Instance Number SAProuter (optional) Entry Enter the instance number listed in the properties of the system entry in your SAPGUI logon window. Entry is optional Step E Field Virtual Application Server Virtual Instance Number Entry Leave the default entry. Leave the default entry. Step F Field Description Entry Optional: to make it easier to record the purpose of your settings, enter a description. On the final screen, a summary of your entries appears. If you want to check the connection at this stage, select Check Internal Host. Choose Finish. B. Granting access to function modules In addition to allowing access to a particular host and port, you also specify which function modules (known as resources in the Cloud Connector) are allowed to be invoked on that host. 1. Select the row containing the entry that you created in A. Exposing intranet systems and choose the plus sign in the section entitled Resource Available On <message server><system ID>:. 2. To specify which function modules can be invoked by the Cloud Connector, enter the following data: Field Function Name Enabled Naming Policy Description Entry LXE_STH Select the checkbox. Prefix Optional: Function modules for SAP Translation Hub. 3. Save your entries. 70 P U B L I C

71 SAP Cloud Platform Cockpit To enable to access your ABAP system via the Cloud Connector, you need a remote function call (RFC) destination that comprises the user name and password of the technical user that you created in the ABAP system. There must be one RFC destination on subaccount level for each of the ABAP systems that you want to use. Create a destination as follows: 1. In the SAP Cloud Platform cockpit, navigate to the required subaccount of your global account. 2. In the navigation structure on the left, choose Connectivity Destinations. 3. Create a new destination with the following properties: Field Name Entry STH_<name of the subaccount on SAP Cloud Platform>_<ABAP system ID>_<client in ABAP system> Example Enterprise accounts: STH_aa956e49a_A32_400 Trial accounts: STH_p trial_A32_400 Type Description Location ID User Password Repository User Repository Password RFC Optional: enter a description for the RFC description. Not required. Enter the user ID of the technical user that you created in the ABAP back-end system. Enter the password of the technical user that you created in the ABAP back-end system. Not required. Not required. You also need some additional properties. The additional properties that you require depend on the load balancing option that you choose when you configure access control in the Cloud Connector (see Configure access control for RFC Exposing intranet systems in Cloud Connector [page 67]). We'll start with the load balancing option: With load balancing (system ID and message server) Property jco.client.client Value Enter the client - as a three-digit number - of the on-premise ABAP system. For more information about the property, see User Logon Properties. P U B L I C 71

72 Property jco.client.mshost Value Enter the message server that you entered in the Cloud Connector - see the Configure access control for RFC section in Cloud Connector [page 67]. For more information about the property, see the Load Balancing Configuration section in Target System Configuration. jco.client.r3name Enter the three-character system ID of the ABAP system. For more information about the property, see the Load Balancing Configuration section in Target System Configuration. Without load balancing (application server and instance number) Property jco.client.client Value Enter the client (as a three-digit number) to be used in the on-premise ABAP system. For more information about the property, see User Logon Properties. jco.client.ashost Enter the message server that you entered as the application server in the Cloud Connector - see the Configure access control for RFC section in Cloud Connector [page 67]. For more information about the property, see Target System Configuration. jco.client.sysnr Enter sapgw<##>, where ## is the two-digit system number that you entered as the instance number in the Cloud Connector - see the Configure access control for RFC section in Cloud Connector [page 67]. For more information about the property, see Target System Configuration. 4. Save your entries Create Translation Projects for ABAP Short Texts Using an RFC uses translation projects to manage the translation workflow of short texts from object lists that are generated in ABAP systems. communicates directly with the selected ABAP system using a remote function call (RFC). See Prerequisites for Translating ABAP Short Texts Using an RFC [page 63]. To translate short texts created in ABAP systems, requires some details, such as the object list that contains the texts in the ABAP system and the required target languages. 1. Create a translation project by choosing ABAP Project as the type. 72 P U B L I C

73 2. Enter the following data: Field Project Name ABAP System Entry Enter a name for your translation project, for example, objectlist01. We recommend that you use a name that enables you to identify the object list from the selected ABAP system. Select the ABAP system from which you want to translate texts. Wondering why you see System Configured on Subscription Level in the dropdown? This means that the RFC destination for an ABAP system was created on subscription level, not on subaccount level. For more information, see the SAP Cloud Platform Cockpit section in the prerequisites. Object List Select the object list that contains your source texts to be translated. To select an object list, open the value help of the field and search for an ID or the description of an object list, using wildcards (*) if required. The search is case-sensitive. To improve the performance of the search, search only by ID or only by description. To access the specific search fields for an ID and a description, choose Show Filter Bar. Domain Select the translation domain that most closely matches the application area or business context of your source texts, for example, Financials or Logistics. Tip If you don't use domains or a similar concept and you're not sure what to select, we recommend General. Source Language Target Languages Select the source language from which you want to translate the texts in your source file. For more information, see Supported Languages [page 23]. Select the target languages into which you want to translate the texts in the object list. To improve performance, select only those target languages that you need. Show Quality Index for MT Decide whether you want to calculate a quality index for translations from English into selected languages that are provided by SAP Machine Translation (SAP MT). For more information, see Quality Index. If you enable this option, the processing time for translation increases. If you do not enable this option when you first translate texts in a translation project and then enable the option, does not show the quality index. If you want to see the quality index for existing translations, select the languages in the translation project again and translate the source texts again. If you translate the source texts again, note that lifecycle statuses are reset. P U B L I C 73

74 Field Entry Post-Editing Required Review Required Use Company MLTR Select Company MLTR Decide whether you want to check translations using a two-step process. This option enables you to carry out a dedicated post-editing step before the review step. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. If you enable this option, enable Review Required as well. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use at least one step to check translations. You can use the review step on its own or as part of a two-step process after post-editing. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use your own company MLTR for translations. If you decide to use a company MLTR for translations, you need to select which one to use. You can select one company MLTR for each translation project. Only active company MLTRs are available for selection. 3. Save the translation project. Your translation project contains the data required to translate the texts from the object list in your ABAP system. Once you have created your project, you can edit the project to add more target languages. If you add more target languages after you have translated the texts in a translation project, the translations of existing target languages are kept, even if you remove a language and add it again later. Related Information Access UI for Translation Workflow Scenarios [page 62] Managing Post-Editing and Review Steps [page 106] Quality Index [page 19] Supported Languages [page 23] Translate ABAP Short Texts Using an RFC [page 74] Update Translations in ABAP Systems Using an RFC [page 76] Translate ABAP Short Texts Using an RFC You use translation projects to translate short texts created in ABAP systems as part of the translation workflow of. You have made the settings described in Prerequisites for Translating ABAP Short Texts Using an RFC [page 63] and there is a translation project for the ABAP object list that contains the texts that you want to translate. 74 P U B L I C

75 On the UI for translation projects, choose the translation project that refers to the object list to be translated. Then choose one of the translation options in the bottom right of the screen: What Do You Want to Do? Choose this Option Follow-On Tasks Translate the texts and update the ABAP system immediately; I don't need to review them before updating the ABAP system. Any existing translations of your texts in the ABAP system will be overwritten. Translate and Transfer You can nevertheless check the translations on the Translations tab. Translate the texts and review them. Some texts are tricky, so I want to make sure the translations are up to scratch before updating the ABAP In the context menu on the Translate and Transfer button, choose Translate Without Transfer to ABAP. Review the translations on the Translations tab. After you're satisfied with the translations, transfer them to the ABAP system by choosing Transfer to ABAP. Handling Translation Projects That Are Canceled In certain situations, you might decide to cancel a translation project or the processing might be canceled due to connectivity issues. In these cases, we recommend that you transfer the available translations to the ABAP system before further processing the translation project. By transferring the available translations to the ABAP system, you ensure that does not translate the same texts again. And in the case of enterprise accounts, this process ensures that you are not billed for the same translations again. Example You start the translation process for an ABAP translation project. When only 30% of the translation project has been translated, you cancel the translation process. If you start the translation process for the same translation project again without first transferring the available translations to the ABAP system, translates the texts again. If you have an enterprise account, you are billed for the translations again. To avoid this situation, we recommend that after you cancel a translation project, you transfer the available translations to your ABAP system. Start the translation project again only after you have transferred the translations to your ABAP system. The source texts are translated into the target languages specified in the translation project. Review Translations If you want to view or change the translations in the project, choose the Translations tab. You see all the translations in the translation project and the translation provider that uses for each text. If some of the texts in the object list are already translated in your ABAP system, does not translate the texts again; in this case, ABAP appears as the translation provider. An ABAP system object can contain more than one text element. For example, a data element contains multiple field labels of different lengths plus a short description. In your translation projects, you see all text P U B L I C 75

76 elements that belong to a single object, which means that all text elements have the same object name. You also see the object type, such as DTEL for data elements, and the length of each field, as defined in the ABAP system. Consider Length Restrictions uses the maximum length defined for each text in an object in the ABAP system to find translations of the correct length. Note that this feature applies only to texts that retrieves from the SAP multilingual text repository (SAP MLTR). If cannot find a translation that fulfills the length restriction defined in the ABAP system, truncates the text and adds an ellipsis (...) to the truncated text to show that the text has been truncated. View Quality of Translations The quality index helps you to judge the quality of translations. The higher the number on a scale from 0-100, the better the quality. For more information, see Quality Index. Update Translations If you change any of the translations, save your changes in the translation project and transfer the changes to the ABAP system manually. For an overview of how to translate ABAP short texts, check out the following video on YouTube: Related Information Access UI for Translation Workflow Scenarios [page 62] Create Translation Projects for ABAP Short Texts Using an RFC [page 72] Update Translations in ABAP Systems Using an RFC [page 76] Quality Index [page 19] Update Translations in ABAP Systems Using an RFC You can use the UI to add or change translations created by during the translation workflow and to push the translations directly to an ABAP system. You have used the translation workflow of to translate the texts from an ABAP object list. When you use the translation workflow, stores the translations of texts from an ABAP object list for each target language. If required, you can create or update translations, and then push them back to the ABAP system. 76 P U B L I C

77 This process overwrites the existing translations from the ABAP system. Bear this in mind if you add or adjust translations in your ABAP system and you want to keep those changes. 1. On the UI, choose the translation project that refers to the ABAP object list whose translations you want to update. 2. Choose the Translations tab. shows the languages defined in the translation project along with the source texts from the object list and the translations. 3. Choose the target language in which you would like to check or update translations. 4. In the Translated Text column, update translations as required. The translation provider is updated to show that you changed the text that entered; your user name also appears under the technical name to show that you changed the translation. 5. Save your changes. If you need to change the translations in other target languages, repeat the previous steps for each target language. 6. To update your translation changes in the ABAP system, choose Transfer to ABAP. Related Information Access UI for Translation Workflow Scenarios [page 62] Building Base URL of [page 33] Create Translation Projects for ABAP Short Texts Using an RFC [page 72] Translate ABAP Short Texts Using an RFC [page 74] Git Repositories You can use to translate texts in.properties files that you manage in Git repositories. The following types of Git repository are supported: Git Repository on SAP Cloud Platform [page 78] Git Repository Hosted By Your Enterprise [page 87] Git Repository Hosted on the Web [page 95] P U B L I C 77

78 Git Repository on SAP Cloud Platform You can use to translate texts in.properties files that you manage in the Git repository on SAP Cloud Platform. Although you do not have to use SAP Web IDE as the development environment, to make it easier to explain and visualize the entire scenario, the following explanations and graphics contain SAP Web IDE. In, you manage the translation process by creating a translation project specific to the Git scenario. accesses the texts in your Git repository. This means that you must ensure all translation-relevant texts have been committed and pushed to your Git repository before you start the translation process. The process comprises the following main steps: 1. You commit and push the files in your SAP Web IDE project to the Git repository. 2. reads the files in the Git repository. 3. After translates the texts, it pushes the translated files to the Git repository. 4. You pull the changes in the Git repository to your SAP Web IDE project. The following graphic shows the main steps and parts in the Git repository scenario: Related Information Create Translation Projects for Git Repository on SAP Cloud Platform [page 80] Configure a Destination for your Git Repository This section contains the steps required to configure a destination for a Git repository on SAP Cloud Platform. You configure the HTTP destination for your Git repository if you are using your own identify provider (IDP). 1. In the SAP Cloud Platform cockpit, choose Services. 2. Choose from the list of services. 3. On the service description screen, choose Configure Service. 78 P U B L I C

79 4. Choose New Destination and enter the following data: Field Name Type Description URL Entry gitconnectionconfig HTTP Enter a description of your choice, for example, Configuration for Git connection. Enter the Git URL for the SAP Cloud Platform region host you are by using the following pattern: SAP Cloud Platform region host> You can take the region host from the base URL of SAP Cloud Platform. If you have a trial account (hanatrial.ondemand.com), enter git.hanatrial.ondemand.com If you have an enterprise account, your entry depends on your Neo region and host as follows: Australia (Sydney) (ap1.hana.ondemand.com), enter git.ap1.hana.ondemand.com Europe (Amsterdam) (eu3.hana.ondemand.com), enter git.eu3.hana.ondemand.com Europe (Rot) (hana.ondemand.com), enter git.hana.ondemand.com Alternatively, for eu1.hana.ondemand.com), enter git.eu1.hana.ondemand.com US East (Ashburn) (us1.hana.ondemand.com), enter git.us1.hana.ondemand.com US East (Sterling) (us3.hana.ondemand.com), enter git.us3.hana.ondemand.com US West (Chandler) (us2.hana.ondemand.com), enter git.us2.hana.ondemand.com Proxy Type Authentication User Internet BasicAuthentication Enter the desired user based on the following pattern: <valid user name for SAP Cloud Platform>,< ID for the same user>@<domain name> Example: username,username@sap.com Access to a Git repository is granted only to users who are authenticated by the SAP ID service. This user must have a developer role in your account and have a valid S user. This configuration means that all operations from to the Git server of your region host ( SAP Cloud Platform region host>.ondemand.com) are executed by the user that you specify here, and not by the actual end user who performs the action. Password Enter the user's password. P U B L I C 79

80 5. Wait for the changes to take effect; depending on the system performance, it can take several minutes for the changes to take effect. Here is an example of the configuration settings for a destination involving an SAP Cloud Platform Git repository. The User field contains both the user ID, and the user's separated by a comma; this means the user can skip specifying the in the Additional Properties popup window. Related Information Regions and Hosts [page 23] Create Translation Projects for Git Repository on SAP Cloud Platform uses translation projects to manage the translation workflow of properties files in applications for which you use the Git repository on SAP Cloud Platform. The encoding of the properties file is UTF-8. If you use your own identity provider (IDP), make the settings described in Configure a Destination for your Git Repository [page 78]. If you use the suggestions API to propose texts in the code editor of SAP Web IDE, use one of the browsers listed in Open SAP Web IDE. If you are translating i18n.properties files for an SAP Web IDE project, see Use. To translate source.properties files, requires some details, such as the location of the source.properties file in the Git repository and the required target languages. 80 P U B L I C

81 1. Create a translation project by choosing Git Project as the type. 2. Enter the following data: Field Project Name Path to Properties File Entry Enter a name that describes your translation project. Enter or select the source.properties file of your application in the Git repository. Tip To select the required.properties file from a dropdown, save your Git credentials. Escape Non-ASCII Chars Select to show machine-readable texts in your downloaded translations file. The file then contains Unicode escape sequences for non-ascii characters ( \uxxxx). This is required only when your translations involve ISO encoding and you need to interpret the content. If you do not select this option (default), the translated file contains human-readable text. Domain Select the translation domain that most closely matches the business context of the application, such as Financials or Logistics. Tip If you don't use domains or a similar concept and you're not sure what to select, we recommend General. Source Language Target Languages Select the source language from which you want to translate the texts in your source file. For more information, see Supported Languages [page 23]. Select the target languages into which you want to translate the texts in the properties file. To improve performance, select only those target languages that you need. Git Server Application Name Branch Git Credentials Select SAP Cloud Platform. Enter the name of the Git repository that contains the application and its source properties file that you want to translate. Use the entry in the Name column of the Git Repositories node in the navigation area of the SAP Cloud Platform cockpit. To see the Git repositories for your account, in the SAP Cloud Platform cockpit, choose Repositories Git Repositories. By default, the branch is master. If you're using a different branch in the Git repository, change the entry as required. If you want to save your Git credentials in, choose Save. By entering the Git credentials, you can choose from possible.properties files in a dropdown on the translation project UI and you do not have to enter your Git credentials each time you translate your translation project. If Destination appears, your Git credentials are saved in a destination in the SAP Cloud Platform cockpit. Path to Properties File Enter or select the source.properties file of your application in the Git repository. P U B L I C 81

82 Field Entry Tip To select the required.properties file from a dropdown, save your Git credentials. Escape Non-ASCII Chars Select to show machine-readable texts in your downloaded translations file. The file then contains Unicode escape sequences for non-ascii characters ( \uxxxx). This is required only when your translations involve ISO encoding and you need to interpret the content. If you do not select this option (default), the translated file contains human-readable text. Keep Translations If you already translated the texts in your properties file, for example, using a different translation provider to, your application already contains translations in language-specific properties files. You use the Keep Translations option to determine how SAP Translation Hub handles these existing translations: If you want to keep the existing translations and have translate only those texts that do not yet have a translation in your application, choose Yes. When you use to translate the texts in your properties file, SAP Translation Hub stores the translations. If you use to translate your properties file a second or subsequent time and you add texts in the source language, uses the same translations for the existing texts that it used during the previous translation of the properties file. If you change any translations directly in the language-specific properties files in your Git project and then use again, ignores your translation changes. The translation changes from your Git project are lost. To prevent from overwriting any translations in your Git project, we recommend that you make all translation changes in. If you want to translate all the texts in your properties file from scratch, and therefore overwrite any existing translations in your properties files, choose No. Show Quality Index for MT Decide whether you want to calculate a quality index for translations from English into selected languages that are provided by SAP Machine Translation (SAP MT). For more information, see Quality Index. If you enable this option, the processing time for translation increases. If you do not enable this option when you first translate texts in a translation project and then enable the option, does not show the quality index. If you want to see the quality index for existing translations, select the languages in the translation project again and translate the source texts again. If you translate the source texts again, note that lifecycle statuses are reset. 82 P U B L I C

83 Field Entry Post-Editing Required Decide whether you want to check translations using a two-step process. This option enables you to carry out a dedicated post-editing step before the review step. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. If you enable this option, enable Review Required as well. For more information, see Managing Post-Editing and Review Steps. Review Required Use Company MLTR Select Company MLTR Decide whether you want to use at least one step to check translations. You can use the review step on its own or as part of a two-step process after post-editing. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use your own company MLTR for translations. If you decide to use a company MLTR for translations, you need to select which one to use. You can select one company MLTR for each translation project. Only active company MLTRs are available for selection. 3. Save the translation project. Your translation project contains the data required to translate the texts in a properties file. You can use the translation workflow to get an initial translation of the texts in the.properties file, as well as to update translations whenever changes are made to the texts in the source.properties file. Related Information Access UI for Translation Workflow Scenarios [page 62] Managing Post-Editing and Review Steps [page 106] Quality Index [page 19] Supported Languages [page 23] Translate Properties Files [page 83] Update Translations in Properties Files [page 85] Translate Properties Files You use translation projects to translate.properties files, which are stored in a Git repository, as part of the translation workflow of. There is a translation project for the application that contains the.properties file that you want to translate. On the UI for translation projects, choose the translation project that refers to the.properties file to be translated, and choose one of the translation options in the bottom right of the screen: P U B L I C 83

84 What Do You Want to Do? Choose this Option Follow-On Tasks Translate the texts in the.properties file and create.properties files for each target language in the Git repository; I don't want to review them first. Translate and Push When you choose this option, SAP Translation Hub pulls the latest version of the.properties file from the Git repository. The target language properties files already exist in your Git repository, but you can still check the translations on the Translations tab. Translate the texts and review them. Some texts are tricky, so I want to make sure that the translations are up to scratch before I push them to the Git repository. In the context menu on the Translate and Push button, choose Translate Without Push. Review the translations on the Translations tab. When you're satisfied with the translations, push them to the Git repository. When you choose this option, SAP Translation Hub pulls the latest version of the.properties file from the Git repository. To verify that your.properties file has been translated and updated in your Git repository, view details in the Git repository browser. For SAP Cloud Platform, view the Git repository from the navigation area of the SAP Cloud Platform cockpit. Choose Repositories Git Repositories and then choose the glasses icon in the row for the required Git repository. The.properties file is translated into the target languages specified in the translation project. For more information, see the following sections. Review Translations If you want to view or change the translations in the project and see the translation provider for each text, choose the Translations tab. View Quality of Translations The quality index helps you to judge the quality of translations. The higher the number on a scale from 0-100, the better the quality. For more information, see Quality Index. Updating Translations in Git Repository If you change any of the translations, save your changes and push the changes to the Git repository manually. For an overview of how to translate a.properties file that you develop in SAP Web IDE and manage in the Git repository of SAP Cloud Platform, check out the following video: 84 P U B L I C

85 Related Information Access UI for Translation Workflow Scenarios [page 62] Quality Index [page 19] Update Translations in Properties Files You can use the UI to add or change translations created by during the translation workflow. You have used the translation workflow of to translate the texts in the.properties file of an application. When you use the translation workflow of, enters translations in.properties files for each target language. If required, you can create or update the texts in the.properties files for each target language. 1. On the UI, choose the translation project that refers to the.properties files whose translations you want to update. 2. Choose the Translations tab. shows the languages defined in the translation project along with the source texts from the.properties file and the translations. 3. Choose the target language in which you would like to check or update translations. 4. In the Translated Text column, update translations as required. The translation provider is updated to show that you changed the text that entered. 5. Save your changes. If you need to change the translations in other target languages, repeat the previous steps for each target language. 6. To add any translation changes to the.properties files in the Git repository, choose Push. To view the.properties files in your development environment, for example, in SAP Web IDE, you must pull the latest changes from the Git repository. Related Information Access UI for Translation Workflow Scenarios [page 62] P U B L I C 85

86 Sample Scenario with SAP Web IDE You can use to translate an HTML5 application that you create in SAP Web IDE. You have a trial account on SAP Cloud Platform. You have enabled in the service catalog on SAP Cloud Platform. You are using one of the browsers listed in Open SAP Web IDE. This section contains the main steps required to translate the texts that you create for an HTML5 application in SAP Web IDE on SAP Cloud Platform. For details about the individual steps, especially the steps required to deploy your app on SAP Cloud Platform and to manage the Git repository on SAP Cloud Platform, see the following: Video on YouTube: Tutorial: Create and translate a sample Fiori app with 1. On SAP Cloud Platform, create an HTML5 application using SAP Web IDE. During the development process, you can use the following features to propose texts in English: Propose texts from when you create new strings (see Managing i18n Strings in Working in the Code Editor) Propose existing texts from the local i18n.properties file (see Using Code Completion) 2. Save your HTML5 project, and commit and push your changes to the Git repository. If you use the Git repository on SAP Cloud Platform, note the steps required to initialize your Git repository and to deploy your application to SAP Cloud Platform. 3. Call the UI, and create a translation project for the required source properties file in your HTML5 application. 4. Choose the translation project for the required source properties file in your HTML5 application, and choose Get Translations. 5. To see the translated properties files in SAP Web IDE, pull the changes from your Git repository. There is a properties file for each of the target languages that you entered in the translation project for your HTML5 application. The properties files are stored in the same project in the Git repository as the rest of the project files. Related Information Create Translation Projects for Git Repository on SAP Cloud Platform [page 80] Deploying Applications to SAP Cloud Platform SAP Web IDE Translate Properties Files [page 83] Translation Workflow Scenarios [page 61] Update Translations in Properties Files [page 85] 86 P U B L I C

87 Git Repository Hosted By Your Enterprise can connect to on-premise Git repositories that are hosted by your enterprise. pulls the files for translation from the on-premise Git repository and push back the translated files. accesses the texts in your on-premise Git repository using an HTTP(S) connection. The communication between the two systems comprises three main parts: An HTTP connection in the SAP Cloud Platform cockpit The Cloud Connector Your on-premise Git repository The following graphic shows the main parts of the setup: Related Information Prerequisites for Git Repository Hosted By Your Enterprise [page 87] Configure the Cloud Connector [page 88] Create Translation Projects for Git Repository Hosted By Your Enterprise [page 90] Prerequisites for Git Repository Hosted By Your Enterprise This section contains the integration tasks that are required before you can use an on-premise Git repository that is hosted by your enterprise. Task You have account logon details for the on-premise Git repository. You have familiarized yourself with the purpose and general concepts of the Cloud Connector. More Information None. See Scenarios and Basic Tasks in Cloud Connector. P U B L I C 87

88 Task You have installed the Cloud Connector and completed the initial configuration. More Information 1. See Tasks in Installation. 2. Complete the steps described in Initial Configuration. Ensure that you have Cloud Connector administrator rights. You have configured the Cloud Connector to communicate with your on-premise Git repository. See Configure the Cloud Connector [page 88] Configure the Cloud Connector To enable to communicate with your on-premise Git repository, you configure the Cloud Connector. 1. Log on to the Cloud Connector (see Initial Configuration). 2. In the menu on the left, expand the required subaccount and choose Cloud To On-Premise. 3. On the ACCESS CONTROL tab, configure the Cloud Connector to expose an internal channel to your onpremise Git server. Choose the plus (+) sign. 4. Make the settings in the following table: 88 P U B L I C

89 Field Back-End Type Protocol Internal Host Internal Port Virtual Host Entry Non-SAP System Enter HTTP or HTTPS, depending on your Git server requirements. Enter the internal host for your Git server. Enter the internal port for your Git server. Leave the default value - the virtual host is the same as the internal host. Virtual Port 80 Principal Type Description Check Internal Host None Enter an optional description for the mapping. Optional: If you want to test the connection to the internal host, select the checkbox. For more information, see Exposing Intranet Systems in Configuring Access Control (HTTP). 5. In the Resources Accessible On <host>:<port> section on the ACCESS CONTROL tab, choose the plus (+) sign. 6. Enter a path to the server that you defined in a previous step by making the settings described in the following table: Field Value URL Path / Enabled Access Policy Description Select Path and all sub-paths Optional: Enter a description for the resource. 7. Choose Save. Related Information Cloud Connector P U B L I C 89

90 Create Translation Projects for Git Repository Hosted By Your Enterprise Translation projects in can be created with reference to an on premise Git repository that is hosted by your enterprise. See Prerequisites for Git Repository Hosted By Your Enterprise [page 87]. To translate source.properties files, requires some details, such as the location of the source.properties file in the Git repository and the required target languages. 1. Call the UI for translation projects, as described in Access UI for Translation Workflow Scenarios. 2. Create a translation project by choosing Git Project as the type. 3. Enter the following data: Field Project Name Domain Entry Enter a name that describes your translation project. Select the translation domain that most closely matches the business context of the application, such as Financials or Logistics. Tip If you don't use domains or a similar concept and you're not sure what to select, we recommend General. Source Language Target Languages Select the source language from which you want to translate the texts in your source file. For more information, see Supported Languages [page 23]. Select the target languages into which you want to translate the texts in the properties file. To improve performance, select only those target languages that you need. Git Server Git URL Select Enterprise. Enter the URL for your on-premise Git repository. Example The URL must start with or Branch Git Credentials By default, the branch is master. If you're using a different branch in the Git repository, change the entry as required. If you want to save your Git credentials in, choose Save. By entering the Git credentials, you can choose from possible.properties files in a dropdown on the translation project UI and you do not have to enter your Git credentials each time you translate your translation project. 90 P U B L I C

91 Field Entry does not check the validity and correctness of Git credentials when you save them on the translation project UI. checks the credentials only when you push translations to the Git repository. Path to Properties File Enter or select the source.properties file of your application in the Git repository. Tip To select the required.properties file from a dropdown, save your Git credentials. Escape Non-ASCII Chars Select to show machine-readable texts in your downloaded translations file. The file then contains Unicode escape sequences for non-ascii characters ( \uxxxx). This is required only when your translations involve ISO encoding and you need to interpret the content. If you do not select this option (default), the translated file contains human-readable text. Keep Translations If you already translated the texts in your properties file, for example, using a different translation provider to, your application already contains translations in language-specific properties files. You use the Keep Translations option to determine how SAP Translation Hub handles these existing translations: If you want to keep the existing translations and have translate only those texts that do not yet have a translation in your application, choose Yes. When you use to translate the texts in your properties file, SAP Translation Hub stores the translations. If you use to translate your properties file a second or subsequent time and you add texts in the source language, uses the same translations for the existing texts that it used during the previous translation of the properties file. If you change any translations directly in the language-specific properties files in your Git project and then use again, ignores your translation changes. The translation changes from your Git project are lost. To prevent from overwriting any translations in your Git project, we recommend that you make all translation changes in. If you want to translate all the texts in your properties file from scratch, and therefore overwrite any existing translations in your properties files, choose No. Show Quality Index for MT Decide whether you want to calculate a quality index for translations from English into selected languages that are provided by SAP Machine Translation (SAP MT). For more information, see Quality Index. If you enable this option, the processing time for translation increases. P U B L I C 91

92 Field Entry If you do not enable this option when you first translate texts in a translation project and then enable the option, does not show the quality index. If you want to see the quality index for existing translations, select the languages in the translation project again and translate the source texts again. If you translate the source texts again, note that lifecycle statuses are reset. Post-Editing Required Review Required Use Company MLTR Select Company MLTR Decide whether you want to check translations using a two-step process. This option enables you to carry out a dedicated post-editing step before the review step. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. If you enable this option, enable Review Required as well. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use at least one step to check translations. You can use the review step on its own or as part of a two-step process after post-editing. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use your own company MLTR for translations. If you decide to use a company MLTR for translations, you need to select which one to use. You can select one company MLTR for each translation project. Only active company MLTRs are available for selection. 4. In the Project Configuration section, specify the editing and review requirements that you need for your translation project. 5. Choose Save. 6. After the translation project has been saved, choose the required translation option in the bottom right of the UI (Translate and Push or Translate Without Push). 7. Enter your Git credentials. If required, you can save your credentials in. If you choose this option, you can update your credentials at a later point in time by editing the translation project. 8. After the execution status changes to Completed successfully, you can view the translations on the Translations tab. Related Information Access UI for Translation Workflow Scenarios [page 62] Managing Post-Editing and Review Steps [page 106] Quality Index [page 19] Supported Languages [page 23] Translate Properties Files [page 93] Update Translations in Properties Files [page 94] 92 P U B L I C

93 Translate Properties Files You use translation projects to translate.properties files, which are stored in a Git repository, as part of the translation workflow of. There is a translation project for the application that contains the.properties file that you want to translate. On the UI for translation projects, choose the translation project that refers to the.properties file to be translated, and choose one of the translation options in the bottom right of the screen: What Do You Want to Do? Choose this Option Follow-On Tasks Translate the texts in the.properties file and create.properties files for each target language in the Git repository; I don't want to review them first. Translate and Push When you choose this option, SAP Translation Hub pulls the latest version of the.properties file from the Git repository. The target language properties files already exist in your Git repository, but you can still check the translations on the Translations tab. Translate the texts and review them. Some texts are tricky, so I want to make sure that the translations are up to scratch before I push them to the Git repository. In the context menu on the Translate and Push button, choose Translate Without Push. Review the translations on the Translations tab. When you're satisfied with the translations, push them to the Git repository. When you choose this option, SAP Translation Hub pulls the latest version of the.properties file from the Git repository. To verify that your.properties file has been translated and updated in your Git repository, view details in the Git repository browser. For SAP Cloud Platform, view the Git repository from the navigation area of the SAP Cloud Platform cockpit. Choose Repositories Git Repositories and then choose the glasses icon in the row for the required Git repository. The.properties file is translated into the target languages specified in the translation project. For more information, see the following sections. Review Translations If you want to view or change the translations in the project and see the translation provider for each text, choose the Translations tab. View Quality of Translations The quality index helps you to judge the quality of translations. The higher the number on a scale from 0-100, the better the quality. For more information, see Quality Index. P U B L I C 93

94 Updating Translations in Git Repository If you change any of the translations, save your changes and push the changes to the Git repository manually. For an overview of how to translate a.properties file that you develop in SAP Web IDE and manage in the Git repository of SAP Cloud Platform, check out the following video: Related Information Access UI for Translation Workflow Scenarios [page 62] Quality Index [page 19] Update Translations in Properties Files You can use the UI to add or change translations created by during the translation workflow. You have used the translation workflow of to translate the texts in the.properties file of an application. When you use the translation workflow of, enters translations in.properties files for each target language. If required, you can create or update the texts in the.properties files for each target language. 1. On the UI, choose the translation project that refers to the.properties files whose translations you want to update. 2. Choose the Translations tab. shows the languages defined in the translation project along with the source texts from the.properties file and the translations. 3. Choose the target language in which you would like to check or update translations. 4. In the Translated Text column, update translations as required. The translation provider is updated to show that you changed the text that entered. 5. Save your changes. If you need to change the translations in other target languages, repeat the previous steps for each target language. 6. To add any translation changes to the.properties files in the Git repository, choose Push. To view the.properties files in your development environment, for example, in SAP Web IDE, you must pull the latest changes from the Git repository. 94 P U B L I C

95 Related Information Access UI for Translation Workflow Scenarios [page 62] Git Repository Hosted on the Web can connect to Git repositories hosted on the Web by third-party providers. can then pull the files for translation from the Web Git repository and push back the translated files. The process comprises the following main steps: 1. You commit and push files to your Git repository. 2. reads the files in the Git repository. 3. After translates the texts, it pushes the translated files to the Git repository. 4. You pull the changes in the Git repository to your development project. The following graphic shows the main steps and parts of the scenario: Related Information Prerequisites for Git Repository Hosted on the Web [page 95] Create Translation Projects for Git Repository Hosted on the Web [page 96] Prerequisites for Git Repository Hosted on the Web This section contains the prerequisites that must be met before you can use a Git repository that is hosted by a third-party Web host. You have account logon details for a Git repository hosted by a third-party Web host. You have created a Git repository that is hosted by your Web host. P U B L I C 95

96 Create Translation Projects for Git Repository Hosted on the Web Translation projects in can be created with reference to a Git repository hosted by a thirdparty Web host. See Prerequisites for Git Repository Hosted on the Web [page 95]. To translate source.properties files, requires some details, such as the location of the source.properties file in the Git repository and the required target languages. 1. Call the UI for translation projects, as described in Access UI for Translation Workflow Scenarios. 2. Create a translation project by choosing Git Project as the type. 3. Enter the following data: Field Project Name Domain Entry Enter a name that describes your translation project. Select the translation domain that most closely matches the business context of the application, such as Financials or Logistics. Tip If you don't use domains or a similar concept and you're not sure what to select, we recommend General. Source Language Target Languages Select the source language from which you want to translate the texts in your source file. For more information, see Supported Languages [page 23]. Select the target languages into which you want to translate the texts in the properties file. To improve performance, select only those target languages that you need. Git Server Git URL Select Web. Enter the URL for the Git repository that you would like to use for your translation project. Valid URLs are preceded by either or You must have an active user account linked with the Git URL. Branch Git Credentials By default, the branch is master. If you're using a different branch in the Git repository, change the entry as required. If you want to save your Git credentials in, choose Save. By entering the Git credentials, you can choose from possible.properties files in a dropdown on the translation project UI and you do not have to enter your Git credentials each time you translate your translation project. 96 P U B L I C

97 Field Entry does not check the validity and correctness of Git credentials when you save them on the translation project UI. checks the credentials only when you push translations to the Git repository. Path to Properties File Enter or select the source.properties file of your application in the Git repository. Tip To select the required.properties file from a dropdown, save your Git credentials. Escape Non-ASCII Chars Select to show machine-readable texts in your downloaded translations file. The file then contains Unicode escape sequences for non-ascii characters ( \uxxxx). This is required only when your translations involve ISO encoding and you need to interpret the content. If you do not select this option (default), the translated file contains human-readable text. Keep Translations If you already translated the texts in your properties file, for example, using a different translation provider to, your application already contains translations in language-specific properties files. You use the Keep Translations option to determine how SAP Translation Hub handles these existing translations: If you want to keep the existing translations and have translate only those texts that do not yet have a translation in your application, choose Yes. When you use to translate the texts in your properties file, SAP Translation Hub stores the translations. If you use to translate your properties file a second or subsequent time and you add texts in the source language, uses the same translations for the existing texts that it used during the previous translation of the properties file. If you change any translations directly in the language-specific properties files in your Git project and then use again, ignores your translation changes. The translation changes from your Git project are lost. To prevent from overwriting any translations in your Git project, we recommend that you make all translation changes in. If you want to translate all the texts in your properties file from scratch, and therefore overwrite any existing translations in your properties files, choose No. Show Quality Index for MT Decide whether you want to calculate a quality index for translations from English into selected languages that are provided by SAP Machine Translation (SAP MT). For more information, see Quality Index. If you enable this option, the processing time for translation increases. P U B L I C 97

98 Field Entry If you do not enable this option when you first translate texts in a translation project and then enable the option, does not show the quality index. If you want to see the quality index for existing translations, select the languages in the translation project again and translate the source texts again. If you translate the source texts again, note that lifecycle statuses are reset. Post-Editing Required Review Required Use Company MLTR Select Company MLTR Decide whether you want to check translations using a two-step process. This option enables you to carry out a dedicated post-editing step before the review step. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. If you enable this option, enable Review Required as well. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use at least one step to check translations. You can use the review step on its own or as part of a two-step process after post-editing. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use your own company MLTR for translations. If you decide to use a company MLTR for translations, you need to select which one to use. You can select one company MLTR for each translation project. Only active company MLTRs are available for selection. 4. In the Project Configuration section, specify the editing and review requirements that you need for your translation project. 5. Choose Save. 6. After the translation project has been saved, choose the required translation option in the bottom right of the UI (Translate and Push or Translate Without Push). 7. Enter your Git credentials. If required, you can save your credentials in. If you choose this option, you can update your credentials at a later point in time by editing the translation project. 8. After the execution status changes to Completed successfully, you can view the translations on the Translations tab. Related Information Access UI for Translation Workflow Scenarios [page 62] Managing Post-Editing and Review Steps [page 106] Quality Index [page 19] Supported Languages [page 23] Translate Properties Files [page 99] Update Translations in Properties Files [page 100] 98 P U B L I C

99 Translate Properties Files You use translation projects to translate.properties files, which are stored in a Git repository, as part of the translation workflow of. There is a translation project for the application that contains the.properties file that you want to translate. On the UI for translation projects, choose the translation project that refers to the.properties file to be translated, and choose one of the translation options in the bottom right of the screen: What Do You Want to Do? Choose this Option Follow-On Tasks Translate the texts in the.properties file and create.properties files for each target language in the Git repository; I don't want to review them first. Translate and Push When you choose this option, SAP Translation Hub pulls the latest version of the.properties file from the Git repository. The target language properties files already exist in your Git repository, but you can still check the translations on the Translations tab. Translate the texts and review them. Some texts are tricky, so I want to make sure that the translations are up to scratch before I push them to the Git repository. In the context menu on the Translate and Push button, choose Translate Without Push. Review the translations on the Translations tab. When you're satisfied with the translations, push them to the Git repository. When you choose this option, SAP Translation Hub pulls the latest version of the.properties file from the Git repository. To verify that your.properties file has been translated and updated in your Git repository, view details in the Git repository browser. For SAP Cloud Platform, view the Git repository from the navigation area of the SAP Cloud Platform cockpit. Choose Repositories Git Repositories and then choose the glasses icon in the row for the required Git repository. The.properties file is translated into the target languages specified in the translation project. For more information, see the following sections. Review Translations If you want to view or change the translations in the project and see the translation provider for each text, choose the Translations tab. View Quality of Translations The quality index helps you to judge the quality of translations. The higher the number on a scale from 0-100, the better the quality. For more information, see Quality Index. P U B L I C 99

100 Updating Translations in Git Repository If you change any of the translations, save your changes and push the changes to the Git repository manually. For an overview of how to translate a.properties file that you develop in SAP Web IDE and manage in the Git repository of SAP Cloud Platform, check out the following video: Related Information Access UI for Translation Workflow Scenarios [page 62] Quality Index [page 19] Update Translations in Properties Files You can use the UI to add or change translations created by during the translation workflow. You have used the translation workflow of to translate the texts in the.properties file of an application. When you use the translation workflow of, enters translations in.properties files for each target language. If required, you can create or update the texts in the.properties files for each target language. 1. On the UI, choose the translation project that refers to the.properties files whose translations you want to update. 2. Choose the Translations tab. shows the languages defined in the translation project along with the source texts from the.properties file and the translations. 3. Choose the target language in which you would like to check or update translations. 4. In the Translated Text column, update translations as required. The translation provider is updated to show that you changed the text that entered. 5. Save your changes. If you need to change the translations in other target languages, repeat the previous steps for each target language. 6. To add any translation changes to the.properties files in the Git repository, choose Push. To view the.properties files in your development environment, for example, in SAP Web IDE, you must pull the latest changes from the Git repository. 100 P U B L I C

101 Related Information Access UI for Translation Workflow Scenarios [page 62] Files You can use to translate the contents of files that you upload manually. In a typical scenario, you develop an application in a particular development environment and store your translation-relevant texts in a resources file. Examples of resources files are.properties files and.xliff files. In, you manage the translation process by creating a translation project for files that you upload. When you want to translate the contents of the file, you upload the file from your local development environment to the translation project in. After has translated the texts in the translation project, you download the translated files and import them in your local development environment. The following graphic shows an overview of the file upload scenario: Related Information Create Translation Projects for Files [page 103] Supported File Formats [page 102] P U BL IC 101

102 Supported File Formats You can use to translate files in the following formats. File Format File Extension Supported Encoding Additional Information ABAP-based XLIFF.xlf UTF-8 For information about ABAPbased XLIFF files that are generated using the export features of SAP NetWeaver, search for the following topics in your SAP NetWeaver version on SAP Help Portal: Android XML.xml UTF-8 None. ios strings.strings UTF-8 None. ios XLIFF.xlf,.xliff UTF-8 None. Exporting Texts for Offline Translation Importing Texts After Offline Translation Java properties.properties UTF-8 Although it is possible to use ISO encoded source files, translated files are UTF-8 encoded. For ISO compatability, use the Escape Non-ASCII characters option when you create your translation project. JSON.json UTF-8 Code Syntax "key1": "value1", " key2": "value2" } Sample Code "okbutton": "OK", "cancelbutton" : "Cancel" } SAP HANA text bundle.hdbtextbundle UTF-8 None. 102 P U B L I C

103 File Format File Extension Supported Encoding Additional Information XLIFF for SAP Smart Business services.xlf UTF-8 None Create Translation Projects for Files enables you to upload and translate files in various formats. The encoding of the file is supported by - see Supported File Formats [page 102]. 1. Create a translation project by choosing File Upload as the type. 2. Enter the following data: Field Project Name File Type Escape Non-ASCII Chars Entry Enter a name that describes your translation project. Select the file type of the file that you want to translate. Select this option if you want to show machine-readable texts in the translated file that you download. The file will contain Unicode escape sequences for non-ascii characters ( \uxxxx). This is required only if your translations involve Java properties files with ISO encoding, and you need to interpret the content. If you do not select this option (default), the translated file contains human-readable text. Domain Select the translation domain that most closely matches the business context of your source texts, for example, Financials or Logistics. Tip If you don't use domains or a similar concept and you're not sure what to select, we recommend General. Source Language Target Languages Select the source language from which you want to translate the texts in your source file. For more information, see Supported Languages [page 23]. Select the target languages into which you want to translate the texts in your source file. To improve performance, select only those target languages that you need. Show Quality Index for MT Decide whether you want to calculate a quality index for translations from English into selected languages that are provided by SAP Machine Translation (SAP MT). For more information, see Quality Index. If you enable this option, the processing time for translation increases. P U BL IC 103

104 Field Entry If you do not enable this option when you first translate texts in a translation project and then enable the option, does not show the quality index. If you want to see the quality index for existing translations, select the languages in the translation project again and translate the source texts again. If you translate the source texts again, note that lifecycle statuses are reset. Post-Editing Required Review Required Use Company MLTR Select Company MLTR Decide whether you want to check translations using a two-step process. This option enables you to carry out a dedicated post-editing step before the review step. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. If you enable this option, enable Review Required as well. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use at least one step to check translations. You can use the review step on its own or as part of a two-step process after post-editing. You use these steps and the corresponding lifecycle statuses for each text to manage the post-editing and review process. For more information, see Managing Post-Editing and Review Steps. Decide whether you want to use your own company MLTR for translations. If you decide to use a company MLTR for translations, you need to select which one to use. You can select one company MLTR for each translation project. Only active company MLTRs are available for selection. 3. Save the translation project. 4. Upload your file by selecting it using the value help or by dragging and dropping the file directly onto the Details screen of your project. Your translation project contains the data required to translate the texts in your source file. Once you have created your translation project, note the following: You cannot change the source file type. You can add more target languages, but to enable to register additional target languages, you must upload the source file again. You can upload the source file as many times as you want, and even replace the source file with a different file. However, if you upload a different file, your project s source texts will be replaced with the source texts from the new file that you upload. Any translations that you have done in the project will be deleted. To avoid losing your work, export your translations before you upload a different source file. For more details, see Translate Files. If you use ABAP-based XLIFF files, there are usually multiple.xlf files, because ABAP systems generate one file per language pair during the export process. Upload only one of the files; it does not matter which file you upload. does not import any of the translations that the XLIFF files contain. 104 P U B L I C

105 Related Information Access UI for Translation Workflow Scenarios [page 62] Managing Post-Editing and Review Steps [page 106] Quality Index [page 19] Supported Languages [page 23] Translate Files [page 105] Update and Download Translations in Files [page 106] Translate Files You use translation projects to translate files of the supported formats as part of the translation workflow of. There is a translation project for your source file, containing the texts to be translated. On the UI for translation projects, choose the translation project that refers to the source file to be translated, and choose Get Translations. For an overview of how to translate a file, check out the following video that shows how to translate a Java properties file: The source texts are translated into the target languages specified in the translation project. For more information, see the following sections. Review Translations To check the translations in the project, choose the Translations tab. You see all translations in the translation project and the translation provider that uses for each text. View Quality of Translations The quality index helps you to judge the quality of translations. The higher the number on a scale from 0-100, the better the quality. For more information, see Quality Index. Download Translations To use your translations outside of, choose Download Translations. Related Information Access UI for Translation Workflow Scenarios [page 62] Building Base URL of [page 33] Create Translation Projects for Files [page 103] Quality Index [page 19] Update and Download Translations in Files [page 106] P U BL IC 105

106 Update and Download Translations in Files You can use the UI to add or change translations created by during the translation workflow. You have used the translation workflow of to translate the texts from a file that you have uploaded manually. When you use the translation workflow, stores the translations of texts from your source file for each target language. If required, you can create or update translations, and finally download them in a.zip file. When you download your translations, you get one file per target language (or per language pair for XLIFF files). 1. On the UI, choose the translation project that refers to the uploaded source file whose translations you want to update. 2. Choose the Translations tab. shows the languages defined in the translation project along with the source texts from the object list and the translations. 3. Choose the target language in which you would like to check or update translations. 4. In the Translated Text column, update translations as required. The translation provider is updated to show that you changed the text that entered. 5. Save your changes. If you need to change the translations in other target languages, repeat the previous steps for each target language. 6. To use your translations outside of, choose Download Translations. provides a.zip file that contains one file in the corresponding format for each target language (or for each language pair for XLIFF files). You can then extract the.zip file and manually upload the target files in your original application. Related Information Access UI for Translation Workflow Scenarios [page 62] Building Base URL of [page 33] Create Translation Projects for Files [page 103] Translate Files [page 105] Managing Post-Editing and Review Steps If you want to check and adjust the translations that provides systematically, you can use different lifecycle statuses to manage the post-editing and review steps for each translation in a translation project. To manage the post-editing and review process as flexibly as possible, no specific roles are required in SAP Translation Hub and there aren't any role-based UIs. Based on the setup and requirements in your organization, 106 P U B L I C

107 you can choose to skip the post-editing and review steps, use the steps individually, or combine them as part of a two-step process. For example, you can use the lifecycle statuses regardless of whether one person has numerous roles in your organization or you have dedicated people for the different roles. Decision Table for Managing Post-Editing and Review Steps What Roles Do You Have in Your Organization? We have specialists for each step in the process; we want the experts to sign off their part of the process. One person does everything; we don't want to set specific statuses unnecessarily. We have only a few small translation projects and we don't want to have to set any statuses. Our Recommendation Two-step process for separate post-editing and review steps. One-step process for combined post-editing and review steps. No special process; you don't see any special post-editing or review statuses. The following video shows how to use the post-editing and review options: Related Information Configure Translation Projects [page 107] Translation Project FAQ [page 113] Use a One-Step Process [page 108] Use a Two-Step Process [page 109] Configure Translation Projects When you create a translation project, you can decide how you want to manage the post-editing and review steps. What Kind of Process Do You Want to Use? Configuration Setting What Does This Setting Mean? No specific steps Do not select Post-Editing Required or Review Required. It's business as usual; you don't see any special review or post-editing statuses in your translation project. The lifecycle status on text level and the project status show only whether texts have been translated by. One-step process Select Review Required. After translates the texts in your translation project, the lifecycle status is In Review. When the person responsible for reviewing the translations is done, he or she completes the review step by approving the translations. P U BL IC 107

108 What Kind of Process Do You Want to Use? Configuration Setting What Does This Setting Mean? Two-step process Select Post-Editing Required and Review Required. After translates the texts in your translation project, the first step is to post-edit texts. As the second and final step in the process, the reviewer approves the translations Use a One-Step Process If you want to check the translations that provides using a simple process, which requires only one status to be set, we recommend that you use the review step. In the configuration settings for your translation project, you have specified that the review step is required. For more information, see Configure Translation Projects [page 107]. You use this process if one person completes the post-editing and review steps. The lifecycle status for each translation in your translation project enables you to see at a glance which translations or source texts were added since the last time you translated the translation project. shows you whether you've reviewed all translations in your translation project by displaying an overall status in the top right of the translation project screens. The following graphic shows the main steps in the process. 1. translates the texts in your translation project. 2. To review the current lifecycle status of translations in your translation project, switch to the Translations tab. You see the current lifecycle status for each translation and an overall status for the translation project in the top right of the translation project screen. For newly translated texts, the lifecycle status for each translation is In Review and the status of the translation project is Review in Progress. To make it easier to see which texts the reviewer needs to approve, we recommend that you filter the translations by the In Review lifecycle status. 108 P U B L I C

109 3. The reviewer adjusts the translations as required and then approves the translations. It's possible to approve each translation individually or by selecting multiple texts on the current screen in the translation project and choosing Approve:. 4. To complete the review process, the reviewer saves the translation project. If all translations have been approved and have the status Reviewed, the status of the translation project changes to Review Complete. 5. Optional: If the reviewer or someone else changes a translation that has already been approved, SAP Translation Hub resets the lifecycle status. To complete the process, any translation whose status was reset must be approved again Use a Two-Step Process If you have multiple roles in your translation process, you can first assign someone to post-edit the translations that provides. A dedicated reviewer can then approve the post-edited translations. In the configuration settings for your translation project, you have specified that both post-editing and review steps are required. For more information, see Configure Translation Projects [page 107]. You use this process if you have dedicated post-editing and review steps in your translation process. Although each step has its own focus and corresponding lifecycle status, you use the same UI without rolebased access for both steps. The lifecycle status for each translation in a translation project enables you to see at a glance which translations have been reviewed or post-edited. The lifecycle status also enables you to determine which translations or source texts were added since the last time you translated the translation project. shows you whether you've reviewed or post-edited all translations in your translation project by displaying an overall status in the top right of the translation project screens. P U BL IC 109

110 The following graphic shows the main steps in the process: 1. translates the texts in your translation project. 2. To review the current lifecycle status of translations in your translation project, switch to the Translations tab. You see the current lifecycle status for each translation and an overall status for the translation project in the top right of the translation project screen. For newly translated texts, the lifecycle status for each translation is In Post-Editing and the status of the translation project is Translation in Progress. To make it easier to see which texts the post-editor needs to check, we recommend that you filter translations by the In Post-Editing lifecycle status. 3. The post-editor checks the translations and confirms that he or she has finished post-editing. It's possible to confirm the post-editing step for each translation individually or by selecting multiple texts on the current screen in the translation project and choosing Finish Post-Edit: 4. The post-editor saves the translation project. If all translations in the translation project have the status In Review, the status of the translation project changes from Translation in Progress to Review in Progress. 5. The reviewer checks the post-edited translations. To make it easier to see which texts the reviewer needs to check, we recommend that the reviewer filters the translations by the In Review lifecycle status. 6. Optional: If the reviewer wants the post-editor to repeat the post-editing step, the reviewer selects the corresponding entries and chooses Send Back for Post-Editing: This step resets the lifecycle status to In Post-Editing, after which the post-editor must again confirm that post-editing is complete by choosing Finish Post-Edit. 7. The reviewer approves the post-edited translations. It's possible to approve each translation individually or by selecting multiple texts on the current screen in the translation project and choosing Approve: 110 P U B L I C

111 8. To complete the two-step process, the reviewer saves the translation project. If all translations have been approved and have the status Reviewed, the status of the translation project changes to Review Complete. 9. Optional: If the reviewer or someone else changes a translation that has already been approved and then saves the translation project, resets the lifecycle status to In Post-Editing, and the process starts from the beginning Working with Translation Projects This section describes the different parts of the translation project UI. Header Section The header section includes the following information: A status for the translation project as a whole This status relates to all translations and all target languages in a translation project. For example, if you are still reviewing the translations for one target language, the overall project status reflects the status of that target language. Only when you set a particular status for all translations in all languages and you save the translation project does the status on project level change. The number of translations in each target language Translations Tab After your texts have been translated, shows the translations for each required target language on the Translations tab. The following features make it easier to review translations. Filter, Sort, and Multiple Selection You can view the number of translations for each lifecycle status, such as In Post-Editing or Reviewed, and the sequence of lifecycle statuses. P U BL IC 111

112 By choosing the buttons for lifecycle statuses, you can filter the translations by a given lifecycle status. You can filter the translations based on the quality index or translation provider and sort the result by using the buttons to the right of the search box. To change the lifecycle status of multiple translations at once, use the checkboxes at the left of each row. If you select at least one row, the status action buttons (such as Approve or Send Back for Post-Editing) at the bottom of the UI become active. Additional Information on Text Level To enable translators and the people who review translations to get as much information as possible about the texts, you can see the following attributes: The attributes appear only if they exist in the source file or development environment. The text type, such as XFLD for a field label Context information about each text in the form of comments that developers enter in their development environment The maximum number of characters that each translated text can have; if you enter a translation that exceeds this number of characters, a message appears under the translated text in question 112 P U B L I C

113 1.4.7 Translation Project FAQ When working with translation projects, you might encounter situations that you would like to understand and resolve. Situation I have changed some translations, but when I save my changes, I get an error message stating that further changes are not possible. Explanation This error occurs when two translators are making changes to the same text in the same language at the same time. It is the result of a locking process that uses to ensure the integrity of translations in the database. This matter occurs rarely. But if you work with other translators for the same language, consider planning your activities to avoid the locking mechanism taking effect. I see strange codes (preceded by \u) in my translated file. These codes are Unicode escape sequences, and appear because you selected the Escape Non-ASCII characters option when you created your translation project. To avoid seeing these codes, change the Escape Non-ASCII characters option for your current translation project, and download the translated file again. The codes will no longer be visible in your translated file. I'm creating an ABAP translation project, but instead of seeing an ABAP system in the dropdown, I see System Configured on Subscription Level. This description means that the RFC destination for an ABAP system was created on subscription level, not on subaccount level. We recommend that you create RFC destinations on subaccount level. For more information, see the SAP Cloud Platform Cockpit section in Prerequisites for Translating ABAP Short Texts Using an RFC [page 63]. In my ABAP translation project, I see the lifecycle status Not Applicable. What does that mean? The Not Applicable status appears when the target language in your translation project is the same as the original language of the texts. Since it is not possible to edit any texts in their original language in, a special status is required. Furthermore, the text in the Translated Text column is grayed out and cannot be edited. 1.5 Integrating Your Own Language Data You can use your own specific translations and terminology to translate texts with. When you translate texts as part of the translation workflow scenarios and with the translate API, SAP Translation Hub uses two translation providers: the SAP multilingual text repository (SAP MLTR) and SAP machine translation (SAP MT). P U BL IC 113

114 Since the translations that these translation providers propose can't always meet the specific requirements of your industry or company, you can integrate your own language data in the translation process. To use your own language data, you use a company MLTR, which serves as an additional translation provider. To use your language data in, the following steps are required: Upload Language Data [page 121] Create a Company MLTR [page 122] Access UIs for Integrating Your Own Language Data [page 121] Prepare a Company MLTR [page 122] Activate a Company MLTR [page 123] Translate Texts with a Company MLTR [page 124] The following video shows how to integrate your own language data from XLIFF files in : Related Information Access UIs for Integrating Your Own Language Data [page 121] Prerequisites for Integrating Your Own Language Data [page 114] Regions and Hosts [page 23] Upload Language Data [page 121] Prerequisites for Integrating Your Own Language Data This section contains the tasks that you must complete before you integrate your own language data in SAP Translation Hub. Task Grant users the required authorization More Information Authorization for Integration of Your Own Language Data [page 115] 114 P U B L I C

115 Task Prepare XLIFF files that you want to upload to SAP Translation Hub Prepare object lists in your source ABAP systems More Information Content and Attributes of XLIFF Files [page 116] See Object lists for translation in the 1. ABAP Back-End System section of Prerequisites for Translating ABAP Short Texts Using an RFC [page 63] Authorization for Integration of Your Own Language Data The use of your own language data in is controlled by a dedicated authorization process. The authorization concept is required in addition to the regular authorization that you need for the other parts of. Prerequisites You have granted authorization to the users who need to use. For more information, see User Authentication and Authorization [page 29]. Process When you enable in the SAP Cloud Platform service catalog, the system automatically assigns your SAP Cloud Platform user to the required role. No further assignments are required for your user. If you want to enable other users to work with the functions specific to the integration of your own language data, assign the required users to the User role as follows: 1. Choose the tile in the SAP Cloud Platform cockpit. 2. Choose Configure Service: Company MLTR Functions. 3. In the pane on the left, choose Roles. 4. In the User section, choose Assign and enter the user ID of the required users, as shown in the following screenshot: P U BL IC 115

116 For role assignments to take effect, close all browser sessions and open a new session or log out from the cockpit and log on again Content and Attributes of XLIFF Files To enable to process XLIFF files for use in a company MLTR, the XLIFF files that you upload must meet certain prerequisites. The following sections outline the individual prerequisites. To visualize the attributes and structure, see the sample XLIFF file. File Attributes The structure of the XLIFF file must correspond to XLIFF version 1.2. The source language of the texts in the XLIFF files must be English. The translation unit keys must be identical in the files for all language pairs. The set of XLIFF files that you upload must have the same source language. For example, English-French, English-German, English-Spanish. 116 P U B L I C