Symptom
- Some System dictionaries (for example, Polskie/Polish, Taiwanese, and Traditional Chinese) may not contain translation values in SAP CPQ.
When such dictionaries are selected as the Default Dictionary on the User page, translations do not appear in the UI. - Instead, the system displays technical dictionary keys (for example,
Admin.MLDictItems.CustomDict) instead of translated labels.
Environment
SAP CPQ
Cause
- Some system dictionaries in SAP CPQ are intentionally created without translation keys.
- These dictionaries are used for system-level translation selection (for example, product or attribute translations) and are not intended to be directly populated with translation values.
Resolution
System dictionaries cannot be directly populated with translation values via import.
To achieve translations for both technical dictionary keys and system-level elements (such as product names or attribute labels), the recommended approach is:
- Create a custom dictionary.
- Set the corresponding system dictionary as its parent.
- Export an existing dictionary with translation values (for example, US English).
- Translate the values as required.
- Import the translated entries into the custom dictionary.
With this setup:
- The custom dictionary provides translations for technical keys.
- The system dictionary can still be used where system-level selection is required.
- If a translation is not found in the custom dictionary, the system falls back to the parent dictionary.
Note: System dictionaries are managed internally and do not support direct updates or imports.
Keywords
System dictionaries, missing values, keys, translation, Polish, Lithuanian, Traditional Chinese,Taiwanese dictionary, Italian, SAP CPQ, dictionary, custom dictionary, UI labels, technical keys, Admin.MLDictItems.CustomDict, missing translation, language issue, dictionary import, translation keys, labels not translated , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Problem
SAP Knowledge Base Article - Public