Translation within SAP CPQ

[Scholtes_T]

We are unable to find a centralized approach that we would expect in a modern cloud application, but have to translate in X places.

We are looking for a centralized solution to translate our custom themes like custom fields, quote tabs, partner functions etc, preferably all in a custom dictionary.

The help page for this is not very helpful.

How to choose a syntax for these things in the custom dictionary? How can we possibly find this syntax in the system if we don't know exactly how to name an object etc.?

it's not just about finding the right key for the entry in a custom dictionary, but more about the general approach of how to translate in CPQ.

1. What can generally be translated in a custom dictionary? Which objects can be included?
2. How to find the right key for the entry in a custom dictionary?
3. The custom dictionary can only be saved as XML. This is neither customer-friendly nor manageable.

[Fancy_Zou]

Hi,

Thank you for your generous feedback on the translation management of SAP CPQ.

Before sharing my experiences with translation in SAP CPQ, I'd like to kindly request that you submit your feedback on the SAP CPQ Customer Influence Portal. This will ensure that your insights reach our product development team through the official channel, allowing them to review your comments and explore potential innovations to enhance your experience.

Here are some of my experiences related to translation during project implementation in SAP CPQ.

1. Standard Objects vs. Custom Objects

- Standard Objects

The translation maintenance for standard objects follows a predefined path. For instance, maintaining translations for products can be done through the actions menu in the product master data path: Product->Products. This includes all standard fields related to a product or product attributes. Similar concepts apply to Categories, Attributes, etc.

- Custom Objects

Translations for custom objects are managed using translation keys in custom dictionaries. When you create a custom object, a corresponding pre-formatted translation key is generated based on the object's name. You can then maintain these translations in the custom dictionaries. For example, a custom item column might have a key like QuoteLayout.Columns.$ColumnName$. Another example is Product Messages, formatted as {{$translations$}}. Moreover, with the IronPython snippet `Translation.Get(dictionaryId, key)`, you can leverage custom translation keys to perform translations using custom logic and display the results in UI fields or custom outputs.

2. System UI Translation

- General design

SAP CPQ provides translations for standard fields, buttons, and labels on the system UI for a range of languages. If your business requires different text for UI labels or if your local language is not well-translated, you would need to update these translations in custom dictionaries using the appropriate translation key.

- Identifying Translation Keys for Standard UI Labels

A useful practice is to change the "Default Dictionary" to a less common language in your "User Page" settings, such as "English - Italy". This allows you to view all UI labels in their original translation key format, making it easier to identify and update them in the custom dictionary.

I hope this information provides some useful guidance to better manage translations in SAP CPQ. If you have any further questions or need more assistance, please feel free to ask.

Best Regards,
Fancy