This Is How You Translate SAP Texts
i18n Translation Manager for SAP® S/4HANA gives you one SAP-certified and clean core compatible tool for all your translation needs. You can translate Fiori apps, Z transactions, Customizing entries, custom forms, and much more. Run an initial analysis to identify every text that needs translation. Then build an end-to-end translation process that truly covers all your SAP texts, using an LLM to translate the bulk of the texts automatically.
Easily Define Your Translation Scope
Enter your custom Fiori apps and Z transactions and let the tool identify the objects they use, such as i18n.properties files, CDS views, text elements, and domain values, as well as the entries you added in Customizing tables. You can also enter transport requests or development packages.
Let Your LLM Do the Translation
Translate your texts using the LLM of your choice, and have it flag the most difficult texts for human review. You can also push your texts to the web-based XTM Cloud translation environment or to SAP Translation Hub. Your linguists translate or review in the editor you selected.
Run an End-to-End Translation Process
Translate any apps or just the texts from your latest release. Automate your workflow, reuse existing translations, and generate translations using an LLM. Commit frontend translations to Git, and write translation changes to transport requests. And if needed, you can also roll back your translation changes.
The Omnivorous Translation Tool
With i18n Translation Manager for SAP® S/4HANA, you can translate almost any text from an SAP system, including SAP ECC. If you enter a custom Fiori app (RAP, CAP, or freestyle), the tool will add the app’s i18n.properties and CSV files to your translation project and optionally add backend objects that the app uses, as well. That includes CDS views, metadata extensions, text elements, data elements, domain values, tables, and messages.
You can also add your custom SAP GUI transactions in a similar way. And as for the Fiori frontend files, you can add those based on the BSP application, or directly from a Git repository.
The most common way to add texts to a translation project may be via transport requests. i18n Translation Manager will analyze the content of the transports entered, identify translatable texts, and add them to your project. You can filter by object types, development packages, or namespaces.
In addition, you can include other objects such as PDF forms, Smartforms, or SO10 texts. Once you’ve created your translation project, you can see the size, translation state, metadata, and the texts of each object. Use Visual Scoping to refine your translation scope and exclude any objects that should not be translated.
i18n Translation Manager also offers extensive support for translating entries you add to Customizing tables. You can analyze an entire system and collect the Customizing entries created on that system into your translation project, or you can analyze specific transport requests. For each table identified, SAP Standard entries are skipped, and only custom entries are added to your project.
Translate with an LLM and Review Only the Difficult Texts
With i18n Translation Manager for SAP® S/4HANA, you no longer need to translate every text by hand. Instead, an LLM translates your texts, using the context in your SAP system – translation history, approved translations in other languages, SAPterm, and your own terminology – combined with translation rules for each SAP text type. Translation runs as a background job, so even big projects run unattended.
Difficult texts, such as ambiguous texts, unclear abbreviations, or translations that do not fit the available space, are flagged for human review – together with the reason why. Your translators or subject matter experts review and approve or correct these texts in the built-in editor. This saves them time, lets them focus on the texts that actually need a decision, and produces great translation quality. A reference implementation using Anthropic's Claude works out of the box, but you can connect any LLM via a BAdI – for example, a model from the AI provider that your organization already uses.
For bigger projects, or where every text needs expert-level review, your linguists can work on XTM Cloud to review AI-generated translations or translate from scratch. XTM Cloud is a modern, browser-based editor by our partner XTM International with great usability that dramatically speeds up a translator's work. You can also use SAP Translation Hub, which is a great lightweight, easy-to-use environment for internal colleagues to review and approve translations. DeepL is available for classic machine translation. All three are fully integrated with i18n Translation Manager. You can also export your texts to XLIFF, an industry-standard format almost any translation agency can work with, or translate in transaction SE63, which i18n Translation Manager still fully supports.
Build Translation Processes Using an SAP-Certified Translation Tool
With the SAP-certified i18n Translation Manager for SAP® S/4HANA, you can run a truly end-to-end translation process. You can translate both backend and frontend texts, including texts from Git repositories holding RAP or CAP Fiori apps, bridging the gap between Fiori and SAP GUI. You can also translate only texts that were added or changed in a specific release of your apps or other SAP developments by basing translation projects on transport requests, which is ideal for Agile scenarios.
And when it comes to deploying your translations, i18n Translation Manager offers a lot of flexibility. For backend objects, you write the translation changes to transport requests. For frontend texts, you can deploy via transport requests, commit your changes to Git repositories, or download your translated files. For apps that deploy to the backend, you even have the option to directly update BSP pages on your quality system via RFC, so your new translations are immediately visible to testers.
When you finalize a translation project, i18n Translation Manager carries out a synchronization against the current state of the apps and backend objects you’ve translated to catch changes a developer may have made to source texts. And when writing to transport requests, the tool checks for apps currently locked in another transport to avoid conflicts with any development going on at the same time.
After you have delivered translations, you can still go back and make corrections based on tester feedback, or correct translations that were flagged for review, but that you did not manage to review in time. And if push comes to shove, you can also fully roll back the translations and restore the old translation state using a correction project. i18n Translation Manager tracks the translation state of each text and lets you manage the entire translation workflow end-to-end.
Do You Need a Custom Solution?
We are frequently asked to adapt our add-ons to fit our customers' needs,
or create new
tools from scratch. Let us know how we can help!