In most SAP Fiori apps, translations are pretty straightforward—we rely on standard i18n files and the user’s browser language. But sometimes, things get a little tricky. Think about texts coming straight from backend APIs or typed in by users. These aren’t in your standard translation files, and you can’t predict them ahead of time. So, traditional static translation techniques weren’t sufficient.
To translate runtime texts, SAP provides an AI-based service through SAP Translation Hub.
Instead of relying on predefined translations, you can send the texts dynamically to the API and get back translations instantly.
Why Software Translation?
Designed for short UI texts
Allows translating multiple languages and strings in a single request
No need for document uploads or static files
Enable Entitlements in SAP BTP
Add SAP Translation Hub as a service plan
Create a Service Instance
Use the default plan in Cloud Foundry or another supported runtime
Use the Software Translation API
Authenticate using client credentials
Use client_id, client_secret, and token URL from the service instance
Send dynamic text for translation
Provide:
Source language
Target language(s)
An array of texts that needs to be translated
Render the translated content in the UI
Display based on the user’s current language preference
| Aspect | Document Translation | Software Translation |
| Best for | Files, long content | UI labels, short strings |
| Input Type | .docx, .html, .pdf | JSON payload |
| API Calls | One language per call | Multi-language support |
| Ideal Use | Reports, documents | Runtime UI elements |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 120 | |
| 37 | |
| 37 | |
| 19 | |
| 17 | |
| 15 | |
| 12 | |
| 12 | |
| 10 | |
| 9 |