An example of Fiori Globalization implementation – the logic of amount value truncation

You have observed the following behavior: the sales volume is displayed in detail view with 1880 USD, while in master list, it is displayed as 2K for short. Why?

The truncation behavior in master list is implemented by Fiori application to fulfill the product standard of Globalization requirement.

The exact value for SalesVolume is 1880.00,

And for the field in master list, there is a formatter to return the volume in short format:

And in order to understand the implementation detail of framework API “FormatAmountShort”, we have to understand the definition of CLDR – Unicode Common Locale Data Repository.

The Unicode CLDR provides key building blocks for software to support the world’s languages, with the largest and most extensive standard repository of locale data available. This data is used by a wide spectrum of companies for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks. See one part of CLDR definition below from http://cldr.unicode.org/translation/number-patterns :

The first call of FormatAmountShort will trigger the load of CLDR file in the runtime.

The English version of CLDR content defined in the web page http://cldr.unicode.org/ is packed and stored in JSON file en.json by SAP and is now loaded:

And here below is the code how “1880” is transformed to “2k” by framework code:

The reason why English version of CLDR file is loaded is the language setting of the browser.

UI5 runtime will use the first Language configured in browser as primary language for all subsequent language-specific configuration stuff load mechanism, as illustrated in line 67 below:

Finally the English version of CLDR file is loaded in line 718: