cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Localization in SAP Asset Manager 2010 application

neha_mahanty
Active Participant
0 Kudos
836

Dear All,

I am working on SAP Asset Manager 2010.

My requirement is to change the application language to "German" Language.

How do I proceed with this change , so that the application details as well as data coming from backend , will be displayed in German language.

There are settings in Mobile status and oData object configuration, so does it mean I have to make the localization active in each object ? Is there a central place where we can change and it effects the entire application , OR do I need to update the language parameter file in SAP WebIDE?

Can you guide me in this please.

Thanks and Regards

Neha Mahanty

Accepted Solutions (1)

Accepted Solutions (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert

Neha,

By default, MDK applications look at the device language and use to determine the language to use for the onboarding screens. This of course assumes appropriate that translations are provided for things like the welcome screen and EULA. After onboarding when the application metadata is loaded the default again is the device language which then determines which UI language strings are used (again assuming the appropriate translations).

In terms of the backend data, the Language URL Param can be used to pass the current device language to the backend so it can return data in that language (again assuming the backend supports this capability and the data is maintained in the specified language).

If you want only Asset Manager to be in German but not set your device to German language, then you could change the metadata to use german translations by default and also look at hard coding the language code to the backend. This would only affect the MDK UI screens and data. Any onboarding and common client dialogs and messages might still display in the device language (errors etc).

--Bill

neha_mahanty
Active Participant
0 Kudos

HI Bill,

Thank you very much for the detailed explanation.

I think in the initial state I would suggest the team to change the device language. Meanwhile I will try the way you have suggested and also to use "Language URL Param" so that the backend data also appears in the required language, which we can release in later project cycle.

Thank you very much

Thanks and Regards

Neha Mahanty

Answers (1)

Answers (1)

prashanthi_vangala2
Product and Topic Expert
Product and Topic Expert

German is a supported language.so, just change your device settings to German and you can test the standard SAM in German..But, if you have done any custom enhancements with custom labels..that needs to be translated in appropriate i18n language files.

neha_mahanty
Active Participant
0 Kudos

Hi Prashanthi,

Thank you , Please correct me If I am wrong. By device setting you mean the mobile device right ? But If I change the Mobile device settings will it not change other applications language also in German.

I would need only Asset Manager to be displayed in German. Also I have not created any custom labels , This is the standard application.

Could you please clarify my doubt.

Thanks and Regards

Neha Mahanty

muhammad_rafay
Product and Topic Expert
Product and Topic Expert
0 Kudos

You cant change the language of only one single application. You have to change the device language in order to see the supported language

neha_mahanty
Active Participant
0 Kudos

HI Muhammad,

Thank you !!

However, when I share this with the functional team, they are not convinced that we have to change the device language setting. I think we understand differently ,Like for example theme, If we change the theme of one app then it applies only to that app and does not effect others. Hope I am able to explain the dilemma here.

Would you be able to share any supporting document from SAP which I can take ahead with the client.

Hope you don't mind, I really appreciate the guidance from you and also Prashanthi , but I am not able to convince the team as we had another understanding of this feature.

Thanks and Regards

Neha Mahanty