
To help remove language barriers, SAP is launching a new automatic machine translation feature for Expert Chat in the SAP ONE Support Launchpad.
What is SAP’s machine translation and How can I use that in Expert Chat?
SAP’s machine translation is a language translation service powered by
SAP Translation Hub, and allows to translate documents, texts, UI elements using a repository of SAP-approved translations and terminology .
When starting an Expert Chat session with SAP Product Support, we will offer the machine translation option automatically. If you agree to use, your chat conversation with the SAP expert will be automatically translated based on the selected language:
- your inputs will be translated from your language to English
- answers from SAP’s experts will be translated from English to your language

Machine Translation in Expert Chat
The machine translation can be
turned off by typing
“translation off” and
turned on again by typing
“translation on” in the text area during the session.
After the Expert Chat session, the chat transcript will be automatically saved to an incident including both the original text and the translated text.
Note: The official language of the Expert Chat – as a product support service - is English. SAP does not provide any warranty regarding the correctness or completeness of the machine translation. The goal of the translation is to make easier the real-time communication with the SAP expert.
Which languages are currently available for the machine translation in Expert Chat?
Update on 24th Nov 2021: The machine translation feature in Expert Chat is available in the following languages:
- Simplified Chinese
- Japanese
- Korean
- Brazilian Portuguese
- German
- Spanish
- French
- Italian
- Russian
Learn more about machine translation
What is Expert Chat?
Expert Chat is a live chat service from
SAP’s Product Support, available only for new technical issues - at no additional cost. Expert Chat is automatically offered during the incident submission process when it is available. The workflow and details described in my previous blogs: