@numerical-type: annotation influences only what you see in the web app/GUI. It does not affect how values are stored, so it is important to ignore them unless you are focusing on the GUI.
The name of the numerical type should correspond to the precision that you require.
From your model I can see that you want to store a
childcarePercentage with 1 decimal place. Therefore, you need a numerical type such as
promille which represents a percentage with 1 decimal place.
The numerical type
fraction is only useful for computations.
You cannot actually store a
fraction as an Alan
number; only intermediate results can have decimal places.
Example code for getting the expected result for
'childcarePercentage': number 'promille' = 96 // 9.6 % in the GUI
'HoldingTarif': number 'eurocent' = 9430 // 94.30 Euro in the GUI
'benefit': number 'eurocent' = product ( // 9.05 Euro in the GUI
from 'promille' .'childcarePercentage' as 'fraction' ,
= 'fraction' * 'eurocent'
= 'promille' * 1 * 10 ^ -3