The Maintain Translations app offers a simple way to translate developer extensions into other languages. Developer extensions refer to objects created via developer extensibility, such as Data Elements, Message Classes, Business Configuration Objects, Data Definitions, Metadata Extensions and more.
For more information about the app, check this SAP help link: SAP Help – Maintain Translations.
To learn the process for maintaining translations, visit this blog by Vijay. The process is applicable to both BTP and S/4HANA as mentioned below –
Additional Steps:
After following the steps in the blog, you may be prompted to enter a transport request when uploading and publishing translations. Ensure you have created a TR under your name, as it will be required during this step.
Once completed, the changes should reflect in the Fiori app when accessed in another language. However, you may encounter situations where the translations don’t immediately reflect in the UI service.
Resolving Translation Reflection Issues:
After translating the CDS annotations of a metadata extension or data definition, it is essential to activate the object again in ADT. This can be done by making a trivial change, like adding and removing a space, and then reactivating it. This step must be performed after publishing the translation in the Fiori app.
Why is Activation Necessary?
Fetching the service metadata from the server involves 5 layers of caching mechanisms, at least two of which only react on (translation) changes if an internal timestamp is changed. So far only the activation of objects involved in the service stack are able to update this timestamp. Since the Maintain Translations application is external to the service stack, the combined effort required to enable a reliable automatic refresh of the translation data in the service metadata as part of the Maintain Translations publish would be quite high, hence this is still in pipeline for SAP to implement.
Due to how the translation data of metadata extensions and data definitions is handled in the transport system, this issue can only affect the development system and the quality / productive systems in which the translations are imported will always have the up-to-date service metadata.
Thanks for reading!
The Maintain Translations app offers a simple way to translate developer extensions into other languages. Developer extensions refer to objects created via developer extensibility, such as Data Elements, Message Classes, Business Configuration Objects, Data Definitions, Metadata Extensions and more.For more information about the app, check this SAP help link: SAP Help – Maintain Translations.To learn the process for maintaining translations, visit this blog by Vijay. The process is applicable to both BTP and S/4HANA as mentioned below - Additional Steps:After following the steps in the blog, you may be prompted to enter a transport request when uploading and publishing translations. Ensure you have created a TR under your name, as it will be required during this step.Once completed, the changes should reflect in the Fiori app when accessed in another language. However, you may encounter situations where the translations don’t immediately reflect in the UI service.Resolving Translation Reflection Issues:After translating the CDS annotations of a metadata extension or data definition, it is essential to activate the object again in ADT. This can be done by making a trivial change, like adding and removing a space, and then reactivating it. This step must be performed after publishing the translation in the Fiori app.Why is Activation Necessary?Fetching the service metadata from the server involves 5 layers of caching mechanisms, at least two of which only react on (translation) changes if an internal timestamp is changed. So far only the activation of objects involved in the service stack are able to update this timestamp. Since the Maintain Translations application is external to the service stack, the combined effort required to enable a reliable automatic refresh of the translation data in the service metadata as part of the Maintain Translations publish would be quite high, hence this is still in pipeline for SAP to implement.Due to how the translation data of metadata extensions and data definitions is handled in the transport system, this issue can only affect the development system and the quality / productive systems in which the translations are imported will always have the up-to-date service metadata.Thanks for reading! Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
