This Is How You Translate SAP Texts.
i18n Translation Manager for SAP® S/4HANA is our SAP translation tool. Whether you want to translate custom Fiori apps, classic Z transactions, or Customizing entries – i18n Translation Manager has got you covered. Start with an initial analysis to get an overview of what exactly you need to translate, and build an end-to-end translations process that truly covers all relevant SAP texts.
And although i18n Translation Manager was built for SAP S/4HANA, it runs on SAP ECC too.
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, and find CDS views, text elements, and domain values – as well as the entries you added in Customizing tables. Learn more →
Extract SAP Texts for Translation
Push your texts to the web-based XTM Cloud translation environment, export them to the industry-standard XLIFF format, or funnel them into transaction SE63. Translators can then enter their texts in the editor you selected. Learn more →
Run an End-to-End Translation Process
Translate one or more apps, or just the texts from your latest release. Automate using SAP Translation Hub, and reuse existing translations. Commit Frontend translations to Git and write translation changes to transport requests. Learn more →
The Omnivorous Translation Tool
With i18n Translation Manager for SAP® S/4HANA, you can translate almost any text in an SAP system. If you enter a custom Fiori app, the tool will add the app’s i18n.properties 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, messages and much more. And as for the Frontend files, you can add those based on the BSP application or directly from a Git repository.
If you are not using SAP Fiori yet, i18n Translation Manager will let you add your custom SAP GUI transactions in a similar way. For each Z transaction that you enter, the tool will analyze its dependent objects and add them to your translation project. In addition, you can include individual objects such as forms, SO10 texts, and specific transport objects.
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 that is identified, any SAP Standard entries are skipped, and only custom entries are added to your project. And the same goes for Customizing tables discovered as part of analyzing dependent objects for Fiori apps or Z transactions.
Your Choice of Translation Editors
With i18n Translation Manager for SAP® S/4HANA, you choose which editor the translators use to type in their translations. Traditionally, SAP texts are translated in transaction SE63, which i18n Translation Manager still fully supports. But you can also export the texts in your translation projects to XLIFF, which is an industry-standard file format that probably every translation agency in the world can work with.
But maybe best of all, you can take advantage of i18n Translation Manager’s full API integration with XTM Cloud, a third-party solution developed by our partner XTM International, and push your SAP texts to this web-based translation platform. This gives your translators access to an easy-to-use, modern, browser-based editor that will speed up the work considerably. Authentication for upload and download happens via OAuth 2.0.
After the translation work is completed, you can import the translations. i18n Translation Manager will synch the new translations with the system state at the time of import to ensure that no incorrect translations are written. After that, the translations are ready to be deployed.
Select, Translate, Commit, Deploy
With i18n Translation Manager for SAP® S/4HANA, you will be running a translation process that is truly end-to-end. You can create translation projects that contain both Frontend and Backend texts, bridging the gap between Fiori and SAP GUI. You can create translation projects based on transport requests, which allows you to translate only the texts that were added or changed in a specific release of your custom apps, for example. This makes our SAP translation management tool the ideal solution for Agile scenarios.
And when it comes to deploying your translations, i18n Translation Manager offers a lot of flexibility. For Backend objects, you deploy via language transports. For Frontend texts, you can deploy via transport requests, you can commit your changes to Git repositories, or you can download your translated files. You even have the option to directly update BSP pages on your quality system via RFC so your new translations are visible to testers right away.
When you deploy a translation project, i18n Translation Manager performs a synchronization against the current state of the apps you have translated, to catch any changes a developer may have made to its source texts. And when writing to transport requests, the tool check for apps that are currently locked in another transport to avoid conflicts with any development going on at the same time.
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!