Symptom
Unable to find keys like COMMON_LEARNING_TAB and COMMON_GOALS_TAB from both custom and default language locales.
Environment
SAP SuccessFactors HCM Suite.
Reproducing the Issue
- Login to the instance
- Go to Manage languages
- Select any language pack to be modified
- Download both default and custom locales
- Notice that the COMMON_LEARNING_TAB and COMMON_GOALS_TAB can't be found but the keys are showing when language is switch to English Debug.
Cause
Known issue due to a code defect
Resolution
Engineering team have identified the fix on a code level and will be deployed by 4th of November so now message keys like(Language COMMON_LEARNING_TAB and COMMON_GOALS_TAB ) are found under Manage language after deployment
What to Expect After the Fix Deployment
After deployment, all the keys can be found and modified through both UI & CSV. But there are certain points below to be aware of:
1. For TST-only message keys with no customization history before the preview release- Any new customization done after the fix (post 4th November) will correctly appear in both the UI and CSV.
2. For TST-only message keys that do have customization history before the preview release- After the 4th November release, you may temporarily see a message strip showing “Invalid keys found in audit.” To address this, we are preparing an additional data fix around Nov 20th. This fix will ensure that these message keys appear correctly in the Valid Message Keys table with complete history under the Custom Translation column. This fix is only for the Preview environment and has no impact on Production.
Production is already behaving as expected since the core defect was fixed earlier.
After the additional fix on November 20, the visibility of custom translation history may vary depending on when customizations were made during this period:
a) After preview release and before Nov 4th, if any customization done (not only for TST, but all), all history before release will be lost
b) No customization between 4th–20th Nov
- All pre-preview history will be retained under the Custom Translation column.
- Any new changes made after 20th Nov will also appear correctly.
c) Customization done between 4th–20th Nov
- Pre-preview history data for that specific key will be dropped. (Once customization is done after 4th Nov for a specific TST key, any older history (before the preview release) will no longer be visible.)
- However, history created after the preview release will remain available.
Note : Production System Impact
- This issue will not occur in Production, as the defect was already corrected before the Production release
- All historical data will remain intact and fully synced.
Keywords
COMMON_LEARNING_TAB, COMMON_GOALS_TAB, missing, translation, keys, manage language, Learning, Goals. , KBA , LOD-SF-PLT-LAN , Manage Language & Text Replacements , Problem
SAP Knowledge Base Article - Public