See https://sapui5.hana.ondemand.com/#/topic/6c47b2b39db9404582994070ec3d57a2%23loioaa9024c7c5444822a68daeb21a92bd51
Example:
<ObjectStatus id="Simulation.DynamicPageHeader.Attr.QuantityWithUnit"
title="{/#FixedAssetPosting/QuantityInBaseUnit/@sap:label}"
text="{parts:[ {path: 'QuantityInBaseUnit'}, {path: 'BaseUnit'}, {path: '/##@@requestUnitsOfMeasure'} ],
type: 'sap.ui.model.odata.type.Unit'}" />
The third part represents the backend customizing which declares the unit "KG" has 3 decimals so that it is formatted as expected. The ability to use backend customizing is specific to the sap.ui.model.odata.type.Unit, as the customizing is loaded via the corresponding code list defined in the OData service used.
If using sap.ui.model.type.Unit UI5's built-in unit customizing applies which is derived from Unicode CLDR. For units, this is to a large extent different from ABAP backend customizing. CLDR only knows kilogram as "kg" (lowercase), meaning that "KG" is an unknown unit. Consequently, the numeric value is formatted "as is". And even if CLDR would know "KG" it might define a number of decimals to show which is different from ABAP backend customizing.
